I might sound jaded, but I'd be more excited for a Chromium fork that focuses on hackability instead of a brand new browser that'll take somewhere between years to ∞ to be even remotely useful. I get why that'd be less fun to work on though.
I'm forking Ladybird and stepping down as SerenityOS BDFL
41–50 of 280 posts
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#42I might sound jaded, but I'd be more excited for a Chromium fork that focuses on hackability instead of a brand new browser that'll take somewhere between years to ∞ to be even remotely useful. I get why that'd be less fun to work on though.
Isn’t there already quite many Chromium forks? They all have the same issue - the more your code diverges, more additional work it will be. And security patches start lagging.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#43Feels like an end of an Era, I used to enjoy Andreas's SerenityOS YouTube videos as he dropped down and implemented different features of the OS during a video coding session, adding code from UI, emulators, game ports, JS & Jakt programming languages, JITs all the way down to the kernel. SerenityOS was unique in that regard with the entire code-base maintained in a single source tree.
I expect interest in SerenityOS will now taper off as a result of this, especially now that SerenityOS is no longer a target for Ladybird.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#44This could be a good move, if it frees resources that would then be allocated for the OS itself. To me SerenityOS as a x86 OS is interesting but redundant, while to me would immediately catch attention if ported to ARM or RISC-V and other embedded platforms.
Many companies already use sluggish Android or web based solutions to build instrumentation screens and other vertical applications where one needs to show GUI primitives, and to me a native, fast alternative is badly needed. SerenityOS doesn't bring all the cruft that would be completely unnecessary in those systems, hence my idea that in some cases it could become the right tool for the job.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#45> Ladybird now targets Linux and macOS. The SerenityOS target is dropped. Why dropping the SerenityOS target?? Does this mean that SerenityOS's Ladybird will need to continually pull patches from the new Ladybird project in order to keep development? Also: is it really a fork if the new project gets to keep the name "Ladybird"? Will SerenityOS's browser need to be renamed, or there will be two diverging Ladybird proj…
SerenityOS's browser has never been named Ladybird AFAIK, it's always been just Browser. https://github.com/SerenityOS/serenity/tree/master/Userland/... Ladybird was the name used for to the cross-platform version of the browser. https://awesomekling.github.io/Ladybird-a-new-cross-platform...
Would it be fair to assume this means the SerenityOS maintainers will have to pull LibWeb/LibJS changes in from Ladybird?
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#46[flagged]
It should be fairly straightforward to get it running on any mainstream *nix system. I only called out macOS and Linux specifically because we have developers actively using those systems day-to-day. :)
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#47Ladybird looks amazing and is moving quickly. Without the linkage to SerenityOS, I even feel like looking at the source and seeing if I can get a handle on what's going on.
Looks like the idea of writing a new browser engine, or of forking Firefox, wasn't an absurdly impossible thing that would require billions of dollars. If this inspires somebody to take up that charge again, or to pick up Servo from the table, that would be wonderful too.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#48Feels like an end of an Era, I used to enjoy Andreas's SerenityOS YouTube videos as he dropped down and implemented different features of the OS during a video coding session, adding code from UI, emulators, game ports, JS & Jakt programming languages, JITs all the way down to the kernel. SerenityOS was unique in that regard with the entire code-base maintained in a single source tree. I expect interest in SerenityOS…
It was a journey for sure. I never contributed code, but color schemes and emojis. But I always enjoy Andreas' Serenity videos, even some coding videos were good (I cannot code). These are special and will forever live in my heart.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#49> Ladybird now targets Linux and macOS. The SerenityOS target is dropped. Why dropping the SerenityOS target?? Does this mean that SerenityOS's Ladybird will need to continually pull patches from the new Ladybird project in order to keep development? Also: is it really a fork if the new project gets to keep the name "Ladybird"? Will SerenityOS's browser need to be renamed, or there will be two diverging Ladybird proj…
I think the fork has to do with the following item:
> Unlike SerenityOS, Ladybird will have a relaxed NIH policy (instead of "no 3rd party code!"), and will leverage the greater OSS ecosystem.
SerenityOS wants to be an OS from scratch, to see how to do things better from existing implementations. When ladybird wants to target that OS as well, using 3rd party libraries would make it hard to stay compatible. Which is easier to do on just MacOS and Linux.
Re: I'm forking Ladybird and stepping down as SerenityOS BDFL
#50[flagged]
I hope there will be also a Windows port someday :P