this post was submitted on 19 Aug 2026
52 points (91.9% liked)
Technology
87402 readers
4744 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It’s true… it’d be replaced by a much LARGER attack surface.
With everybody on Webkit, a vulnerability in it applies to every browser and nearly all apps on iOS. If other engines were allowed, a threat would only apply to apps using that engine.
On the flip side, keeping the engine centralized means that a single fix will close a hole in every app, keeping unmaintained apps safer.
I wonder if it would be possible to implement Firefox or Chromium in webassembly and run it on top of WebKit — it wouldn’t be as performant, but would be an extra layer of sandbox. You could theoretically do this in any app that uses WebKit too.