this post was submitted on 04 Mar 2026
26 points (84.2% liked)

Programming

26050 readers
87 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

API-wise, native apps lost to web apps a long time ago. Native APIs are terrible to use, and OS vendors use everything in their power to make you not want to develop native apps for their platform.

all 20 comments
sorted by: hot top controversial new old
[–] HetareKing@piefed.social 15 points 1 week ago (1 children)

I have no dog in this race as far as Claude is concerned, but this is pushing a false dichotomy. Not using, say, WinForms or something, because it's too limiting or because you don't want to make a unique UI for every platform, doesn't have to mean strapping an entire web browser to your frontend, there are plenty of other options.

The reason frameworks like Electron are popular is that we've spent a long time hammering a square peg into a round hole and there are now a whole bunch of tools for designing on top of web technologies and a lot of designers with experience with those tools. And of course, the fact that code can be reused between the web app and the desktop app helps too. But it does have a performance cost. The fact that you can have poorly performing and bloated native UIs too doesn't change that no matter how well-optimised your HTML+CSS+JS is, you can create something of the same complexity that is faster and leaner using native widgets. And when people opt for the desktop app instead of web app, they typically want something that performs better than the web app.

[–] ultimate_worrier@lemmy.dbzer0.com 11 points 1 week ago* (last edited 1 week ago) (1 children)

Imagine being such a slop-brainwashed fanboi that you bend over backwards to justify Claude’s objectively stupid decision to build a custom react game engine for a terminal app.

I’m not a fan of this Primeagen guy but he’s right. https://youtu.be/LvW1HTSLPEk

Edit: OP is referring to their desktop app rather than the TUI but my/the primeagen’s point still stands.

[–] codeinabox@programming.dev 2 points 1 week ago (1 children)

Imagine being such a slop-brainwashed fanboi

Do you have any evidence for this? Looking through the post, and the author's other blog post titles, there is very little mention of AI or Claude.

Instead of throwing labels at the author, it's much more worthwhile to discuss their key argument about the challenges of developing native apps.

[–] beeng@discuss.tchncs.de 3 points 1 week ago

OpenCode is written in JS and uses Bun. Eats ram and crashes everyday.

[–] eleijeep@piefed.social 3 points 1 week ago

because we've lost native

Speak for yourself.

[–] spacemanspiffy@lemmy.world 2 points 1 week ago

I feel like that meme works here:

You: Don't use Claude because it's Electron.

Me: Don't use Claude because it is AI related.

We are not the same.

[–] NostraDavid@programming.dev 1 points 1 week ago* (last edited 1 week ago) (1 children)

Codex is written in Rust, as it should be. It even has readline integration, so you can do ctrl-j to insert a newline! :D

edit: ah dangit, this is about the desktop app. Nevermind.

[–] baod_rate@programming.dev 2 points 1 week ago

Still relevant because claude's CLI (which is actually more of a TUI) is built on react

[–] mvirts@lemmy.world 1 points 1 week ago