Viewing profile — awesomekling

Very interesting, I was not familiar with your project. Thanks for sharing it here!

Whatever happens, large parts of the codebase + dependencies will be C++ (or C) for the foreseeable future. We're working on integrating with Swift, but despite the team's earnest …

This is awesome! Really great write-up, and solid work by Jessie :^) The Ladybird codebase is generally very defensive, but like every browser, our JavaScript engine is slightly le…

Can confirm, am incredibly excited to talk browsers and discuss how they work! (Hi Pavel, love the book!)

Oliver (the main developer) just announced that they’re going to work full time on Porffor: https://x.com/canadahonk/status/1818347311417938237

Which part, the nonprofit or the permissively licensed codebase? ;)

I’m still the BDFL but my role is evolving a bit as I’m now also running the nonprofit. We are definitely a stripped down operation, and we will spend as much of our funding as pos…

We’re always open to new developers! Find a website that doesn’t work right, then try to figure out why, and see if you can fix it :) The best for a beginner is usually to start wi…

Please don't trust random distro packages of Ladybird, we have no idea what they're packaging, but it's unlikely to be current, and not something we can help you with. I wish distr…

We will absolutely have the ability to block ads. The web is downright unpleasant without this feature!

Yes! I'm already working on it full time, along with 3 employees. In the next month, we are bringing on 3 more. Given the limitations of our funding model, we won't be building a h…

Yes, our next language will be a memory safe one.

We've committed to this in our application for tax-exempt status, so it's something the organization will be stuck with. :)

> What do you think is going to be the first milestone where Ladybird is going to be able to be a real alternative (even if limited to certain use cases) and in what timeframe do y…

These days, all major browsers are taking interoperability very seriously. There’s even efforts like the annual “Interop 202x” where people vote on which interop bugs browsers shou…

That was a long time ago indeed! To be honest, I think I was partly saying that because I was scared of the idea of supporting the entire web platform. It seemed so far away at the…

1. We are not focusing on legacy hardware support. Given our release date is far in the future, we are mainly targeting the kind of devices most people will have a few years from n…

There are a ton of standards at a glance, but when you look closer, you realize that much of it isn't implemented by other browsers either, and you only need a fraction of it to re…

With a simple two-part strategy: 1. We keep the team small enough that there's always at least 1.5 years of runway in the bank. 2. We continue fundraising actively.

We have not been debating this publicly as it has a 100% chance of devolving into a bikeshed discussion :)

Yes, we are aware of how permissive licenses work. If someone forks our code and does a better job with it than we do, fair game. :)