[flagged]
[dead]
[flagged]
Ladybird passes the Apple 90% threshold on web-platform-tests
221–230 of 272 posts
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#222Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#223Earlier quoted context omitted.
So it's okay for a website builder to test in only one browser defaulting to an imposed browser/agent restriction?
The point is they are not even compliment to their "own" spec. They are part of whatwg. But if you ever write web page. You will know it's always the safari that differs from the spec. Firefox in the other end never have such issue. Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari. Supports safari literally means support another browser (by workaround all its bugs).
> The point is they are not even compliment to their "own" spec. They are part of whatwg.
I think web devs have too much faith in the "standard"; the WHATWG specifies anything supported by two implementations, and with Google controlling Mozilla that already feels somewhat unfair...
> Write a page on chrome, works 90% on Firefox. But will likely works 10% on safari.
Disregarding the issue that you're writing pages that only 90% work on anything but Chrome... do you have any examples of Safari misbehaving?
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#224The WPT score is a flawed metric (encoding tests are overweighted), but it's one of the few objective yardsticks we have. What matters more is that Ladybird is finding spec ambiguities by implementing from scratch rather than cargo-culting Chrome's behavior.
The real test isn't passing 90%—it's whether they can keep pace as the web platform adds new APIs faster than any independent team can implement them. Browser engine development has become a regulatory moat, and breaking it requires either massive funding or accepting permanent incompatibility with the "modern web."
Still rooting for them. Browser monoculture is worse than metric gaming.
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#225The WPT score is a flawed metric (encoding tests are overweighted), but it's one of the few objective yardsticks we have. What matters more is that Ladybird is finding spec ambiguities by implementing from scratch rather than cargo-culting Chrome's behavior.
The real test isn't passing 90%—it's whether they can keep pace as the web platform adds new APIs faster than any independent team can implement them. Browser engine development has become a regulatory moat, and breaking it requires either massive funding or accepting permanent incompatibility with the "modern web."
Still rooting for them. Browser monoculture is worse than metric gaming.
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#226Along the same lines, the State of Utopia will be building a free web browser for everyone, once AI is strong enough to do so. Please feel free to vote on feature ideas here: https://pollunit.com/polls/ahysed74t8gaktvqno100g
> teleports the founder and his wife to the same location so they can be together in person holding hands - they're already in the same same city and want to meet immediately, so they are 99.98% of the way there! They're both working 10 hours a day to bridge the remaining 0.02%. Following this proof of concept, other people will also be allowed to date, however at the moment all dating is prohibited until the founder…
I didn't originally include this text in the browser feature vote, but I showed my wife the feature vote and she insisted that I need to include this part until it's solved. I can't wait for this to be done.
I didn't see any feature suggestions from you, please feel free to suggest a browser feature for AI to build once it is powerful enough to do so, you can do so at the bottom of the page. It only takes a few seconds. Thank you.
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#227Earlier quoted context omitted.
Why are you bringing this up, when it’s not been implemented as a metric here, but because Apple requires it for iOS.
This is a headline that is very easy to misread and or misunderstand. I don’t find their comment to be that out of place at all.
[deleted]
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#228Earlier quoted context omitted.
Why are you bringing this up, when it’s not been implemented as a metric here, but because Apple requires it for iOS.
This is a headline that is very easy to misread and or misunderstand. I don’t find their comment to be that out of place at all.
Root comment is lecturing the ladybird team about not using this suite as a metric, which is totally uncalled for. That’s what I’m trying to convey.
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#229Earlier quoted context omitted.
Browsers have been historically the biggest and most difficult projects, so hard to say why it wouldn’t be. When they can start promising 20k bounties for segfaults, they are getting close.
They are pretty far way from that. I still think it is one of the most exciting open source projects in recent years.
As someone who has first encounter with the ladybird - why is it exciting?
And how could ladybird attract so many sponsors for such a project? Why wouldn't they fund Firefox instead if they want to achieve some diversity in browser engine field?
I'm curious, not skeptical.
Re: Ladybird passes the Apple 90% threshold on web-platform-tests
#230What's the security story in Ladybird? Do they use sandboxes etc? I'm a bit concerned that hundreds of thousands of lines of C++ browser code written in just three years could be a minefield, but I hope I'm wrong.
Last I heard they were planning to move to Swift [1] partly because of the safety features. Apparently there are still some blockers [2] preventing that move though.