Don't confuse browser vendors with the people creating and abandoning frameworks left and right. I like the part of the HN guidelines that refers to something

Don't confuse browser vendors with the people creating and abandoning frameworks left and right. I like the part of the HN guidelines that refers to something in particular being "a semi-noob illusion". The fragility of the web is like that: a semi-noob illusion that people come away with because they don't understand the layers underneath and who's responsible for what. The web has robustness and forward compatibility baked in. TC-39 in particular, which is responsible for defining "JS", even operates with the unofficial motto "don't break the Web". I'm also fond of this comment from Roy Fielding: > As architectural styles go, REST is very simple.¶ REST is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directly opposed to short-term efficiency. Unfortunately, people are fairly good at short-term design, and usually awful at long-term design. Most don't think they need to design past the current release. https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...