Meta replaces WhatsApp for Windows with web wrapper that uses 1 GB RAM when idle

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by hliyan on Thursday November 13, 2025 @02:34AM (#45911875)

I've been wondering whether it's time to reserve browsers for their original purpose of reading documents and move web applications to a different paradigm: perhaps native controls/windows rendered and controlled by cross-platform markup served over the web, running on a "headless" sandbox. Perhaps a bit like React Native, but JIT compiled on the client. Not sure if this already exists. I'd really like to have native UI controls back for applications.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by hoppp on Thursday November 13, 2025 @02:49AM (#45911980)

The majority of people use web browsers to run applications because every website nowadays is a huge blob of js.

Maybe what you thinking is a wasm runtime like wasmer.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by GoblinSlayer on Thursday November 13, 2025 @03:43AM (#45912397)

https://doc.qt.io/qt-6/qmlreference.html

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by hliyan on Thursday November 13, 2025 @04:09AM (#45912599)

Yes, but QT is precompiled. If QML can be served over the web and JIT compiled locally, that might be closer to what I'm talking about.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by zahllos on Thursday November 13, 2025 @03:57AM (#45912497)

We could call it Flash. Or Java Applets.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by hliyan on Thursday November 13, 2025 @04:08AM (#45912588)

You have completely misunderstood the proposal. None of those drive OS native UI widgets through markup and scripts downloaded from the web.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by zahllos on Thursday November 13, 2025 @08:04AM (#45914429)

Ah no I was just being snarky and not at you. We're all missing (hyper)text markup language as the UI markup layer, plus js. We previously had some kind of alternative "load app from internet" but the runtimes were external (and provided lots of fun security holes).

I completely agree it would be better to rethink what we want and have markup/code/etc optimised to the task of rendering applications. I don't think it'll happen unfortunately.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by qcnguy on Thursday November 13, 2025 @10:44AM (#45916245)

Java applets drove native widgets in their first iteration. It wasn't markup but that hardly matters, you could have easily slapped some XML over AWT and the difference between a .jar and a .js isn't big.

They had to stop because native widgets aren't secure enough.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by wodenokoto on Thursday November 13, 2025 @04:50AM (#45912868)

Mozilla did that for a while, but ended up giving up on it, and spend 5 years pulling the UI markup out of their code and engine.

[ Parent | on HN ]

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by bonesss on Thursday November 13, 2025 @05:31AM (#45913201)

If they hadn’t fumbled the UI framework, and to a lesser extent the language design, you’re effectively describing .Net’s original role in the MS ecosystem and their play for web dominance.

JIT compiling, native graphics, quick and easy online deployment into sandboxes, support for desktop standards like keypresses, etc.

It feels like the web ate up the windows desktop experience instead of that experience spreading cross-platform and dominating.

[ Parent | on HN ]