8 ms·
The analogy is simple: back in the day devs got sick of IE because it was the one thing holding them back. You can make a site, easily, that looked beautiful on
by hn_throwaway_99 5y ago
The analogy is simple: back in the day devs got sick of IE because it was the one thing holding them back. You can make a site, easily, that looked beautiful on all the other major browsers, but because IE was outdated when it came to standards support, you had to basically spent all your time fighting with it.
Safari serves that role today. There are tons of things I'd love to do but can't because they're not supported on iOS Safari.
- blub 5y agoBack then there were many browsers and many actors involved in developing web standards. It was justified to criticise laggards. Nowadays the Microsoft browser, Opera and others are just Chrome skins. Google is pushing various drafts and essentially dictating web standards and then even when a browser like Firefox does support those Google flavoured standards, it still gets blocked outright on new Google products or gets a limited feature set on existing ones. Or it gets hobbled by Google oopsies. Why would anyone want to play in such a rigged game...
- hn_throwaway_99 5y agoYet I don't have a problem supporting Firefox, or honestly even desktop Safari for the most part. It is specifically iOS Safari that is being deliberately held back by Apple to protect their App Store monopoly.
- wwarek 5y ago100% that, happens regularly. The most recent case being lack of `scrollIntoView` options[0], so smooth animations work everywhere but Safari. You have to go and hack/implement that manually just for Safari. [0] https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView https://developer.mozilla.org/en-US/docs/Web/API/Element/scr...
- veeti 5y agoIt's always fun when some bog standard 2010 flexbox layout works perfectly in every modern browser until someone on an old iPhone tries it. Android has its own update woes to say the least, but at least Chrome receives evergreen updates through the Play Store. Why can't Apple do the same?
- tarsinge 5y agoSafari is not holding back, Safari is just not implementing Google’s PWA (because it doesn’t really make sense on Apple devices where it would be far inferior to native). You can make a beautiful site in Safari and it will work everywhere (I do professionally). Chrome is the new IE (2001 era, when it was cutting edge and pushing proprietary technology) except ActiveX is PWA.
- tehbeard 5y agoSafari can't even implement a key value store (indexedDB) correctly... We had whole versions where it was basically stuffed, and even in the recent versions, I'm getting random errors where it just refuses to write to disk. If they don't want to implement PWA, fine, their walled garden and wall that, claim it's for privacy etc etc. just don't half ass all the APIs around it then! Leave them out!
- cuddlecake 5y ago> We had whole versions where it was basically stuffed A co-worker asked me "uh, why does the app use 120GB for indexeddb?" Wildest bug I've ever had to deal with. Unfortunately it wasn't even just a safari issue.
- kristiandupont 5y ago>it doesn’t really make sense on Apple devices where it would be far inferior to native Yeah, I get that it doesn't make sense for Apple, business wise -- which is why they are not doing it. But it sure would make sense to developers.
- LAC-Tech 5y agoIt makes zero business sense for small-medium companies to make separate android and IOS apps. That's man hours that will be spent on a specific platform and its app store, instead of on improving the core product. PWAs are here to stay.
- tarsinge 5y ago
- lucideer 5y agoBut that isn't the case. At all. IE wasn't difficult because it was behind the times; it was difficult because it was deliberately different. The 2nd pillar of Microsoft's infamous Embrace, Extend, Extinguish strategy ensured incompatibility, which doubled developer efforts. The idea of IE being purely an "outdated" browser seems to be one perpetuated by young devs reading & misunderstanding old blogposts. The narrative is attractive because it fits the impatient desire be an early adopter of "shiny new thing", but it doesn't match the reality of how IE6 actually worked. Safari is compliant. It's behind but compliant. That makes it incredibly easy to develop for because backward compat. & progressive enhancement work well if you're not too lazy to develop according to well-known best practice. What doesn't work well is the spec. du jour that the Google have just added to Chrome before submitting to a standards body and are proceeding to use their monopoly position to pressure other browsers to adopt. That's IE6 behaviour.
- Touche 5y agoYou're concentrating on the time period when IE was the only game in town and ignoring the 10 or so years post Firefox/Chrome (until basically they switched to Chromium) when it was behind the times and was a tremendous drain on web development. Any attempt to say that otherwise is just wildly incorrect.
- The_Colonel 5y agoAt the time of their release IE4-IE6 have been the most standard-compliant browser. IE was also the fastest at the time. Netscape was in a technological dead-end, and it took considerable time until its complete rewrite (Netscape 6/Mozilla/Firefox) stabilized and caught up. The biggest problem was MS simply dropping its development (IMHO their biggest strategic blunder of 2000s). Back then all browsers had unstandardized behavior, there was plenty of Netscape specific and IE specific hacks. Some of them were intended as EEE, some of them were result of weak standardization or mere technical limitations of their respective architectures.
- lucideer 5y ago> At the time of their release IE4-IE6 have been the most standard-compliant browser At the time of their release, Opera was the most standards-compliant browser. Beyond Opera, I'm not sure where Firebird, KHTML, etc. stood relative to IE4 specifically, but IE5.5/6.0 were well behind most contemporary browsers (lets exclude Netscape shall we; it was in crisis at the time and promptly discontinued). Opera, KHTML, Firefox and Webkit all passed Acid2 long before IE (IE8 was the first version). It's worth remembering that Acid1 was released in 1998; IE6 was released in 2001. So this wasn't a time before web standards and cross-browser compat: they were very much a part of the discourse at the time. A discourse MS largely refused to participate in. > Back then all browsers had unstandardized behavior, there was plenty of Netscape specific and IE specific hacks. Some of them were intended as EEE, some of them were result of weak standardization or mere technical limitations of their respective architectures. That is true, but it was largely due to bugs other browser makers were working on fixing. The EEE had a heavy influence on MS' motivations to get fixes out (whereas with Safari there isn't really any evidence of any EEE being present). A good counter-point is XMLHttpRequest. It was non-standard mainly because "AJAX" was a new-ish idea and standards didn't exist. There's good arguments that Microsoft's engagement with standardisation efforts of AJAX APIs was non-existent/actively-hostile, but at the end of the day the various APIs they implemented were pretty easy to detect (even the ActiveX variants), and generally could be targeted in a very cross-browser-compatible way. That was very much the exception to the rule though: the majority of pains were layout related, and involved not extra nor missing features, but rather features that were in common with other browsers that were deliberately implemented in a different way.
- thecupisblue 5y agoWas just fighting Safari few days ago and I completely agree. Noticed that "vw" and "vh" CSS3 units dont work in it like they do in other browsers. Upon digging, found a medium article explaining it - but as I was in safari, the article's code snippets or images wouldn't load properly. As much as I got a bit hyped to try using safari after WWDC - I just can't. It's so discombobulated regarding web standards that I wonder if it can even count as a "web browser" any more than emacs can.
- pwdisswordfish8 5y agoThe problem also is web developers themselves, with the author of this piece and the Redditor they quote included. Whatever Medium's needs are for putting images and the written word on the screen were satisfied a decade+ ago. The fact that that Medium article doesn't work is a consequence of how web developers have normalized the practice of passing the blame for their failures and lack of competence on to the browsers and browser makers by extension. We shouldn't even use the term "web developer". The entire industry, bolstered by analogizing themselves to mobile app programmers, have snowed the world and warped expectations that they are or should be anything other than experts in digital content publishing. The entire notion of "full stack" (which embodies a lie in the very term) should have never even happened. If we really want to pick bones, where the engineers working on web browsers and "web developers" are both fair targets, then the overwhelmingly pressing matter would have to be how the latter are a piss poor substitute for anyone competent the skills they should possess, which would involve library and information sciences and a smattering of practical tech discipline. The industry is a perfect example of the rampant "consultant effect", where people create massively complicated stacks that often don't accomplish anything that their forebears couldn't manage, and then get paid bloated salaries for mastering the tools and workflows that are ostensibly meant to solve the very problems that they are responsible for foisting onto the world in the first place.
- naravara 5y ago> The industry is a perfect example of the rampant "consultant effect", where people create massively complicated stacks that often don't accomplish anything that their forebears couldn't manage, and then get paid bloated salaries for mastering the tools and workflows that are ostensibly meant to solve the very problems that they are responsible for foisting onto the world in the first place. Organizations want to buy a solution to their problem instead of reorganizing themselves to develop the fundamentals required to not have the problem. It's like managing your back-pain with pain killers without actually doing any physical therapy or lifestyle changes to fix your body mechanics. It's a temporary solution that puts you on a ladder to needing ever more intensive interventions.
- agloeregrets 5y agoSafari isn't that. Old edge, IE, and FF are that. Safari is WAY closer to chrome than IE ever was.
- bromuro 5y agoThe amount of pain we had with IE is not even comparable to the sweet issues we may have with Safari. Who survived those times, with the evil F12 debugger, can confirm. Safari is a joy to develop with and it sucks I have to switch to chrome for its extensions.