19 Matching Annotations
  1. Mar 2022
  2. Jan 2022
  3. Oct 2021
  4. Jun 2021
    1. so by adopting git installations with latest source code you're effectively agreeing to go bleeding-edge. I would assume that means you're ready for any breaking changes and broken installations, which is what happened here.
  5. May 2021
  6. Mar 2021
    1. The Model macro literally does what our model! step did.

      That information is not generally relevant. Only makes sense for someone who actually knew about or used the old interface.

      The docs shouldn't assume you are an experienced user / a user of the previous version.

      Would have been appropriate in a Changelog entry or announcement, but not in the general docs.

  7. Feb 2021
    1. More and more, Im seeing this "retro graphics" (aka - lazy cash in.) money grab titles that are completely broken or absolutely terrible.. and they're RAPIDLY flooding the Switch like flies to horse dung. With no real reliable independent reviews of Indie titles available (Even MetaCritic is blank for at LEAST 70% of these indie garbage games..) players are left with no recourse but to flush hard earned cash on what is essentially a non-refundable gamble.
  8. Dec 2020
    1. more leading edge than bleeding
    2. Is using bleeding edge tech risky and foolish? How much blood are we talking about? My experience tells me Svelte is a safe choice, more leading edge than bleeding.
  9. Nov 2020
  10. Oct 2020
    1. This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.
  11. Sep 2020