41–50 of 293 posts
Earlier quoted context omitted.
> but a lot of popular sites don't even work with Firefox Which ones? I have always exclusively used Firefox and rarely have issues.
I can't get Reddit to work in Firefox or Chromium. No idea why.
I would love to use this as my daily driver, but a lot of popular sites don't even work with Firefox. I hate what a small group of lazy front-end people have done to our world...
I would love to use this as my daily driver, but a lot of popular sites don't even work with Firefox. I hate what a small group of lazy front-end people have done to our world...
Shopify is a sponsor! I wonder how that came about.
See https://awesomekling.substack.com/p/welcoming-shopify-as-a-l... Discussion: https://news.ycombinator.com/item?id=36502433 (246 points | 7 months ago | 66 comments)
Earlier quoted context omitted.
The whole point of the project is to write a completely independent browser from scratch. The effort seems focused to me, write a complete engine. Not write a small part of a browser. But why would reusing something be better? Reusing someone else code wouldn't be competing with them, it'd be depending on them.
Because you can have something usable instead of dreams. If you want to have completely independent code eventually, then replace modules one by one, while having a working product. Like Mozilla did with Servo. They had C++ codebase they wanted to replace with Rust codebase. They did not create entire browser from scratch, but replaced C++ with Rust gradually. While one figures what HTML and CSS layout should look li…
However, the thought has also crossed my mind if we're finally seeing fruits of browsers being better standardized on "95%"+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back. While the web is of course still evolving, it feels more "settled in" than 10-15 years ago.
There's also the factor that past developers didn't have the more complete roadmap set when they initially planned browser design, but now we have huge amounts of web standards already there AND also know how popular they got over time i.e. what to prioritize to support a modern web. One might superficially think there's simply more of everything, but I also think ideas that can be discarded. Just imagine that Internet Explorer had XSLT support, and FTP was common once upon a time!
It would be interesting to hear more about their own thoughts on these topics!
Edit: My bad; XSLT is still commonly supported and by all major browsers but a rarely used feature and stuck in limbo in XSLT 1.0. So it's probably among those things that can be safely omitted for quite some time.
I would love to use this as my daily driver, but a lot of popular sites don't even work with Firefox. I hate what a small group of lazy front-end people have done to our world...
It's really quite incredible that one guy basically started a project to create a whole operating system from scratch for fun and to give himself something interesting to do, and then accidentally created one of the most viable new browser engines in a decade or two... I've been watching the development videos for a year or two, and the speed that this has progressed in such a short time is unbelievable. Now they hav…
I can’t tell from the link. What makes it so viable?
Ladybird also comes with their LibJS runtime, which has good coverage of the JS standards and even manages to implement some new features before the big browsers all get to it.
[flagged]
Why write Servo from scratch instead of porting Blink/Webkit? One could at least use the HTML/CSS layout manager. Seems like a waste of effort.