I feel you. I have worked on an Angular project for over a year and was miserable working with it (and I _really_ tried to like it).
At first glance it seems "complete", but once you start building there's just so many insane edge cases that don't work well or have bugs. I also think that "integrating" RxJS was a mistake, while I get it and it's nice, it's imho too low level of an abstraction if you have many people that don't necessarily want to learn all the details (easy to shoot yourself in the foot with it), too different from anything else in JS, and too poorly integrated into angular.
And also the verbosity of everything.. was too much for me.
It's a bit weird to me that they're going with intel, is the new i7 better than ryzen processors if you count in energy efficienty (and thermal output)?
If you had to pick a multiplatform solution (for whatever reason) which one would you pick? I've been exploring this space a bit, and it's really hard to form an opinion on this.
It's all nice, but where does the base load come in? From what I know Germany is decomissioning their reactors, and is replacing them with NEW coal power plants + importing energy from other countries (which is just sidestepping the problem)
What's the real solution here? If all countries did what Germany does, we'll have a lot of coal power plants, why not instead have nuclear ones? I don't know a lot about this topic, but it seems to me there isn't any viable solution here, even if nuclear costs a lot.
Couldn't you do the same thing with class components though? From what you've mentioned it seems you've mostly moved complicated logic into reducers. I may misunderstand though.
They don't compete in the local talent market, they compete in the global talent market while offering local compensation. If they have a physical office, then they actually compete in the local market.
edit: I mean have an office and require to work from there. Companies which have an office and offer remote are naturally at a disadvantage here in the same way, though having an office may help offset the disadvantage (some people don't want to work remotely, having an office to go to from time to time and talk to people, meetings, integration parties, other benefits)
edit2: I've also just checked their rates, and for my region they are at best average even accounting for local market prices. So I don't see how they have an attractive offer in any way.
I know they have their reasons, and it may even work for them, but I really loathe their location dependend compensation (as a person living in one).
I think their explanations don't hold water. For eg. they actually compete with other remote companies for people working in what they consider "low-wage regions", but those companies pay the same rates for everyone. So they won't get top engineers from those regions, since those engineers can work in other remote companies which pay more (and don't discriminate people based on location).
I think the sleepiness in meetings is mostly related to lack of fresh air. I remember reading some articles that the air during meetings (talking about physical meetings in rooms here) has a very high CO2 count.
Which is the same thing that a virtual DOM does, it also has to have an adapter(react-dom in Reacts case) which applies the VDOM to the real DOM via it's imperative API.