I started off as a FE dev working on mostly Rails projects. Not knowing Ruby or Rails, I depended on others for updating controllers, debugging Rails errors, etc. I was also commonly frustrated when my teams treated the client as a second-class citizen for no apparent reason besides an aversion to JavaScript. JS' takeoff in the market was actually quite satisfying at first, but the more I worked with Angular, React & company, the more I missed the productivity of server-rendered JS responses, jQuery, and Turbolinks. I doubt Turbolinks + Stimulus wins prom king at JavaScript High next year, and I couldn't care less.
Also, Redux as "self-congratulatory" had me dead. XD
Stimulus is a new upcoming framework for sprinkling in bits and pieces of JS. DHH talked about it on https://twitter.com/dhh/status/946184709528158208.
Also basic blog and structured content 'pages' sites.
For building anything that requires complex client-side interaction, i.e. the sort of things that even warrant looking at React (e.g. a calendar app, or a music player app), then you're going to get yourself in a real mess attempting that with 'javascript sprinkles'.
> Also, Redux as "self-congratulatory" had me dead. XD
Also completely wrong if you've ever read/heard anything Dan Abramov has ever written/said [1].
[1] https://medium.com/@dan_abramov/you-might-not-need-redux-be4...
Stimulus essentially structures DOM manipulation. Whereas other frameworks aim to solve rendering, it seems Stimulus will offer a lo-fi and sane way of making your views dynamic. Restated, it's a framework for managing JS sprinkles aka jQuery spaghetti aka templating logic. I don't think its a component library because DHH explicitly mentioned its not a mechanism designed for handling JSON and similar concerns. It targets the realm of updating element classes and attributes, handling events, etc. It'll also allow you to partially update views with HTML templates sent over the wire.
When combined with Turbolinks, it should elegantly solve all your everyday front-end concerns. There's a lot of helpful context I'm neglecting - check out the podcast, DHH pretty much opens with this topic.
DHH's complaints here about React (and Redux especially) resonate with me, but I have a hard time believing a React-less approach is the best solution. I'd rather Rails roll its own enhancement of Redux - and perhaps CSS management - alongside a handful of component generators that make everything from "Javascript sprinkles" to SPAs easier to manage in Rails.
It seems wrong at a moral level. Especially since smoke detectors and carbon monoxide monitors can be bought for $10-25.
I know nothing about making a co2 monitor but other than marketing hype, the willingness to function at optimum efficiency and not die of oxygen deprivation, is there anything about it at the hardware level that warrants it being 10x the price of other sensors?
