"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

There's gonna be a new browser wars.

How exciting!

Time to do your part. Switch to ladybird!

(Insert imaginary we want you for the army poster here)

I realize I'm about to post something that sounds like the most generic HN slop comments... but, considering it's why Mozilla initially made a whole new language in the first place, I hope most can look past what fanatics would normally say and focus on the scenario:

I was ecstatic about Ladybird from a "fun NIH project" perspective but once it became "serious" and had a cross-platform daily-driver long term focus it was quite the let down that the hot new independent kickstart was... still going to be built on C++ anyways. Even the Serenity ecosystem had started work on a NIH memory safe language - Jakt! I'm not going to say the "R" word (mostly because I'm less interested "which" and more interested in the "what") but the one place I'd really like to see memory safety is the new fresh-engined web browser written by a small team (or really, any team).

On that front https://servo.org/ is "alive" again under the Linux Foundation. It has a focus on being an easily embeddable engine and it seems to be picking up a bit of steam. Whether or not it really takes off remains to be seen. I'll be watching closely though!

I agree with you there, on all parts.

My reason for learning Rust in the first place was trying to contribute to the servo engine. But then, Mozilla happened. My hope for servo continues, but it won't go anywhere if it stays in the limbo it has been in after Mozilla ditched it as a project. We need a real browser project, with a full UI/UX and everything, until people take it serious as a base to fork off.

The problem with reality is that almost all software is still built on C. Kernels, userspace APIs, libraries, everything. I just wish that we would've gotten something like C ABIs, but with memory safety and VM-to-VM communication in mind, e.g. for Rust and Go, along the way. WebASM / WASI somehow got there, at least in that direction. But it's never seen as a shared object or dll replacement, and always is just a compile target and nothing more - even when the potential is there.

Something like that would solve so many problems that all kinds of programming language are trying to solve by themselves, over and over again.

Your personal site is awesome by the way! Though I got too excited about the CV "challenge" until I read on GitHub it really is just a random password you hand out to people and not a "find the secret password somewhere and trigger its" somewhere :p.

Cookie invaders gave me a good shock too :D. As well as the random "bloop" sounds. 10/10

Haha, thanks for the flowers. I tried to make my website fun to use while not sacrifing backwards compatibility.

PS: The crypto challenge is related to the song that the avatar is humming :)

Well, shit... now I must resist the urge to go back and figure it out! I've got things to do this weekend, couldn't you have lied and said it wasn't really a challenge! ;)

Yeah when I built that I was way too deep in the steganographic rabbit hole. Might have to rework it at some point, because it needs a deep understanding of how to use statistical analysis to find a key/alphabet, and the frames that don't match the previous audio frame so that the codec skips them as corrupt frames. It was the year after 3301 so well...I kind of overdid it :D

Maybe something assembly related would be fun to do, too. These days I am reversing lots of malware, so sth like patching a binary so that it evolves into a different program similar to how APE does it would be a fun challenge, I guess :D

I think Ladybird is being developed in swift, it just has a lot of c++ code that they plan on replacing because it started as a fork.