5 ms·
Passing Acid3 is a nice milestone, but realistically that's a 16-year-old test without modern performance requirements. $1 million is wild for an open-source ho
by pornel 2y ago
Passing Acid3 is a nice milestone, but realistically that's a 16-year-old test without modern performance requirements. $1 million is wild for an open-source hobby project, but sadly it doesn't buy many person-years at competitive salaries.
For Google and Apple browsers are loss leaders for their bigger business, so they have infinitely deep pockets to play Fire and Motion[1] with each other by adding more and more stuff to the platform, and setting higher and higher performance and security/privacy goals. Once you implement the first 90%, there's the harder second 90% to implement, and the goal keeps moving. And that's before you even have to waste time fighting bug-compatibility caused by the Chromium monoculture and Google's "oopses" serving non-broken code only to Chrome.
[1]: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
- khimaros 2y agoit seems to me that, if we could clearly define and document a useful subset of browser features, and start targeting that, it would help tremendously with long term viability and sustainability of hobbyist browser implementations. maybe starting with what dillo supports today?
- klysm 2y agoThat’s terrible for developers though. It’s already a moving target and having several moving targets to pick from doesn’t sound fun
- rererereferred 2y agoSounds more like the subset would be a static target that you could confidently assume that works. Which is sort of what I expected from AMP and Gemini.
- klysm 2y agoHow could it be a static target though? That doesn't seem practical.
- khimaros 2y agoif it is a strict subset, why is that harder?