Vibe coding also lowers the barrier of maintaining multiple native pathways. Also of adopting QT instead of electron.
replyyeah but you also have commercial licensing with Qt specifically :))
replyor we are going to see an explosion of vibe-coded GPL apps.
anyhow, the likes of Linear and Notion ain't gonna abandon web and go Qt. or!! if we are very lucky, we can see a native app framework that ticks all the boxes of a modern UI framework and is permissively licensed, but we need this crunch to stay there for years.
> you also have commercial licensing with Qt
replyThat doesn't apply so long as you are willing to accept the LGPL. In practice that means you can statically link everything except QT so that the end user is free to drop in a modified QT version if he would like.
You can even statically link QT if you really need to as long as you dump the unlinked objects on some server somewhere.
replyIf you are going to vibe code you can just pick any language you want. I had a go vibecoding in Rust and it worked perfectly fine. Even better than vibe coding in JS/Python because the type hints give the LLM a faster way to check progress.
reply