21–30 of 349 posts
What we all REALLY care about: they went with C++ and Qt https://github.com/SerenityOS/serenity/tree/master/Ladybird
The version of the browser native to SerenityOS hopefully still uses the SerenityOS GUI libraries
I think a potentially interesting use case for Ladybird is as a "contenteditable" polyfill. With their dependancy free stack I'm guessing it's not out of the realms of possibility to compile it to WASM and HTML canvas. Having to only target one rendering engine when developing a rich text editor would be much better than the current nightmare it is. (There would be an accessibility problem to solve, we need some new…
I'm finding it weird that unlike other non-trivial projects like OSes or compilers, people often discourage building web browser engine because it is "hard" or something like that like... how is it different from building a compiler? You gotta build HTML parser, CSS parser, figure out a fancy structure to represent those concepts and modify at fly. Also there's difference between making it work and making state of th…
I’m only half joking but I’m pretty sure there are some PR companies pushing “trends” on the behalf of big corps.
It would be stupid and uncapitalist not too…
Building a web browser is a difficult, but attainable task. On the other hand, getting the UX right is a gargantuan task that even big tech struggle with.
I'm finding it weird that unlike other non-trivial projects like OSes or compilers, people often discourage building web browser engine because it is "hard" or something like that like... how is it different from building a compiler? You gotta build HTML parser, CSS parser, figure out a fancy structure to represent those concepts and modify at fly. Also there's difference between making it work and making state of th…
You forgot about the rendering and the user interaction.
I'm finding it weird that unlike other non-trivial projects like OSes or compilers, people often discourage building web browser engine because it is "hard" or something like that like... how is it different from building a compiler? You gotta build HTML parser, CSS parser, figure out a fancy structure to represent those concepts and modify at fly. Also there's difference between making it work and making state of th…
A browser that's unfinished really cant be used by users at all. Either it lacks security, so nobody should use it, or it lacks vital features (of the spec, not end-user features), so nobody can really use it because every time a website relies on that API something doesn't work.
Chrome wasn't built in a day.
What we all REALLY care about: they went with C++ and Qt https://github.com/SerenityOS/serenity/tree/master/Ladybird
Another aspect is that for any complex, large-scale project like browser, lots of, if not most of, effort is actually in the long tail: to make 90% or even 99% websites work probably is as hard as making the rest 1%.
So while the team probably could cruise through when working on current gen spec and popular sites like Discord/Twitter, it's what left is going to be a nightmare to manage at the end.
But again, nothing is impossible, and I really look forward to having a new browser engine in the wild.