HNHacker News
TopNewBestAskShowJobs

circl_lastname

22 karma · joined July 1, 2024

submissionscomments
circl_lastname··on Pwning the Ladybird Browser
Nothing a little printf (or dbgln as it is known as in Serenity-Ladybird land) can't fix
circl_lastname··on Pwning the Ladybird Browser
Current blockers to swift usage are found here: https://github.com/LadybirdBrowser/ladybird/issues/933 Rising tide lifts all boats, by trying to use Swift seriously, they're finding and helping fix bugs in the compiler
circl_lastname··on Pwning the Ladybird Browser
The browser was not started with the idea of taking over the main focus of development, it was just another part of an already pretty large hobby OS project
circl_lastname··on Pwning the Ladybird Browser
The core Swift Lang has is being made more independent of Apple, and can be compiled for an increasing number of platforms thanks to the LLVM-based compiler
circl_lastname··on Cohost to shut down at end of 2024
Extremely saddened. I quite liked the site, I hoped it could stay afloat
circl_lastname··on Welcome to Ladybird
Ladybird is for the modern web, not so the late 90s, early 00s anymore. I don't see a worry of integrating domain-specific third party libraries, we were able to drop thousands of lines of non-Web code that people would otherwise have to maintain.

I'm guessing 2026 was chosen as people would be quickly discouraged by its slow rendering performance right now. The average person would just see it as just a slower browser rather than a serious contender.

circl_lastname··on Welcome to Ladybird
It was AI-generated
circl_lastname··on Welcome to Ladybird
It already loads most websites pretty well (The JS engine is nearly complete!). Currently the big tasks are implementing the remaining web APIs and improving performance, stability, and security, so IMO 2026 is a good target for the first Alpha-test releases.