3 ms·
What quirks? There was a time when you had to essentially make different websites for IE, Chrome, Firefox etc. Even without JS, CSS layout and HTML tags were in
by paxys 6y ago
What quirks? There was a time when you had to essentially make different websites for IE, Chrome, Firefox etc. Even without JS, CSS layout and HTML tags were interpreted very differently by each one. Browsers have become a lot better at adhering to standards as time goes on.
- amelius 6y agoYes, but there is absolutely no guarantee that the browser will run a JS file from X years ago flawlessly.
- paxys 6y agoThere's also no guarantee that browsers will render HTML and CSS as it exists today in 10 years. Maybe all of the internet should just be ASCII text then (if there even is a guarantee of that)?
- amelius 6y agoWe should distribute software in a way such that its dependencies are completely described. So when we pull something from the internet (be it a JS file or some HTML), the system will know what other software to pull and it will just run. The current way of doing things works most of the time, but it is fundamentally flawed, which becomes apparent when viewing stuff from a decade ago.
- erik_seaberg 6y agoAre there any HTML 2.0 documents that aren't usable 25 years later?
- Kaze404 6y agoJavascript is designed to be backwards compatible, always. You can visit a website made 20 years ago and all the APIs it uses will still be there.
- z3t4 6y agoUnless it uses some IE, Firefox or Chrome specific API. Or standard API's that has been deprecated. API's are constantly being added and removed.
- Kaze404 6y agoWhich APIs that were part of the ECMA standard were removed? As far as I know the only APIs that get removed are the ones that get implemented outside of the standard, and are later deprecated. That's fault of the developer, not of the technology.
- z3t4 6y agoSearching for site: developer.mozilla.org "deprecated" should reveal some deprecated browser API's and JavaScript stuff. I think the Chrome team wait until less then two million sites use something before removing it. For example sync XHR is currently on the deprecation list and will be removed once the usage is low enough. If sync XHR is removed you can no longer sync load modules on the web.
- cxr 6y agoDon'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...