I mean, web browsers are pretty fucked design-wise these days and Edge sucks, but the crawl towards only a single web rendering engine that's Google controlled is pretty bad
@ng0 Hm, I didn't realize it was only rumors for now. Hopefully it's just rumors!
@kelly_clowers I suspect @ng0 is talking about packaging difficulties since Rust is self-bootstrapping and that creates the usual difficulty for reproducible operating systems where you have to bootstrap the compiler with an older version of itself. I could be mistaken though, I shouldn't speak for ng0 :)
It's just annoying as a packager to deal with these things mostly because language authors are mostly "happy" that the umbellical cord has been cut when self-compiling is possible, but if you want to avoid "Thompson Attacks" ie "Reflections on Trusting Trust" it's more work if a version pre-self-hosting isn't maintained
@cwebber Microsoft got scroogled by Microsoft.
@cwebber preach ✊🏽 I'm not sure what the state of Chromium is these days, but Chrome is a bloated buggy mess. Regardless of reasons, data parasite Google needs less influence in our lives.
@cwebber its nigh impossible to find a decent web browser that isn't chromium/blink based or firefox
@pupy @cwebber well, blink and gecko are the only 2 really solid engines these days, with WebKit and Servo behind, falling and rising respectively. A good browser based on any engine is pretty well non-existent though. SeaMonkey is falling behind on gecko version, and has no good path forward, and FF is FF, so. And Chrome is trash
expect about a 30 million dollar investment today to get that to happen with a comparable number of "features"
@cwebber @pupy @kelly_clowers i'm pretty far from expertise, but that almost feels low - i mean, what do you need to pay in annual salaries and infrastructure expenses just to _keep up_ with changes once you somehow get to feature parity?
this is compounded by the fact that there's mostly no such thing as graceful degradation or fault tolerance on the web at this point. an engine with like 90% of the featureset still wouldn't _work_.
@cwebber honestly we had 3x more problems with Safari than Edge. They don't want their own CSS stuff all the time at least.