281 karma · joined October 1, 2014
It was on its way to get implemented and then Microsoft enabled it by default in IE10, so not making it the choice of a human, and ruined it for everyone.
It would be better if that would be the other way round "linter forbids it unless you ask it not to". Never wrong to allow users to shoot themself in the foot, but it should be explicit.
- One the homescreen seeing the search as a clear button is useful for most users. The swipe down is just not easy to find and remember. The dots shown when swiping through homescreens is actually much clearer if you don't have so many pages.
- Same goes for the pull down search bar. It took me a long time to remember that. And then in the system settings it always took me some time to find it again. That it's the same gesture as reload in other apps made it even more confusing. Now it's right where you thumb is.
- The pulsating buttons - I haven't even seen them. And I switch during the public beta phase. Normally buttons get hidden by your thumb when you press them.
- And then yeah a lot of things look different now. We had that before when we switch to the previous design language and people were just complaining as much.
But it's really not needed - you can just use signals in react with the preact-signals package (works with preact and react and standalone) which has been created 3 years ago: https://preactjs.com/blog/introducing-signals It can even skip the virtual dom and diffing.
The issue is not React per se. Just look at what the ecosystem has to offer. You can also speed up your loading times by using preact. And if you don't like a compile step use a package like htm and tagged templates for a JSXish syntax. And then move your "store" outside of react with signals etc. There is enough innovation happening, no need to always look at the other side.
But if you want some small and simple framework as guidance you can also try out Slim Framework.
I see it being used since over 25 years for the Austrian national broadcaster. Based at least originally on rhino, so it's also mixed with the Java you love. Fail to see the big issue as it's working just fine for such a long time.