I was very specific about my keyboard needs: I wanted basically a keyboard layout from a notebook (mac) so i don't have to adjust to layout, it had to be wired because bootcamp and bluetooth are not working good together, ISO layout (which is TERRIBLY hard to find), full size keys but compact design (think magic keyboard). In the end i settled with penclic, which had the added brilliant advantage of having those media keys right next to fn key, so you can adjust volume with one hand. Stil prefer logitech k780 feedback and feel, but couldnt handle the extra length. Once you go TKL it's hard to go back
That's not the issue, the issue is huge disproportion of influence that these platforms create for their owners. You are practically saying that monopolies are fine as long as you're not getting robbed. The fact is, you probably are getting robbed, by paying too much money for the dominant service.
OP seems to be resentful especially toward the mega fortunes amassed by some folks.
Regarding digital monopolies like facebook and google, those markets didn't even existed 20 years ago. It's them who created them, almost from zero. They created the need in the market. I still can't see any reason why a third party (aka government, in the name of the people) would use force to break them apart. Mostly because they're not monopolies for services related to basic human needs.
Nothing on this project solves the real problems and introduces different ones, like how to have a reducer respond to different actions.
My quibble with React is that when you get into moderately complicated forms, you start sprinkling stuff all over the place to get the desired output.
Take for instance the most popular form library, redux-form. It's very heavy on it's own way of doing things, and there's a lot of stuff you have to know about it to be able to read into what the hell is going on, and it's hard to keep shit in the same place.
Reselect is also very heavy handed for what it does. I NEVER needed anything like reselect before redux, and it kinda went alright!
In my experience, for any reasonable development with redux you have to introduce:
reselect, redux-form, thunk, some sort of immutability (immutable or redux-orm), a sprinkle of compromises and plenty of boilerplate, or roll your own magic util functions (i actually rolled my own very similar stuff to rematch, for quick and dirty stuff).
When you summarise all that, it's really not that simple anymore!
By the time you get through all of that, you might aswell pick up angular with the added benefit of clearer best practices, nicer dependency injection (oh, but react calls it context so it's cooler!), familiarity and type safety.
It's kinda funny how redux succeeded with such heavy concepts, which is normally not the case. This is still a mistery to me.
Oh and don't get me started on HOC. Want a tooltip over your component? Sure, wrap it in tooltip HOC! Sooo much nicer than directives!
It's pretty much an issue of getting to a "stable" state, which means that model stabilizes to a certain value after all the actions by user and code. That can be a problem with 2way binding and sometimes it causes very subtle bugs, but it boils down to the infamous event storm. So that's why they gave up on 2way binding and made it more optional and deliberate
