News for hackers. Stuff that matters.
Re:The baseline for web development in 2022 by heavyset_go on Thursday January 27, 2022 @04:32PM (#30107035)
> Does Safari suck because it's not supporting actual standards, or does Chrome suck because it's trying to make sure that the web only works on Chrome

This is a weird argument when Firefox supports many of the standards that Safari doesn't, as well.

Re:The baseline for web development in 2022 by mrtksn on Thursday January 27, 2022 @05:05PM (#30107500)
It's not really weird at all, that's actually what happened with IE. It wasn't that IE was lacking but people used it anyway, IE was doing really cool stuff but in it's own way.

AJAX is one example, IE introduced XMLHttpRequest back then and it took 15 years to become a standart. So people built their cool websites around IE features that were not actually standards and once Microsoft screwed up IE people found out that you can't switch to alternative browsers because websites were built to support IE.

As the IE experience degraded(has become famous for crashing and taking the OS with it) and there was a room for improvement, Netscape become Mozilla and they introduced actually good browser that later will become Firefox but because most people used UI, web developers had to accommodate IE by writing IE specific code everywhere. That's where the hate for IE comes from, it wasn't fanboys hating IE, it was developers hating IE because they had to write extra code all the time.

Firefox may support some Chrome features but how sure you are that Google will keep making a good browser? For many, Chrome is already a degraded experience for what it was and it is actually very nasty in favouring Google properties and tracking that can be a disaster if switching away from Chrome becomes as hard as it was with IE.

Re:The baseline for web development in 2022 by darklion on Thursday January 27, 2022 @04:38PM (#30107117)
Or is Firefox willing to compromise on more technologies that aren't yet standardized than WebKit is?

Without knowing whether the "standards" being tested are actually standards, it's impossible to know.

Re:The baseline for web development in 2022 by account42 on Friday January 28, 2022 @04:01AM (#30112309)
Firefox has been copying Chrome for a long time now. Either Mozilla doesn't believe that they have the market share to succesfully challenge those "standards" (I think its the other way around, they keep loosing market share because anyone who wants Chrome uses Chrome) or they don't want to risk their primary funding source. Either way, something being implemented by Firefox does not mean that WebKit has to implement it too.
Re:The baseline for web development in 2022 by imachine1980_ on Thursday January 27, 2022 @04:48PM (#30107224)
not some of the tools are propose or standard some of then from Mozilla foundations and try to be implemented safari tend to implement standard a lot more slow than the other because this isn't the core business, and let browsers do more things and you don´t need to use the app store.
Re:The baseline for web development in 2022 by pjmlp on Thursday January 27, 2022 @04:44PM (#30107166)
Mostly because it is the only way to still be relevant, and as the charts prove it is not doing a great job at it. Typing this from FF by the way.
Re:The baseline for web development in 2022 by account42 on Friday January 28, 2022 @04:09AM (#30112357)
I think blindly copying Chrome in so many ways is actually making Firefox less relevant.