> Though I could just be wearing rose colored glasses. > al_borland Borland had a nice and not complex solution. Which made for very fast, low latency interfa

> Though I could just be wearing rose colored glasses. > al_borland Borland had a nice and not complex solution. Which made for very fast, low latency interfaces. Everyone starts crying when you don't have the react, downward reactive (well, for some definition of this leaky abstraction thing they call reactive because javascript doesn't support anything to help), but with simple events, getters and setters it was much much clearer what was happening every tick and you could optimise, even as junior, accordingly because everyone gets it all after 10 minutes of tutorial of how it works. I have seniors asking me (every few days) why something doesn't or does update in react or why it's so slow to input something in a field in react (we fix or patch horrible software for a living, so we see 100s of different companies over the months / years; these are not the same seniors asking me this; there are very very few people actually understanding how it works and how not to crash and burn because it LOOKS like you can do something in 'this way' (even on the official react site), but when you do it, you machine gun yourself in your legs). Not to mention that you would end up with a consistent UI with shortcuts that every user could use immediately instead of the shitshow of 'designer' choices.