Cassius
ladybird
Our great sponsors
Cassius | ladybird | |
---|---|---|
5 | 19 | |
90 | 1,562 | |
- | - | |
0.0 | 8.9 | |
about 1 year ago | over 1 year ago | |
Racket | C++ | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cassius
-
The Rules of Margin Collapse
FWIW, while there are unfortunately only very few attempts at formalizing CSS, there's at least an unofficial, unreviewed (?), partial formal semantics for (CSS 2-era) float layout based on z3 SMT and Racket you can take a look at to get a flavor, though it isn't receiving further development.
[1]: https://github.com/uwplse/cassius
[2]: https://pavpanchekha.com/blog/css-floats.html
-
W3C’s transfer from MIT to non-profit going poorly
Do we need W3C anymore? The HTML 5 specification has been created by WHATWG for many years now, with W3C only rubber-stamping historic WHATWG versions until 2017 or so. SVG2 is going nowhere, and so isn't MathML, leaving the CSS working group as W3C's remaining point of influence over the Web. CSS is regarded as so poor and overdone a specification that the only two external projects for a formal specification have failed or remained woefully incomplete (1, 2).
-
Is There Too Much CSS Now?
1. CSS should've been split into app-y styles and doc-y styles a looong time ago; meaning that when you need JavaScript to make use of a feature anyway, there's no point in using CSS and it's better to set styles, layout using JavaScript rather than bloat CSS. The Houdini API was on the right track years ago.
2. The CSS WG at W3C must deliver formal specification rather than the prose they're writing up now. For an idea how a (partial) formal spec for CSS rendering looks like, see eg. [1], [2] (with limitations).
The one way complexity that both W3C and WHATWG have delivered over the past 15 years with complete lack of mental discipline due to financial dependency/job security will be a major source of confusion for generations to cone, and will not be looked at favorably.
[1]: https://github.com/uwplse/cassius
[2]: https://github.com/lmeyerov/sc
-
Verifying GCC optimizations using an SMT solver
There's this cool project using z3 (and racket) for formalizing CSS rendering [1] I never came around to lift for anything. Maybe someone else interested in leading the web out of the dark ages and give W3C's CSS WG an idea what we expect from them will.
[1]: https://github.com/uwplse/cassius
-
Ladybird: A new cross-platform browser project
FWIW, I know two (partial, kinda) formal specifications of CSS normal flow and float layout, both of which are finished ie dead projects:
[1]: https://lmeyerov.github.io/projects/pbrowser/pubfiles/paper....
[2]: https://github.com/uwplse/cassius
(not counting the 1990s constraint CSS effort).
The first was merely part of a parallel compiler project and also covers table layout, whereas the second is a Racket (Scheme) program to formulate the HTML doc and CSS rules as a theory for submitting to z3 SMT to solve all kinds of decision problems (it can also produce a rendering).
Not sure that's very helpful; it would be cool if W3C can invest some time into better specs (not just prose).
ladybird
- The illusion of free choice
-
Min: A fast, minimal browser that protects your privacy
A browser is not a web app, it doesn't have a strict separation of "frontend" and "backend" in the same sense that a web app would have; the lines are drawn quite differently. The rendering engine is never "just" the rendering engine; you can't abstract or swap it without tremendous effort.
If you'd like to learn more about how a web browser project would organize its internal architecture, but are discouraged by the complexity of Chromium, Firefox, etc. I'd recommend source diving Ladybird (https://github.com/SerenityOS/ladybird), NetSurf (https://www.netsurf-browser.org/), or Dillo (https://www.dillo.org/).
-
What Beta-Browsers are you all looking forward to have an official release?
I'd love to see a stable version of a brand new web browser, not based on Blink or Gecko, such as Ladybird or Flow Browser. Competition is a good thing.
- The Ladybird Web Browser
- What's the status of Servo right now?
-
Ladybird, the from-scratch SerenityOS browser, can now display Google Docs
note, native Windows is not currently supported:
https://github.com/SerenityOS/ladybird/issues/113
- Github.com on Ladybird, new browser with JavaScript/CSS/SVG engines from scratch
-
Improving Firefox Responsiveness on macOS
Google is dominating, pushing through Android and via Googles-Webservices and Microsoft is using it now. A reason to worry because developing new web-engine requires an big effort. For instance Microsoft only allows usage of Microsoft Teams Web with a webbrowser based upon Blink. So were back in 2002?
WebKit features also WebKit2Gtk (Epiphany) and Qt5-webkit (Otter) with native integration. They use the native toolkits, which is an advantage! Interaction with the open-source community around WebKit seems rather good and the engine is integrated by others. Gecko seem not to be integrated by others, but by forks only? You remember when Chrome was considered slick and fast? Originally Google used the native toolkit on every platform but know they use an own solution on every platform, like Firefox.
Maybe there is a new kid on the block:
https://github.com/SerenityOS/ladybird
-
In light of the recent news about Google’s war on adblockers, I’ve made a poster of sort
Funny you should ask: https://github.com/SerenityOS/ladybird
-
Sounds like fun for Web Developers ...
I've not heard of Ladybird before. True, it's a free and open browser engine and a very interesting project!
What are some alternatives?
Radpath - Path library for Elixir inspired by Python's pathlib
wpt - Test suites for Web platform specs — including WHATWG, W3C, and others
ex_guard - ExGuard is a mix command to handle events on file system modifications
serenity - The Serenity Operating System 🐞
sizeable - An Elixir library to make File Sizes human-readable
netsurf - netsurf
servo-embedding-example - Examples of embedding Servo inside non-browser GL applications.
browser-base - Modern and feature-rich web browser base based on Electron
alive2 - Automatic verification of LLVM optimizations
servoshell - A work-in-progress user interface for Servo, built in Rust.
splitbrowser - Split Browser - a minimalistic, ultra-lightweight, open source web browser based on WebKit/Ultralight/native webview with a split screen (tiled) view