News for hackers. Stuff that matters.
Re:Meta replaces WhatsApp for Windows with web wrapper that ... by iamcalledrob on Thursday November 13, 2025 @06:49AM (#45913787)
Personally I think the challenges with this approach (having literally used a Go shared library + native UI myself): 1. The web still exists. You can't practically use a Go shared library on the web. And you probably don't want your shared library written in JS. 2. In my experience, most of the coordination is about the UI, not the underlying implementation. So the human cost isn't reduced much with shared libraries. 3. At a big company, "feature teams" can't easily ship native desktop UI because feature team eng only knows web...

I do think this approach is super viable with a product development approach that is more waterfall, however. Where a team owns the platform and it's design.

Re:Meta replaces WhatsApp for Windows with web wrapper that ... by dickersnoodle on Saturday November 15, 2025 @11:50AM (#45938706)
>feature teams" can't easily ship native desktop UI because feature team eng only knows web...

This is the bane of a lot of the native developer's existence. Add to that the designers that only know how to use Sigma plugins and it just makes it worse.