awesomekling

8 ms·

1.
by awesomekling 1y ago
Very interesting, I was not familiar with your project. Thanks for sharing it here!
2.
by awesomekling 1y ago
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 efforts, Swift/C++ interop is still young and
3.
by awesomekling 1y ago
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 less so (in the pursuit of performance.) There are architectur
4.
font-size: An Unexpectedly Complex CSS Property(manishearth.github.io)
5 points by awesomekling 2y ago|0 comments
5.
First ever pizza ordered with Ladybird web browser(twitter.com)
15 points by awesomekling 2y ago|1 comments
6.
by awesomekling 2y ago
Can confirm, am incredibly excited to talk browsers and discuss how they work! (Hi Pavel, love the book!)
7.
Proposal for Memory Safety in C++(safecpp.org)
6 points by awesomekling 2y ago|1 comments
8.
by awesomekling 2y ago
Oliver (the main developer) just announced that they’re going to work full time on Porffor: https://x.com/canadahonk/status/1818347311417938237
9.
A New Chapter for Porffor(goose.icu)
3 points by awesomekling 2y ago|0 comments
10.
by awesomekling 2y ago
Which part, the nonprofit or the permissively licensed codebase? ;)
11.
by awesomekling 2y ago
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 possible on engineer salaries for the foreseeable future.
12.
by awesomekling 2y ago
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 with some simple page you made yourself, since you know how it
13.
by awesomekling 2y ago
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 distros would not package pre-alpha software, sinc
14.
by awesomekling 2y ago
We will absolutely have the ability to block ads. The web is downright unpleasant without this feature!
15.
by awesomekling 2y ago
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 huge team, but rather a small team that allows us t
16.
by awesomekling 2y ago
Yes, our next language will be a memory safe one.
17.
by awesomekling 2y ago
We've committed to this in our application for tax-exempt status, so it's something the organization will be stuck with. :)
18.
by awesomekling 2y ago
> 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 you think this can be accomplished? At the moment, we are
19.
by awesomekling 2y ago
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 should focus on fixing. We benefit greatly from this of course,
20.
by awesomekling 2y ago
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 time. :) Going forward, we want to support the open web as
21.
by awesomekling 2y ago
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 now. 2. No concrete plans, but it's not outside the real
22.
by awesomekling 2y ago
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 render 90%+ of the web. The last 10% will be a huge chall
23.
by awesomekling 2y ago
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.
24.
by awesomekling 2y ago
We have not been debating this publicly as it has a 100% chance of devolving into a bikeshed discussion :)
25.
by awesomekling 2y ago
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. :)
26.
by awesomekling 2y ago
We will never charge our users, or attempt to monetize them in any way. Our nonprofit will run on unrestricted donations only.
27.
by awesomekling 2y ago
Indeed, Shopify was our first major sponsor, they signed up almost a year ago! I'm super grateful to Tobi for believing in us when we were even less mature than we are today. <3
28.
by awesomekling 2y ago
Thank you for making the website! :)
29.
by awesomekling 2y ago
Yes, but not automatically yet! We are actively working on our WPT infrastructure (which relies on a full Web Driver implementation) and running it manually at the moment. Once we've got it stable and automated, we'll look at push
30.
by awesomekling 2y ago
That's right. The Ladybird Browser Initiative will only accept unrestricted donations. We're missing out on a fair bit of money this way, but we believe it's the right path for us.

More ›