circl_lastname

4 ms·

1. 1.▲
   by circl_lastname 1y ago

   Nothing a little printf (or dbgln as it is known as in Serenity-Ladybird land) can't fix
2. 2.▲
   by circl_lastname 1y ago

   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
3. 3.▲
   by circl_lastname 1y ago

   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
4. 4.▲
   by circl_lastname 1y ago

   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
5. 5.▲
   by circl_lastname 2y ago

   Extremely saddened. I quite liked the site, I hoped it could stay afloat
6. 6.▲
   by circl_lastname 2y ago

   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
7. 7.▲
   by circl_lastname 2y ago

   It was AI-generated
8. 8.▲
   by circl_lastname 2y ago

   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 A