161–170 of 272 posts
I wonder how hard the last 10% will be? If its a typical software project its going to be 90% more effort for the last 10%.
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.
That's just a tired thrope that keeps being repeated by people who don't know any better.
Earlier quoted context omitted.
AFAICT, Chrome and Firefox on iOS are still just WebKit wrappers. I’d love for that to change though, WebKit in iOS sucks in quite a few ways.
such as? I consider myself a power user and I've never run into anything I couldn't handle or get around. Genuinely curious.
Earlier quoted context omitted.
> Chrome can push back against proposals The problem isn't Chrome pushing back proposals. The problem is Chrome pushing ahead with its own proposals regardless of anyone: https://news.ycombinator.com/item?id=45371575
OTOH, are all of the browsers supposed to move in lock step? Is chrome supposed to wait for everyone else's approval before launching any kind of feature?
Otherwise you get Internet Explorer, in reverse: https://www.quirksmode.org/blog/archives/2021/08/breaking_th...
Chrome literally doesn't even bother pretending that many of their proposals are more than some scribbles in spec-adjacent format. E.g. a spec for WebHID that other browsers could implement was just dumped into the repo after Chrome shipped it.
Constructable Stylesheets had both a badly named API and a trivially triggered race condition. Shipped in Chrome in the middle of discussion because Google-developed lit "needed" it.
And so on and so forth.
Earlier quoted context omitted.
> Chrome can push back against proposals The problem isn't Chrome pushing back proposals. The problem is Chrome pushing ahead with its own proposals regardless of anyone: https://news.ycombinator.com/item?id=45371575
OTOH, are all of the browsers supposed to move in lock step? Is chrome supposed to wait for everyone else's approval before launching any kind of feature?
Earlier quoted context omitted.
I believe they are or will be transitioning to Swift: https://x.com/awesomekling/status/1822236888188498031
This is often cited, but it seems like there has been very little movement toward swift since this tweet.
To me that all sounds like wishful thinking on their part. But I have a lot of faith in Andreas and the team, so I'm willing to take their opinion over my knee-jerk reaction shrugs.
As someone who's been quite heavily involved with web-platform-tests, I'd caution against any use of the test pass rate as a metric for anything. That's not to belittle the considerable achievements of Ladybird; their progress is really impressive, and if web-platform-tests are helping their engineering efforts I consider that a win. New implementations of the web platform, including Ladybird, Servo, and Flow, are ex…
Why are you bringing this up, when it’s not been implemented as a metric here, but because Apple requires it for iOS.
Earlier quoted context omitted.
such as? I consider myself a power user and I've never run into anything I couldn't handle or get around. Genuinely curious.
Web devs make huge efforts to work around WebKit's issues. It's the new IE6.
Earlier quoted context omitted.
AFAICT, Chrome and Firefox on iOS are still just WebKit wrappers. I’d love for that to change though, WebKit in iOS sucks in quite a few ways.
such as? I consider myself a power user and I've never run into anything I couldn't handle or get around. Genuinely curious.
Earlier quoted context omitted.
Three years ago I was very skeptical of Ladybird. But two things have changed. First, they have funding for 8 full time engineers, which I definitely wasn’t expecting. Second, it’s been three years. So given that, I am more optimistic. There’s still a very long way before they can compete with Chrome, of course. And I’m not sure I ever understood the value proposition compared to forking an existing engine.
The value proposition is not having vendor lockin and having WebKit/Blink be the defacto behaviour. For example the Ladybird team have found and raised spec issues in the different specs. Another example is around ad blockers -- if Blink is the only option, they can make it hard for ad blockers to function whereas having other engines allows different choices to be made.
It’s that Chrome and V8’s implementation has grown to match resourcing. You probably can’t maintain a fork of their engine long-term without Google level funding.