> 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 projects with the same name? (Maybe a qualifier would help, like SerenityOS Ladybird vs Open Ladybird or something?)
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.
SerenityOS' browser began identifying itself as Ladybird last year or the year before in the UI, the folder was always called Browser.
It'll probably just be renamed back, or the "port" of Ladybird will always be built as part of the base system (which would make sense, so Serenity could continue getting updates to LibWeb and LibJS)
> Does this mean that SerenityOS's Ladybird will need to continually pull patches from the new Ladybird project in order to keep development?
It will probably mean that Ladybird becomes a port. As for what happens to the LibWeb that's in SerenityOS right now, that's still undecided.
> 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 projects with the same name? (Maybe a qualifier would help, like SerenityOS Ladybird vs Open Ladybird or something?)
SerenityOS' browser will probably go back to being called "Browser", like it was before.
As mentioned by Andreas, it's because SerenityOS does not depend on third party libraries and part of the new ethos of Ladybird is to decrease "not invented here" syndrome.
because the main focus on serenityos is writing code. hence no 3rd party code policy. the fork is mostly to make the browser use 3rd party code, hence it is now no better than just porting Mozilla. i think this will fork both forever
the writing has been on the wall for a long time (as the post mentions too). I'm cynical so I think to some extent it's related to the fact that writing a browser from scratch has been able to attract significant funding, whereas the operating system has earned a lot of nerd goodwill and small donations but would have a really hard time commercially justifying itself. I think it's a shame because it's a far cooler project, but of course it's not up to me to dictate how others spend their time.
my understanding is that serenity will focus less on the web browser in the first place. it might just go back to being a simple html viewer with rudimentary js support?
my hope is that they take this as an opportunity to come up with a purpose built "web" stack for serenity? use it as an excuse to reinvent the web and "fix" the mistakes that were made? maybe by actually Putting Scheme In The Browser rather than js?
Fill your bowl to the brim and it will spill. Keep sharpening your knife and it will blunt. Chase after money and security and your heart will never unclench. Care about people’s approval and you will be their prisoner. Do your work, then step back. The only path to serenity.
Ok yeah but the thing about the knife is just not true, a knifes not sharp until you de-burr it and if you just continue to grind the edge youre going to just be building a bigger burr and removing metal, eventually the knife will be ground away but thats beside the point. Good knife sharpening does only need a bit of grinding until you reach the grit you want and then de-burr but youre not going to make it dull by continuing to remove metal.
That seems to be a bad translation, the original text means something like “sharpen something fully and it won’t last so long” (presumably due to it being more brittle). The text (like the rest of Tao Te Ching) is pretty vague and doesn’t actually refer to knives, so it could also be read metaphorically.
I was being silly and pedantic but thats an interesting distinction!
I imagine Laozi probably knew how to have sharp knives so I defer to his wisdom as far as 4th century chinese knives go anyways. Perhaps they used a different technique there and then than the type of knife sharpening I'm familiar with.
Sure you will, because a knife blade good enough to hold an edge at all isn't homogeneous.
Good high-carbon steel is harder to make than mild steel. It used to be a lot harder to make; carburization in ambient atmosphere takes an enormous amount of time and fuel, and even then is hit-or-miss.
Because that's so, and also because the brittleness that makes high-carbon steel great for knife edges also makes for a very fragile blade if that's all you use, good knives historically have been made by forge-welding a strip of high-carbon steel to a larger piece of mild steel. The mild steel makes up the bulk of the blade, and the high-carbon strip is shaped and ground to form the edge.
You can sharpen that edge by removing metal, but if you do that enough, you'll remove all the high-carbon steel and end up sharpening the mild stuff. That can't take as good an edge or hold it nearly as long, so you end up with a knife that's dull no matter what you do.
This is also why sharpening steels are a thing, because good knives are usually still made this way. Stropping on a steel cleans up the edge profile without removing metal, yielding a sharper cut without shortening the life of the tool.
Granted, all of this discussion of the mechanics misses the point of the koan, which is all about moderation and humility, and nothing really to do with cleverness beyond the always wise counsel not to let it run away with you. But then, too, moderate discussion of the mechanics may in this case cut toward that end, so I don't really feel this an indulgence to excess.
Thats a good point the knives he was familiar with were probably case hardened! So you would get to mild steel just like you said if you kept removing steel.
Nowadays though, knives are generally homogenous or some other composition like san-mai which will have the good steel in the center all the way through so even if you grind it down to a toothpick most modern knives will still have the good steel on the edge. Modern metallurgy means we can have high hardness, high toughness, high wear resistance and high corrosion resistance all in one composition. See Magnacut and other modern powder metallurgy knife steels:
https://knifesteelnerds.com/2021/03/25/cpm-magnacut/
I am sure there are still some case hardened knives but for the most part case hardening is a historical technique. Same goes for the type of laminated construction you describe above.
All told the metaphor makes sense historically and in context but taken in the context of modern knives it makes less sense. This is interesting in and of itself because the meaning of metaphors and sayings can change drastically across time and social context.
Sure, I guess. I don't really make a habit of pedantry, in the kitchen at least; we both evidently know very well to what tool I referred, and if it means something to you to use one name over another then you're certainly welcome to honor that preference.
No, it wasn't about the pedantry, it was about the fact that they don't really sharpen anything. Honing rods are just used to keep the edge, generally. They won't sharpen a dull knife.
Andreas is a fantastic coder and also a great shepherd of geeks (community builder).
The split makes sense for practical reasons - I also sense he is personally perhaps more passionate about browser hacking than OS hacking (his own contributions were more to Ladybird than to the OS for about a year as he himself writes).
Smart as he is, he may have recognized that he is in a unique position to be able to contribute a cross-platform browser that competes with the big tech companies, where as SerenityOS is essentially more of a toy OS (32 bit, 1990s look and feel, not compatible with important other operating systems, no radically new OS concepts) - without wanting to dimish the contributions of its amazing developers.
IMHO, SerenityOS is more about the process of writing code from scratch than the resulting software itself. Its purpose appears to be 1. to prove it is possible despite the naysayers ("only large tech companies can build a browser", "no-one can build an OS from scratch") and 2. to enjoy the coding itself.
As other commenters have already stated, the only issue will be taking as much from Ladybird over to SerenityOS as possible.
Having watched this over years, and deleted every single comment I've written on it thus far, I'm challenging myself to be honest and forthright.
There's another way of looking at, that is confirmed by the same set of facts:
- There was an OS project run by an awesome dude with a great story that was seen as in a unique position to compete with big tech companies.
- It needed a web browser.
- A web browser project was created.
- Now, the web browser is in a unique position to compete with big tech companies.
- This means it needs to fork itself, and drop support for the OS. That is because the OS project is now a toy.
My last deleted comment mentioned my deep respect for Andreas, and that my next milestone for the browser is downloadable builds and/or moving from pre-alpha to alpha (the downloadable builds was listed as a warning it was in pre-alpha).
I don't like appearing negative or arguably unsupportive, hence all the deleted comments over the years.
But, it's very important to me to make sure there's an accurate signal of what working on your own project looks like. Including the progress rate on things that sound awesome to work on, like an OS or web browser.
I've been dreaming of doing that since I was 17, and it took me 18 years of preparation, predominantly careful observation of successes, and failures, to go out on my own successfully.
I agree, and I think it's worth pointing out. A younger me would have misunderstood complex technical work for business / success. Do it to scratch your own itch, but not for fame/money/fortune. Also worth noting the decision to focus on it is an excellent example of this: do what feels right, rest falls into place.
That's not the nicest way, nor is it the most honest or accurate. I actually do care (and I know I'm not the only one) and even find myself firing up ladybird from time to time. It's probably more accurate to say "few" people care, and caring comes in degrees. Just in case it needs to be said: popularity isn't necessarily a great measurement of salience either.
You're 110% right. Why would any company care about competition from it? Its years away from being real, then it can start trying to build name recognition like Firefox had to. And once all that's done...does it actually do anything different fundamentally that could lead to a qualitatively different experience, like Servo?
There's a certain set of topics that are beyond my ability to explain exactly why they have an aphrodisiac-like appeal to enough commentators that they can't be discussed.
It's dangerous because if you read the threads, all the signal you'd have is "these are important, noteworthy, well-known projects that even get funded!", and anyone making decisions about their own career based on that would be gravely mistaken.
So, you're left with impressions and no facts: you have no idea that its a web browser that you have to compile to use, most people talking about it aren't using it, even as a toy, even one-off.
The multiple engineers hired to help came from a one-off grant from pandemic-era Shopify that thought it was 10x'ing in size, & it was given for absolutely no reason, strategic or otherwise. That would fund, in actuality, roughly 1 engineer for a year, whereas it's lauded as funding that enabled hiring multiple engineers for the long-term.
I waited days to reply to you, because if I voiced anything remotely straightforward on the topic, it'd be downvoted to invisible, which would have just further reinforced the ideas in a reader, it'd look like I was making inaccurate claims.
* quick try: appeals to 'oh it wasn't that hard' we all meet somewhat regularly while programming. Then add the "I could build Dropbox in a weekend" effect. Then throw in "big tech companies suck", and "all web browsers suck", and you want this to succeed. Then throw in "man this guy sure has an awesome personal story, pulled himself up by his bootstraps and recovered!". Without any counter discussion, which is verboten because of the personal story, you're just getting absolutely bombarded with messaging that appeals to your common HN confirmation biases, you can do it, you can break bigco and fix the web/computers/etc.
Ladybird has garnered a level of mainstream attention that SerenityOS never really managed to.
The browser has the potential to impact many more people, and the project is well funded by large investors.
It makes sense that Andreas would shift his focus to LadyBird at this point.
While Safari is busy being Safari and Firefox is busy eating glue in the corner, I'd love to see LadyBird become a real contender in the browser market.
> I'd love to see LadyBird become a real contender in the browser market
At this pace it would likely take decades just for them to be complete enough to show up on MDN or wpt.fyi
But I agree. With Microsoft ditching their independent Edge and becoming Chromium-based and Opera doing the same we're really down to 3 real engines. The best fourth option we can get are Goanna-based browsers like Pale Moon which are themselves just an early fork of firefox
A completely new and fresh often can go a long way in safeguarding the openness of the web. Even if there's not a powerful company behind it
> At this pace it would likely take decades just for them to be complete enough to show up on MDN or wpt.fyi
The important thing to keep in mind with this announcement is that the glacial pace was previously a restriction of being attached to SerenityOS. Everything needed to be built from scratch with no reliance on third party libraries. Now that they're detaching from Serenity they can start reaping the benefits of the existing work in the FOSS ecosystem, which should enable a faster pace of development.
> Now that they're detaching from Serenity they can start reaping the benefits of the existing work in the FOSS ecosystem, which should enable a faster pace of development.
Well, they could build their UI using an existing toolkit, like GTK or Qt. Though, when I previously tested Ladybird it seemed to be using GTK and the current AUR package lists Qt as a dependency, so it seems they're already doing that.
They could also rely on existing multimedia libraries for audio/video (ffmpeg). Those are the main things that jump out to me. There's so much ground to cover that there's probably more, though. Maybe SDL for gamepad support?
It depends what the end goal of Ladybird is. I'd be happy with a browser that just had literally zero telemetry and I could install plugins to block ads.
Some things in other browsers could be used without much pain, e.g. image renderers, JavaScript engines. Things that are totally self contained and can be used until someone writes a suitable replacement.
Ladybird does not have investors, only sponsors/donors. We have received some really generous donations in the past, for example $100,000 from Shopify in 2023 which allowed me to hire a few of our contributors to work full time on the project. :)
Sponsors have no direct influence over the project, but I obviously feel a strong moral obligation to put 100% of the funds towards improving Ladybird and nothing else.
Yeah but one person working 5 years or 5 persons working 1 year isn't likely to be enough to make a modern browser that is feature complete enough to be able to replace the likes of Firefox, Chrome etc.
Apologies, I did mean "well sponsored" not well funded, my mistake :')
You're doing awesome work and I'm really excited for you and the project!
All the best :)
I agree (apart from the popular hate on Firefox). Ladybird is promising and has a much bigger chance to make an impact than SerenityOS.
But it's a bit disappointing to see that it's still pretty much a one-man project. Especially to have a chance to get close to the performance of Chrome and Firefox, it will need a large investment.
The amount of engineering resources poured into just making JavaScript fast is mind-numbing. But even "just" providing a light, mostly standards-compliant browser with a sorta-good-enough performance would be great.
Edit: Just saw a video from a few days ago talking about JS performance. Apparently the target is reaching JavaScriptCore performance, without JIT enabled. Disappointing, but understandable.
I don't think that was intended to be hate on Firefox itself, but hate on the general mismanagement of the project by Mozilla. Firefox itself may not be in the corner sniffing glue, but it often feels like much of the decision-making at Mozilla is glue-sniffing-fueled.
(Happy Firefox user here; I still don't understand why anyone who cares even the tiniest bit about privacy or an open web is using Chrome.)
The amount of things that now need to be toggled off on a new install are approaching Windows “telemetry” levels:
disable sponsored shortcuts on homepage, disable experimental “Studies”, sponsored suggestions in search bar, “suggested extensions”, Pocket, and the list goes on.
I really need to look into a privacy friendly fork of FF..
> I really need to look into a privacy friendly fork of FF..
I'd love to make the jump too, just that I rely upon FF sync too much. It's handy getting your bookmarks and other details on mobile devices. The other forks look to be desktop only.
True, it's very handy... but can't Chrome do it with a Google account ? (I really don't know)
To me the really seeling point of firefox is being able to switch off search suggestions. Now the bar only searches opened Tabs, history, bookmarks and I can tab into them quickly. If nothing turns up, pressing Enter will still launch a search. Being able to do casual navigation without having to go through a search engine is a killer feature (and it's better for the planet).
Not only tab but you can search directly into opened Tabs/history/bookmarks with the right %/^/* symbols !
Not to hang around like a bad smell every time they come up, but just think it’s worth noting they are not open source anymore, instead being “source available”. Really gives me the old school “greenwashing” vibes Microsoft used to do with their Shared Source licenses. Poor showing considering they used others work to get to where they are, then shut the door when others started doing the same.
I would say feel free to give Waterfox a try - I’ve tried to strike the balance of useable web and privacy, with the added enhancement of Oblivious DNS enabled by default.
In this case I had completely missed the bad smell, so I appreciate the comment cause it prompted me to look up the whole situation. yikes. I was already planning on moving to another fork soon since I wasn't using most of floorp's power features, so this just expedited that.
Also from your language it sounds like you're a Waterfox dev? If so thanks for all your hard work on open source software! I haven't tried waterfox in years, I will definitely give it a go after uninstalling floorp.
> I rely upon FF sync too much. It's handy getting your bookmarks and other details on mobile devices.
I would love to use that functionality, but... How?!? Once you have a gazillion tabs open on your phone, the “Open tabs from other devices” (or whatever it's called) menu item on the desktop just shows an endlessly spinning spinner. :-( So maybe via bookmarks... But where's the “Bookmark all open tabs” menu item in FF for Android???
This is an extremely uncharitable view of Firefox and an outrageously generous view of Windows. The things you listed take 2 checkboxes in a new tab window, 2 checkboxes in settings (which has a search bar that takes you right to them by just searching "studies" or "data collection"), 2 checkboxes in settings (search "suggestions"), 2 clicks (right click the pocket button and click hide)... The only tricky one is the recommended extensions but that's tucked at the bottom of a page nobody uses anyways (everyone just googles the extension they want and grabs it from the web), but even that takes like 15 seconds once you know what setting it is in about:config. I actually don't even disable the two telemetry checkboxes because they're transparent about the data they take and what they do with it, so I'm happy to share it. You can easily do all of this in one or two minutes and it won't roll itself back.
With Windows you would be lucky to even have a supported method to disable their telemetry, and if you do get one it will probably be through an obscure series of registry edits that will ultimately get rolled back during a system update.
> This is an extremely uncharitable view of Firefox and an outrageously generous view of Windows. The things you listed take 2 checkboxes in a new tab window, 2 checkboxes in settings (which has a search bar that takes you right to them by just searching "studies" or "data collection"), 2 checkboxes in settings (search "suggestions"), 2 clicks (right click the pocket button and click hide)... The only tricky one is
It’s wild to me that this is being presented as if it’s not a big deal.
Shows how far the goalposts have moved in this conversation.
How big a deal it is depends on what you're comparing to. Yeah, at first, when I read his post, I was wondering if it was a joke or something, with so many checkboxes in different places. Then I got to the point about Windows and realized he's right: compared to Windows, all those steps in Firefox actually aren't that bad, and actually stay unchecked unlike Windows which happily changes things back.
Thank you. And I would even say that settings aren't really even in different places, they're all either on the Settings page or on the element in question. New tab settings are on the new tab page, and you disable the pocket button by right clicking the pocket button. Not exactly rocket science, especially compared to Windows.
"by just searching "studies" isn't "just", to have to remember the option names and be certain you remember them all (and not miss the newly added ones), it's not that trivial of a hurdle
It isn't. I can without any sarcasm disable all of that in about a minute or two, and for the most part see no reason to do so in the first place (the worst bit is probably sponsored links on new tabs but that's also the easiest to remove). Acting like this invalidates the existence of the whole browser is what makes no sense to me.
"Acting like this invalidates the existence of the whole browser is what makes no sense to me."
They market themself as standing for the open and free web and digital rights and privacy and what not. And then have the browser spying on every user by default with integrated ads.
So sure, you and me deactivate it, but a common person who just fell for the marketing and who does not even know what "telemetry" is, will have it enabled. The only reason I use their browser is, because there is no alternative - yet.
Transparent telemetry is not spying. I'll agree that the ads are annoying but they're about as unobtrusive as you can make them. This is not the catastrophe you believe it to be, and even if it were, the big scary evil worse-than-Google Mozilla allows forks and Librewolf exists.
Its usage and the data it collects are not malicious or done to track you. "Data collection" is arguably a clearer name than telemetry to the average user and is clearly labelled, and can be disabled in a single checkbox in settings. It is transparent.
"Its usage and the data it collects are not malicious or done to track you."
There is tracking also for ad purposes activated by default in firefox. A recent developement. Before the tracking was ocasionally and hidden under "studies". Firefox in its default settings spies on its users and sells this data to advertisers - that is the situation.
On the frontpage FF is advertised as privacy friendly and there is 0 indication that FF itself will also track you.
If that is transparent to you, than we can just agree to disagree.
I will definitely second this. I moved over to librewolf last year and love it. I’m glad Mozilla is staying in business though. I know not every organization has my beliefs and I can live with that
> The amount of engineering resources poured into just making JavaScript fast is mind-numbing. But even "just" providing a light, mostly standards-compliant browser with a sorta-good-enough performance would be great.
We're long past the time that we should be using one type of app for text plus a bit of Javascript and another for running apps that are hosted on a remote server. I would definitely use a fast, lightweight, privacy-oriented browser for sites like HN or viewing local HTML files.
> But it's a bit disappointing to see that it's still pretty much a one-man project.
I don't know much about this project and I have never used it. But in my experience as a developer and user of software I couldn't disagree more.
The longer something can stay a one-person project, the better! Nothing kills creativity, innovation, and velocity faster than having to make every decision by committee.
Big communities are great when a project is in its maturity and mostly needs tending and slow evolution. They mitigate the risk of a single developer getting bored and walking away, or turning into a murderous wacko, or attempting to monetize the project to death. Not naming any names.
But when something is being built from scratch? Give me a single developer with a fat internet connection, alone in a cabin in the woods with a shed out back full of Red Bull :)
> The longer something can stay a one-person project, the better! Nothing kills creativity, innovation, and velocity faster than having to make every decision by committee.
One person can get surprisingly far, but there's a limit beyond which no single human will scale. Getting to the v8 performance is IMHO such an example. You might be OK with a browser which has a noticeably subpar performance, but it will likely stifle mainstream adoption (which again, might be OK for you and that's fine).
> Getting to the v8 performance is IMHO such an example.
There's no doubt in my mind that Andreas could achieve that by himself. He's worked professionally on webkit, and implemented a JS interpreter, a JS bytecode interpreter, and a JS JIT all by himself after all. Also let's not forget that V8 is open-source, all their optimizations are available for others to see and implement.
But to be clear this isn't a one man project, he hired a few contributors to work full time on it. Sure, it's a small team, but as said in sibling comments a small team has much more velocity.
Seems like Andreas doesn't have the same delusions of ridiculing the army of (pretty smart) Chrome/V8 devs by doing the same job just on his own. His own goal is to achieve the performance of non-JITed JavaScriptCore - i.e. an optimizing interpreter.
Matching V8's perf would be infeasible, but couldn't a small team get within an order of magnitude of V8's perf for a decent chunk of websites? How much slower is Fabrice Bellard's QuickJS?
Andreas isn’t targeting V8’s JIT performance. The goal is to be roughly in line with WebKit’s performance with the JIT turned off.
The theory is that JS JIT compilers don’t actually improve real world performance on the majority of websites. This was apparently per the advice of the authors of Chrome’s and Safari’s JITs.
Have to admit the Firefox hate is mostly irrelevant.
its from a place of disappointment with Mozilla more than hate really.
I agree that the amount of work and competition LadyBird is facing from Chrome alone is staggering, but at the same time, I'll always root for the little guy in tech, since imo thats where real innovation comes from.
There's several decades-old sayings to the effect of what Intel giveth, Microsoft taketh away, or similar observations about the software side of computing spending all the hardware improvements and more.
To this general principle you can add browsers and websites; what the browser giveth, the websites taketh away. You may think browsers are slow... they really aren't! There's a staggering, even arguably insane, amount of optimization in there. But then we write websites that are barely adequate, and load them up with ad scripts that aren't even barely adequate, and blame the browsers for being slow.
Write yourself an old-school 1998-style static website without a big pile of fancy features, give yourself solid .css and .js caching and use it judiciously, and the browsers can blast content to the screen blazingly fast, for all the work it is doing.
If you even could feed a 2024 web site to a 1998 browser, you'd probably be able to eat a meal while it was trying to render facebook.
I don't. I use uBlock Origin which blocks "ad scripts" and the like. My everyday machine is an old PC (older than 10 years) still on Win7, and everything is running just fine.
I also use a top of the line, recent PC on Ubuntu, mostly for development. Websites there feel instantaneous. I sometimes wonder what a subpar browser would feel like on that machine.
Maybe I should just try to run Ladybird on this to see how it goes.
So many apps have low-hanging fruit performance issues that don’t get addressed because they are judged to perform adequately in practice. Addressing them takes developer time, and not all developers have the skill set to do so (especially in a methodical way).
But, what if we had an AI agent dedicated to improving performance? It doesn’t need to be capable of solving every problem, but it could address the low-hanging fruit problems which aren’t hard to solve but nobody has time to look at.
As an embedded developer it always makes me sad to see physicists and engineers pushing the limits of physics to make faster hardware, just for devs to squander that power with lazy programming.
Exactly. What people also miss that the complexity grew considerably because of the need to cover many more "edge" cases. 30 years ago, you could assume a rough display size (fixed layouts) and DPI (no scaling needed), assume ASCII / ISO-8859-1, assume that the user is able-bodied and doesn't need accessibility features, target just DOS etc.
There is also a lot of accidental complexity which you might be able to get rid of only by BC breaks, unfortunately.
Don't forget, back in the early days of the WWW, web pages weren't mostly annoying ads. These days, this is very, very important, so we dedicate a lot of computing resources to it.
No, it really isn't. The point of faster chips is for the user to be able to do more things and do them faster (without having to wait for the computer). This may mean more complex software that uses the added capabilities to do actually useful stuff that would not have been feasible before. It does not mean meaninglessly squandering performance on layers of abstractions because that takes slightly less developer time.
The point of faster chips is to make computer programs faster. We've increased performance a thousandfold and yet programs almost always take more than a frame (16ms) to update. Once everything is rendering at absolute 60FPS (and actually, 144FPS would be nice), and the hardware is reasonably cheap (Raspberry Pi cost perhaps), then the point is to make software development cheaper.
One would think so, but some browsers do not handle well repaints or do it prematurely. I've been testing a fediverse platform against a plethora of browsers, and I'm always surprised at the differences. It's not terrible, but some do take their time.
To be fair, Twitter is painfully slow on other browsers as well due to only fetching and rendering the content after the page and javascript have loaded.
It doesn't but it accumulates cruft and since then new libraries emerge which you might be able to reuse instead of writing your own thing. Just as an example: Boost first appeared in 1999 so very likely at least early on no one used it.
Of course you could do that, but the existence of a bit of code that's survived that long within a project that's been around for 20 years doesn't mean nothing new has happened. Mozilla invented a whole language to make it easier to write browser in; I don't think they won't have considered using Boost or whatever much less radical approach we might come up with here won't have been considered and invested in.
The last time a major browser originated, RAM was measured in MB, CPU freq in MHz, and the iPod was the thing that the one trend hunter your friend knew was about to buy.
The major browser platform today, smartphones, did not exist. PDAs did not even have wireless internet yet.
The basis for the functionality of the browser is due for a reimagining.
Chrome forked from Webkit, which forked from KHTML, which apparently dates from 4th November 1998, so Chrome's base is 25 years and 7 months old tomorrow.
Feels 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.
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.
This is one of the kindest "I'm forking xyz" posts I've ever read. The whole thing is some level of heartwarming, and unlike a lot of the other posts in the same range actually makes me consider contributing to either Ladybird or SerenityOS!
Because it's not done because of anger, or anything similar. Instead it's observed that a small project became a big one, and started the cannibalize the bigger project.
So the developer decided to take the growing project to its own space and let the other project thrive, too.
Oh, this is interesting. As a GitHub sponsor of Andreas for a while now, what does that mean for sponsors? Are we funding exclusively work on LadyBird? (Had we been, for some time already?) Does the SerenityOS project have a GitHub sponsor?
I personally had grown more interested in the browser anyway, so I'll just keep sponsoring Andreas, I suppose, unless this all is a prelude to VC investment or a big company acquisition or something...
As I wrote in the announcement, I've already been working primarily on Ladybird for ~2 years already, so you have indeed been sponsoring Ladybird development by sponsoring me.
SerenityOS doesn't have a GitHub Sponsors itself, but it does use Polar to allow anyone to directly sponsor work on specific issues. See https://polar.sh/SerenityOS
And don't worry, there won't be some VC investment or big company buyout.
This 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.
Sad to hear. Hacking on SerenityOS together with Andreas was some of the most fun I've ever had. Wishing him the best of luck with Ladybird, and hoping he will come back once in a while (become the TYVC? :).
I'm seriously impressed by the amount of progress this project has made (and its apparently helped with finding issues in the various specs that constitute a modern browser) so I wish him all the best in this new direction
What's the plan for Jakt, the programming language? Does it fall under the SerenityOS umbrella? Will LadyBird continue to use C++? The blog post doesn't mention it.
It has come up from time to time. From the perspective of LadyBird it is an experiment that ran its course and LadyBird will likely just be c++.
From the perspective of serenity os it is still there and mostly compatible if someone is interested to come along and push it forward to be used in the os.
Pretty sure it has been dead for a while. I personally never saw the point but I suppose the whole mantra of Serenity was developing everything from scratch.
Andreas is probably the most positive person I can think of. I'm happy to read such an article where for once "forking" isn't associated with a negative event.
Best of luck on the new Ladybird adventure, and thanks for all your positivity and contributions!
It's getting forked. It's not that SerenityOS is losing anything it already has. Sure, the Ladybird project moving forward is choosing to use different rules/philosophy about using 3rd party code/libraries - but I find it hard to agree with your assertion that this is a negative move.
I feel like this should've been done a while ago. Community was quite split by two projects and it felt like SerenityOS was dragging Ladybird development down, both from sponsor and developer point of view.
I'm glad Andreas had committed to this, for the best to both projects.
I don't know much from Andreas other than reading a couple of his posts from here, but he's a bit of a superhero to me. Wholesomely humble guy that started what's usually deemed as a massive coding project, from scratch, just to put his head out of some shit - and the guy not only manages to make two great projects, but also identify and adult his way out of one of them for both project's good.
Ladybird 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.
I think because Servo was orginally focused at researching new techniques for designing a modern browser, not creating something for users to user. Parts of Servo made it into Firefox.
Servo was picked up from hibernation by Igalia about a year ago. They have made very good progress so far, also with a small team.
The choice of c++ for Ladybird looks a bit odd, even from code reuse point of view since Firefox, Chrome and obviously Servo can share Rust code (WebKit will likely not?).
I hope that long term the browser gets first class Windows support (currently it's via linux running under WSL), just because broad reach is best for longevity/sustainable relevance.
If you build for a particular shape/character of OS (linux/BSD as it currently stands) then a lot of the abstraction that would be needed for a truly "cross-platform" app doesn't happen.
Absolutely. As a great example, code that was architected to use either poll/epoll/kqueue/etc and IOCP under Windows was in a great position to just adopt io_uring without much rearchitecting!
It makes sense if he wants to make a useful web browser and leverage third party technologies for it, Serenity is totally from scratch. This should mean more time being spent on better problems in the web browser through reinventing fewer wheels and probably speed up the development of a new browser engine, which seems pretty interesting to me.
Ladybird had a unique position of having been developed from scratch. That had brought a fresh set of eyes to an ancient tech called Web. Leveraging OSS would diminish that aspect, IMHO. What’s your vision Andreas? What are you trying to do with Ladybird as it’s no longer a hobby but a more serious project now?
Damn I was worried for a second there, fearing some sort of falling out with the community. But this is awesome news! Ladybird is a far more important project to focus on imho.
By dropping SerenityOS as a target, Ladybird is free to make use of 3rd party libraries that don't currently work on SerenityOS. And keep in mind, SerenityOS would be unable to integrate Ladybird in this new state anyway, since SerenityOS has a strict "no 3rd party code" policy.
(Also nice: it stops being necessary to wait 30+ minutes for multiple CI runs on SerenityOS every time you post a browser engine pull request!)
In time, I'd love to see Ladybird come back as a port on SerenityOS.
Wondering about that too, but to be fair, he probably doesn't use it as his primary OS (none of the developers does I think), so with Serenty mostly being a development project and the interest shifting (back to) developing web browsers it seems logical to focus on these targets.
I've been working on projects myself where the primary target switched, because I noticed it's a bit draining to keep supporting something "just" because I love it. Dropping a target usually doesn't mean it cannot be used there anymore, but simply that you don't feel comfortable guaranteeing support.
I don't know if that's the case here, only that it doesn't necessitate bad feelings.
Given that it was also stated that it won't be self-contained anymore that's also a very good technical reason. And I totally get that if you want to create a new browser with a new layout engine not wanting to re-invent every audio, video, image decoder, not wanting to reinvent all the wheels makes it already a huge project and I'd assume it's hard to guarantee all of these things will also work and compile on Serenity, which despite doing an amazing job at porting might get stuck here and there. I mean, see the OpenBSD and Rust(up) story.
Possibly that for Ladybird to move forwards more quickly, it needs access to OS API's or Graphics stuff that Serenity can't yet provide? (I'm just spitballing here, I don't know much about OS development)
To take it a step further, due to the fact that Andreas is being sponsored to work on Ladybird full time by a few companies, if it's inherently also tied to the development of Serenity (since its a primary target) that might make him concerned that there's a clash of responsibilities there - he might not want any sponsors pulling out or arguing that he's spending their money on Serenity instead of Ladybird.
This is all just assumptions however, and regardless of the reasons I think he's doing the right thing.
The web is eating everything. Maybe every app could be structured as if it's a web app or worker service to do everything people expect while being minimal?
It's interesting that the OS layer could be even thinner than SerenityOS. With 'Local first' capabilities and the expanding role of web technologies, this is not only possible but could be a good idea. The new Ladybird project will be really interesting; it could be a real alternative browser people want!
Being able to boot a good browser on multiple operating systems, such as a minimal BSD, a minimal Linux from scratch style OS, or even a stripped-down SerenityOS variation, is exciting. This could be more secure and easier to innovate with because it has a better level of abstractions to draw upon.
The bootable web OS projects like Palm webOS, the booting Gecko/Firefox OS projects, and Chrome OS could offer interesting lessons for Ladybird.
Running a browser in a VM, on metal, or on an existing host OS like BSD or Linux is very useful. This approach could be secure and powerful enough to attract users for security, speed, or powerful user-centric reasons (not corporate/adware-centric).
Kling and the community he's assembled is "at risk" of helping solve some serious use-cases for people and industries while having fun! Google's OS development with Android, Chrome OS, and Fuchsia may seem complicated compared to what a Ladybird OS could do.
Android is complicated and advanced, but in practice, it's bloated and error-prone with terrible complexity. For example, Pixel users miss calls due to bugs, and there are problems calling emergency numbers. Think about the array of Android and iOS exploits. The attack surfaces and codebases are too big!
Given its complexity, I can see Google switching to working on Ladybird or a Go/Rust variant. Maybe even Apple will consider this. LLMs are now capable of semi-automatic porting with their large context windows. I think things could change fast, and maybe we'll have secure devices in our pockets one day.
I wonder what Alan Kay and his fellow researches would have to say about this.
Can we interpret this as good news of Ladybird but bad news for Serenity? If Ladybird drops support for SerenityOS, what would be its built-in browser?
Serenity still has Ladybird as it is right now. So I assume that will become the baseline for "Browser" in SerenityOS going forward, and be developed independently. Whatever the browser in SerenityOS will end up looking like though, I doubt it will see much development. The kinds of people interested in working on browsers will just work on Ladybird.
Someone will probably once again port Ladybird to SerenityOS in the future. It won't be part of the main system, but users would be free to install it.
I tried Ladybird browser for fun, and it looks more stable than when I ran it for the last time, which is great!
It doesn't properly load the given substack (it seems to stop loading it in the middle), but it looks fine. :)
Surprisingly, loading Google Maps even work, but I can't seem to do more than move the map around. Github even works!
So far it seems better than Servo in throwing random sites at it, but I last tried Servo years ago so it's not fair. I guess I will try Servo now for the heck of it
edit: yeah Servo still seems worse, but it loads the whole substack post :)
I take this as very good news because like Andreas I am much more interested in the browser too. (I never liked the OS aesthetic they are targeting when it was current and I don't care for it now).
Though I wish they still targeted Serenity OS. I guess the expectation is for someone to fork the more general browser to Serenity at a later date. That's not a bad plan either since the incompleteness of the OS is bound to hold the browser back.
This whole thing is one of my most favorite things to happen in open source software. Andreas already succeeded in getting people to look at OS and browser development in a new way. All the best to them.
Thank you Andreas for creating both of these projects and for all your work on both of them and for all of the videos you’ve been making along the way while working on them.
> Ladybird now targets Linux and macOS. The SerenityOS target is dropped.
Aww :(
I can understand forking the browser from the OS, but I'm a bit sad about this. I hope SerenityOS can have a first-class browser in line with the OS philosophy.
To be fair though. SerentyOS given the size of its user base has a ton of ports already and since even super niche projects like NetBSD can pull off having one of the best (and certainly the most portable) ports collections out there I'd assume that SerentyOS will be able to pull off keeping a browser compatible that was originally made for this OS - if there is interest of course.
This is really surprising but also not at the same time. Developing a browser engine from scratch is a huge task. I think the writing was on the wall when some big donations were made from various companies (including Shopify) and Andreas hired a full time dev.
This will probably mark the beginning of the end for SerenityOS but I guess we'll see. Really enjoy watching the development videos from Andreas' YouTube channel.
Wow, I wonder what libraries Ladybird will start depending on? There are some web features that are backed by the same open source library in all three major browsers, and would be huge projects to reimplement in a compatible and cross-platform way. WebRTC and ANGLE come to mind.
Actually Ladybird had its own separate repo before merging with SerenityOS monorepo: https://github.com/SerenityOS/ladybird, so now it's like reverting it.
Have you considered doing a rewrite (or a partial one) now that third-party libraries can be used? To take all your learnings and new opportunities and use them to rearchitect things.
I fully respect these reasons, they are logical and well said. But hopefully interest in SerenityOS doesn't taper off due to this. Kling was great at garnering interest with his YouTube videos where he'd go deep into bug fixing and feature development.
Certainly, the browser has the most potential and even immediate necessity for the sake of the open Web, but I would still like to daily drive SerenityOS some day. Its aesthetics and holistic architecture are a dream realised.
Windows is going down the toilet fast, and Linux lacks the holistic element, so having something that combines the greatest visual design language - mid to late 90s interface guidelines - with the powerful Unix shell would be a huge boon for desktop computing. (Yes OSX has great albeit modern UX with the Unix underpinnings but isn't OSS or affordable to the masses).
People talk about Linux as if it's a monolithic OS and one team in some OS team sport. It's not. It's a kernel.
We've got lots of OSes built on top of that kernel: ChromeOS, Android, and all the distros that are largely different flavors of a GNU/GPL'ed user space, including Fedora, SteamOS etc.
This is fine. If you want a new OS with a "holistic" user space, well Linux is probably the easiest kernel to build it on, but you can't count on it being as free as the GNU user space, because it's still going to be expensive as hell to build, and whoever does it is going to want to recoup their investment many times over.
I think the chance that the GNU user space ever morphs into a "holistic" consumer operating system is basically zero due to how it's licensed, and the key is to understand that this is both fine and necessary.
If you want some other kind of more consumer friendly user space... I guess that starts with convincing some VCs they can make money off of it. They are not going to fund it out of the kindness of their hearts.
Personally I lost interest in consumer operating systems that are designed to limit freedom for the sake of profit, and became an exclusive Debian/Ubuntu/Mint user long ago. If you can be a programmer you can run these operating systems. The tradeoff is you lose the "holistic" and you gain freedom. The two are fundamentally incompatible I'd say so you have to make your choice.
Linux (kernel I mean) is good enough. There were some scheduling problems with audio, but it's mostly resolved. The problem is GNU style. We need another GUI and that doesn't mean just replacing X with/or Wayland protocol. It means replacing GTK and QT too.
The penguin kernel is indeed very nifty and boots nearly everywhere. Most importantly it is replete with battle-tested drivers.
Maybe the bold solution would be to port the Serenity userland + UI stack across to Linux and be very staunch about what gets into it. Essentially grafting the Linux kernel in place of the Serenity one, and using its UI Kit and WindowServer instead of GTK/QT/X/Wayland.
Maybe it might even be possible to preserve the logic and non-UI libraries of many applications, even if the UI required a complete rewrite.
Not really. Pantheon, elementary's desktop environment, is forked from gnome. So in that sense, it's very much a traditional linux desktop distro (not to belittle it, as they have put in a lot of worthwhile work into pantheon & the assorted apps)
Ah, I thought it was it's own thing. Oh well. I do think we're due for a commercial desktop Linux distro. Yes I think it should be paid. Something needs to take the place of Windows that isn't tied to specific hardware (MacOS) because Windows is getting unusable.
> Windows is going down the toilet fast, and Linux lacks the holistic element, so having something that combines the greatest visual design language - mid to late 90s interface guidelines - with the powerful Unix shell would be a huge boon for desktop computing. (Yes OSX has great albeit modern UX with the Unix underpinnings but isn't OSS or affordable to the masses).
MacOS is only as good as its hardware integration. Lifting and shifting MacOS UX to another system would only be skin deep. Much of the simplicity (and ire to many technical users) of MacOS is because its deep vertical integration.
Modern macOS design is reasonably consistent but with fewer visual cues - still a step above Windows post-7. And yes, I meant the bezels and skeuomorphism of earlier design - exemplified by Windows 9x-2k and System 8/9, while NeXT and IRIX also deserve a shout.
I guess SerenityOS is somewhat doomed now? I never saw this kind of move ending well, honestly. Even when not involved, having the original around is always a great boon to the popularity of a project.
I for one would love to see the SerenityOS GUI ported to Wayland on Windows. It's precisely what I ask for from an OS honestly.
I don't know, there's quite a few open source projects where the original author stepped down and it's thriving. Take Arch Linux for example. Before that Gentoo - and there I think the main "problem" with popularity is that self-compiling fell out of fashion.
There's also tons of software projects where this happened, just more quietly. Usually when there is no drama, nobody reports about it. So I'd assume it's usually more a problem, if there is drama, but even here I can think about projects surviving despite it. See OwnCloud/NextCloud.
Honestly, I can't think of projects where this did not end well. Given that SerentyOS is still a thing, despite Kling pulling out a while ago (in the sense of only working on the browser) it really doesn't sound like the project is on its last breath now.
Given the history of getting people into OS development - even more so than Haiku, which also did a pretty good job at that I think Kling leaves with a multitude of people stepping in.
Define ‘doomed’. As far as I can tell, SerenityOS did everything (and much more) than Andreas ever hoped it would.
It was never meant to be a ‘mass-market’ general purpose OS, but could still turn into one (or be the basis that one is built from) if the right maintainers steer it that way. But even if it doesn’t I’m glad that it existed, and that it spawned Ladybird is pretty crazy and awesome.
The audacity to call this shameful is striking to me. If you feel strongly enough that this free, open source, extremely limited resource project (working on one of the largest problem spaces..) doesn't support FreeBSD, port it yourself instead of casting shame on others for not doing it. Hopefully your comment is more lighthearted than I'm giving it credit for.
It's not out of carelessness or spite. The developer(s) can only support something they use at least semi-regularly.
Many developers who use Windows don't support Linux for example (and vice versa). Even if the code were cross platform. They simply can't claim to support something they don't use themselves or have resources to test extensively because it'll requires continous support and there can be a lot of incompatabilities even among different linux distros or environments.
That's why, in OSS, support for different platforms is usually done by having a separate engineer as maintainer for each platform, e.g: Linux drivers, gcc (for different CPU architectures), etc. These maintainers are each experts in their respective platforms and responsible for supporting it.
Here is a list of OSes[0]. Where do you draw the line on supporting these? Should every new project try to support all of these? Do you, doublerabbit, get to decide which OSes are important enough for support?
Or do you think the person who created the project and does all the work should be able to decide where to spend their free time?
Where those are still in active development. Where those exist you should attempt at least for. It's partly why they failed in the first place.
> Should every new project try to support all of these?
As said above, attempt. My projects in Perl work most places, my TCL programs do too. C and C++ all have been universes. Heck even Python.
It's only new fangled languages like Rust and Go that make an ball ache.
> Do you, doublerabbit, get to decide which OSes are important enough for support?
Yeah why not, at least allowed to voice an opinion. I'm so sick and tired seeing the world of IT on repeat. See it get abused, capitalised and freedom sucked from it. I give Linux five more years before it will be smothered in corporate.
After working as an sysadmin from the age of 13, to 35. I wish I could call done but other opportunities are not feasible at this time. The amount of bug reports I've submitted across the board is more than a dozen. Hand crafted brittle configuration files, been there done that. This isn't just me being edgy.
For more the past twenty years we've only dominated one bloody OS. Only then do we all bitch at each other because of fanboi or whatever cliche is at the moment. Systemd comes to mind.
I am so bored of the neo-Linux crowd and I've been working with it for it since 2.x kernel.
Only when you jump off the bandwagon do you see how clunky it really is.
First HN was shouting at me how a new browser could never be made and now HN is jumping up and down because one has yet won't acknowledge that other OS exist and that I personally feel developers should catered for.
> C and C++ all have been universes. Heck even Python.
> It's only new fangled languages like Rust and Go that make an ball ache.
is not even remotely accurate. The whole idea of the Rust and Go standard libraries is to abstract platform differences away, and in cases where they're unavoidable, to make them impossible to ignore. Python, by comparison, handles them badly. It does certified Bad Things like making POSIX operations silent no-ops on non-POSIX platforms. C doesn't even try. Any cross-platform C program is an #ifdef minefield, and you'll only find out whether it works on a given platform when you try to compile it and start getting obscure library header errors.
People like you is why people burn out from open source. Can't create anything without random nobodies who spend zero effort on anything shouting at you and hurling insults at you. You're being a completely toxic asshole.
No, it's not me at all. People like you are the reason why I suffer from burn out.
The burn out is because your working on an single platform and refusing to even attempt for another project, or OS for this matter. That's how I find it.
Lets reinvent the wheel for the same OS where the wheel has already been reinvented. Yet lets not reinvent the wheel for another OS.
> The burn out is because your working on an single platform and refusing to even attempt for another project
If you only knew how ridiculous this statement is then you wouldn't have made it. I've spent about ten years working in the BSD community, sent some patches to FreeBSD just a few weeks ago, spent quite a lot of time improving the Go kqueue integration recently, have donated to both FreeBSD and OpenBSD over the years, I have VMs for all the BSDs (and illumos) and regularly test things with it if need be, etc. etc.
But that doesn't mean I expect everyone to make the same choices. Some people choose to support only Windows. That's fine. Some people choose to only support OpenBSD. That's fine. And some people choose to only support Linux. And that's fine too.
If you're getting burned out because other people aren't spending their free time in the fashion you wish then your burnout is 100% self-inflicted.
This kind of hostility towards Linux was already getting old back in the FreeBSD 4 days.
You are being extremely rude and entitled throughout this entire thread. No one is under any obligation to bring their software to any given platform.
I don't think anyone disagrees that the world would be better if software were freely available on everyone's platform of choice. But you're coming up against fundamental resource limits -- there are only so many people working on a given project and there is only so much time in a day. Resource constraints are why you yourself are not doing the work and resource constraints are why other people are not doing the work.
You answered earlier that it'd be less work for everyone involved if the original authors simply ported the software, and perhaps so, but I'm not convinced of this. I would have a difficult time porting my software to MacOS for example because I've never used the platform. And even if so, I have a limited amount of time on earth. In terms of maximizing utility of my time, I think there is a strong argument that spending my time improving the software quality instead of improving its reach will result more happiness overall. Partly because you cover more than 99% of people by targeting mainstream platforms. FreeBSD for example cannot account for anywhere near 1% marketshare.
In the case of Serenity, it's not yet even in a usable state as a replacement browser. Let them focus on getting it usable. It's the type of thing that will eventually appear on BSD when it gets good enough to be used.
None of this is going to change by you leaving rude comments to the people doing open source work. I think the net result of it, if anything, is reduced interest in porting.
You have to understand and accept that you have made an ideological choice on what platform you use. You have to understand that your platform has an absolutely minimal number of users. The inevitable consequence of this is less software available for your platform. It isn't a grand conspiracy, it isn't spite, it isn't me acting like the BSD's do not deserve ports -- it's just the fundamental nature of reality and resource constraints.
Even folks on Linux are sacrificing on software and convenience and Linux has a market share which is likely multiple orders of magnitude larger than FreeBSD.
I'm sorry you're feeling burned out, but posting mean and entitled comments online is not going to help. It's only going to spread the burnout like a mind virus, causing others to feel burned out themselves.
I think if you care, go help them make Ladybird work on your OS. People who make software for fun and give it away for free owe all of us precisely nothing: I believe that’s a very important principle, otherwise they’ll just burn out as their hobby project turns into a grind.
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. :)
I know my comment comes out negative. Shameful wasn't the right word. It's disappointing that there is no target for *BSD.
I'm very respectful for you to attempt such a project. In no way am I dismissing your work but I see more and more projects becoming very mono orientated where it becomes a struggle for other OS's to adopt.
Yes, that is always implied. Even Guido, the original BFDL, stepped down. Linus will probably retire at some point (I hope, considering the alternative would be death before retirement at a relatively young age). Etc.
Which is exactly what happened to the first "dictator for life" (without the B) ;-). Even at more or less the exact age where one would expect someone to retire today.
See also: Julius Caesar, Ides of March
Edit: Just to make this clear, I also find the "I'm doing this as long as it works out and makes sense" to be the only useful approach to the "title" of BDFL.
I never got to try SerenityOS due to the developer's bizarre insistence that users compile the OS instead of just providing a precompiled ISO or IMG file. Shame because I appreciated the workhorse 9x aesthetics it had.
Why is it bizarre? It encouraged people to contribute to the project. It clearly worked out well for them. SerenityOS isn't for regular users, it's for developers.
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.
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.
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 projects with the same name? (Maybe a qualifier would help, like SerenityOS Ladybird vs Open Ladybird or something?)