675
Mozilla lays off 60 people, wants to build AI into Firefox
(arstechnica.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Feb 2024
675 points (95.5% liked)
Technology
60052 readers
2990 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
What a slap on Konqueror's face.
I don't really see it this way it's just marketing. Saying "all other browsers descend from big bad corporate Apple" is scary, saying "all other browsers descend from another open source project" is meh.
"It's all KHTML", I heard.
You have a point. But still, they could have added an "ackshually" footnote or something.
And text only browsers too.
Unfortunately, KHTML was discontinued in 2023 (according to Wikipedia)
I mean yes no kinda Konqueror simply accepted a bunch of downstream patches, including a name change.
...more or less. It could for a long time use all three of KHTML, WebKit (fork of KHTML) and QtWebEngine (Blink wrapped for Qt, that is, a fork of WebKit), they recently removed KHTML support because noone was updating it and it hadn't been the default for ages.
If they hadn't implemented multi-engine support in the past they probably would've switched over to "whatever Qt provides" right-out, it's KDE after all. Ultimately they're providing a desktop, not a web browser. Back in the days they did decide to roll their own instead of going with Firefox but it was never a "throw project resources at it" kind of situation, there were simply KDE people who felt like working on it. Web standards were a lot less involved back around the turn of the millennium, and also new and shiny. Back in the days people thought that HTML 4.01 Strict and XHMTL would be a thing that servers actually would start to output instead of the usual tagsoup.
If you're that kind of person right now I'll point you in the direction of Servo. No, Firefox doesn't use it and it's not a Mozilla project any more, Firefox only included (AFAIK) parallel CSS handling, the rest is still old Gecko.
That's quite the bummer. But still. Saying that almost all browsers can trace their lineage to Apple and Webkit is technically correct, but it's just a half-truth. As Apple and Webkit were once based on KHTML.