We’ve been searching for a memory-safe programming language to replace C++ in Ladybird for a while now. We previously explored Swift, but the C++ interop never quite got there, and platform support outside the Apple ecosystem was limited. Rust is a different story. The ecosystem is far more mature for systems programming, and many of our contributors already know the language. Going forward, we are rewriting parts of Ladybird in Rust.
@Beep@lemmus.org @technology@lemmy.world
Ah, the smell of irony by the morning! Adopting a programming language often praised by its “safety”, while the entire pretension of “safety” is alchemically transmuted into a sewage and deliberately flushed up (not down) by a clanker who drinks from the cesspool with the same determination and thirst that of a Chevy Opala gurgling down entire Olympic pools worth of gasoline.
Being serious now, the foreseeable future for Web browsing is definitely depressing: Chromium needs no introduction (used to be an interesting browser until Google’s mask “don’t be evil” fell and straightforwardly revealed their corporate face and farce), Firefox have been “welcoming the new AI overlords” for a while, text browsers (such as Lynx) are far from feasible for a CAPTCHA(and Anubis)-driven web… now, one of the latest and fewest glimmers of hope, an alternative Web browser engine, is becoming the very monster the fight against which was promised to be the launchpad purpose (“They who fights with monsters should be careful lest they thereby become a monster”). I wouldn’t be surprised if Servo were to enshittify, too. Being able to choose among the sameness is such a wonderful thing, isn’t it?
I mean, I’m not the average Lemmy user who got this (understandably) deep hatred against AI, I am able to hold a nuanced view and finding quite interesting uses (especially when it comes to linguistics) for the clankers (especially the “open-weighted” ones). However, this, to shoving AI everywhere and using AI to “code for you”, it’s a whole different story. A software should be programmed in the way programming (as posited by Ada Lovelace) was intended to, not “vibe coded” by a fancy auto-completer who can’t (yet) deal with Turing completeness, especially when it comes to a whole miniature operational system that browsers became nowadays. When coding a whole OS, AI shouldn’t even be touched by a two million light-years pole, let alone by a two-feet pole.
To me the hope lies in Firefox forks
@INeedMana@piefed.zip @technology@lemmy.world
Yeah, me too. Unfortunately, the forks can only get so far in removing upstream AI garbage and other proprietary/corporate-oriented whistles-and-bells. If, say, some AI feature becomes so ingrained inside Firefox upstream, so deeply it ends up becoming some hard dependency for fundamental functioning of the browser (i.e. a feature that, if removed at the code-level, would render Firefox simply unable to function), no WaterFox, IronFox, Fennec or LibreWolf would be able to keep up with the latest versions: they’d either need to do a hard fork trying to independently maintain an entire codebase for a browser, or they’d need to use downgraded versions.
Not even to say about licensing shenanigans. We’ve seen many open-source projects suddenly changing their licensing to include legalese thin letters. We’ve seen open-source projects requiring developers to sign up some kind of NDA before being allowed to contribute with code. Seems like initially-open licenses aren’t written on stone when it comes to big projects, and Firefox is a big project.
The universe of open-source software is being slowly hijacked by corporate interests. This is not different with Firefox, which (as I said in another reply to someone in this thread a few minutes ago) is Mozilla’s main product (if not the main product, it’s certainly among their main projects). The same Mozilla which has been pivoting to AI (e.g. acquisition of Anonym; subtle phrasing changes from “About Firefox” page which used to state how “Firefox will never sell your data”, now this phrase is gone).
I use WaterFox on a daily basis. It’s by far the best browser I’ve been using. I tried LibreWolf but it doesn’t really likes my Portuguese ABNT2 keyboard (which has accents I use often), even after disabling ResistFingerprint, so I ended up sticking with WaterFox. On mobile, I use Fennec on a daily basis, and I’m worried about the end of “sideloading” on Android which will likely mess with its installation. But I’m aware of how both browsers rely on upstream code from Mozilla Firefox, whose enshittification is already an ongoing phenomenon. And that’s really depressing when it comes to the future of browser landscape, because we’re hoping for a true alternative. Servo is the last bastion of said hope (until it gets EEE’d by corporate interests, given how Linux Foundation itself is increasingly surrounded by corpos.
I’m more of a GNU/Stallman person who values autonomy and libreness as non-negotiable principles. I’m only using Android because I’m stuck with it due to certain societal impositions (banks and gov apps), otherwise I’d be long using a custom phone, which wouldn’t even be Linux, but something way more “unorthodox” for a phone such as FreeBSD or Illumos/OpenIndianna, systems of which I already used on a PC environment and got quite fond of.
Why leave WebKit out?
@paraphrand@lemmy.world @technology@lemmy.world
Oh, right, WebKit, I forgot mentioning it, thanks for reminding me of it!
It’s the engine I likely used the least throughout my digital existence. I mean, I likely used Lynx more than I used WebKit, hence my forgetfulness.
However, if we’re talking about the WebKit-based Linux browsers (such as Konqueror), IIRC, they’re a bit out of spec when it comes to the “modern Web”: WebKit’s adoption of latest specs tends to be slower than Firefox and Chromium.
Now, if we’re talking about Safari specifically, then… it’s part of Apple’s walled garden, one where even “Firefox from App Store” is actually a reskinned Safari (at least in iOS).
Be it Safari or Konqueror, deep inside, the WebKit engine seems to me like the “Apple’s Chromium”, so mentioning WebKit doesn’t really improve the awful prospect for browser engines that we’re facing nowadays.
WebKit-GTK is up to date. 30 seconds of research in your favorite search engine and you would have found it out.
@woelkchen@lemmy.world @technology@lemmy.world
It takes the same 30 seconds of using caniuse.com (screenshot below), which doesn’t list WebKit-GTK specifically, but lists Safari (which is WebKit under the hood), for it to become clear how many things are missing from Safari implementation (which is WebKit).
To be fair, yes, there are many bleeding edge features, some of them implemented only on WebKit/Safari, but those Safari-only features are kind of proprietary features (prefixed by
-webkit-). Similarly, there are indeed many features still missing from Firefox while already implemented for the two other engines (such as CSS@function).But my point, which I should’ve gone into further detail earlier, is that WebKit, primarily maintained by Apple (originally authored by Apple, and a trademark of Apple since 2013), doesn’t have the same, browser-focused teams found on Mozilla (whose main product is Firefox) and Google (whose main product is advertisement through their platforms, including Chrome, so Chrome is part of their main focus just because that’s essential to keep the ads running and telemetry sneaking on the user). Apple is more focused on other businesses, such as hardware and UI, Safari and WebKit are their side-project.