ladybird VS b-decoded

You're in luck, Andreas has been hacking on that since a couple of months. They're calling the Linux version of the browser Ladybird: https://github.com/awesomekling/ladybird

LadyBird

Why not ladybird? https://github.com/awesomekling/ladybird

The page loads fine in Ladybird[1] on Arch. It's the browser purpose-built for SerenityOS[2] using a in-house HTTP/JS/TLS engine that hasn't matured to the point of practical usability yet. If I were a site administrator using some kind of weird metric to block a browser, this thing would definitely go on the blacklist.

As for a more common uncommon browser, GNOME Web (WebKit) also works fine.

Whatever is causing you to get blocked, it's not the browser engine you're using. Check your plugins, antivirus, MITM engines, and whatever else messes with your connection. It could also be a simple IP block because of a bad IP neighbour or a shared CGNAT server.

[1]: https://github.com/awesomekling/ladybird

[2]: https://serenityos.org/

Ooh, ooh.

I'm on Ubuntu, and it looks like I need to upgrade to 22.04 before I can experience the build process for myself.

https://packages.ubuntu.com/search?suite=jammy§ion=all&a...

The repo itself is shockingly tiny: https://github.com/awesomekling/ladybird. Looks like it needs https://github.com/SerenityOS/serenity as well. https://github.com/SerenityOS/serenity/tree/master/Userland/... is 100kLoC which is also surprisingly small.

Just use b

I use b

I used to believe this but i don't anymore.

From https://github.com/tlack/b-decoded

Arthur is famous for his very dense programming style. Most C programmers would scream when seeing this code.

In his view (and others in the terse scene), it is much better to have everything in your application readable on the screen at once than to have great names for things or a lot of white space to comfort the first timer reader.

To them, once you've sufficiently studied that screen or two of code, you can understand all of it at the same time. If it's spread out over thousands of files, it's very difficult to understand all of it, which leads to bugs, unnecessary abstraction, and the need for advanced tooling just to work with your own project's code.

He wants to see the code "all at once" so he can understand all of its behavior without paging around and shifting his focus to another tab, window, etc. To get there he makes a lot of tradeoffs in terms of the code formatting and naming conventions. He also, in b, creates a dense set of interlocking macros and abstractions that can make the code very hard to follow.

Critics and the uninitiated say that his code is like old school modem line noise: random punctuation intermixed with bits of understandable code. I would suggest that he's actually quite careful with the abstractions he chooses and they are actually not always the most dense, highly compressed code structures available to him. He chooses wisely and his code rewards deep study.

Interview with Arthur Whitney: https://queue.acm.org/detail.cfm?id=1531242

Here's some links relating to this style of code that you may find useful:

https://docs.google.com/document/d/1W83ME5JecI2hd5hAUqQ1BVF3...

https://github.com/tlack/b-decoded

https://chat.stackexchange.com/rooms/90748/conversation/ngn-...

They're not 1.5 paragraphs per line, but enough to give a taste of the implementation style.

I could write a whole compiler in that time.

Here is a link: https://github.com/tlack/b-decoded