Infinite Red Shift

I used to recommend unroll.me to people but eventually found that relentlessly unsubscribing from things worked better anyway. I assumed they were making money from ads, but should have known better. I have a few simple rules I follow to hit inbox zero...works quite well: 1. Unsubscribe Relentlessly 2. Use Keyboard Shortcuts or Gestures 3. Snooze Important Emails 4. Use a To-Do App (I wrote it up in more detail here: https://shift.infinite.red/how-i-achieve-inbox-zero-every-day-and-you-…

One of the slides shows "Rails is still the best choice for entire classes of apps." "Best" is of course usually subjective, and this could spawn huge internet arguments back and forth about the relative merits of various solutions. But I think there's perhaps an objective argument to be made that this isn't true now, and won't be true with Rails 5 and beyond. I own a web + mobile app dev shop (Infinite Red). Our background is Rails, and some on our team have been using Rails since pre-1.0 (Steve Kellock, for example wrote the first Rails guides, and his name still appears on the website). We have loved Rails (and Ruby) for a long time. But the concurrency and scalability difficulty of Rails isn't just an opinion. As we've built larger and larger applications on Rails, the amount of effort put into making Rails scale gets disproportionately high. Not to mention server costs. Yes, it's totally possible to scale Rails. No, not every Rails app needs to scale to Twitter-level. We get that; we've been doing both for years. When we discovered Elixir/Phoenix [cue the groans, sorry] it felt like we kept the magic of Ruby on Rails while (in a single stroke) we also made a giant leap forward in concurrency, scale, and reliability. In my opinion, this is the direction the Rails community would be better off going. We felt so strongly about this that my partner Ken Miller wrote a piece titled "Phoenix is Rails 5".…

Very much agree, and even for the more complicated use cases Saga's are much cleaner and I would argue easier to understand. Article below goes through a few of the differences. https://shift.infinite.red/redux-observable-epics-vs-redux-sagas-8e536…

The maintainer released Yarn 2. Yarn 2 is pretty foundationaly different than Yarn 1, and can and does break a lot of products/projects if used. Some folks are not happy about it, although Yarn 1 will probably continue to be maintained by the community for a while. This seems to be pretty fair about the whole thing: https://shift.infinite.red/yarn-1-vs-yarn-2-vs-npm-a69ccf0229cd

More information about this can be found in my the accompanying blog. https://shift.infinite.red/avoid-nightmares-nsfw-js-ab7b176978b1