But that's not how the argument is used in practice. In practice this argument is used to justify bloated apps, bad engineering, and corner-cutting. When people say “users don’t care about your tech stack,” what they really mean is that product quality doesn’t matter.
Yesterday File Pilot (no affiliation) hit the HN frontpage. File Pilot is written from scratch and it has a ton of functionality packed in a 1.8mb download. As somebody on Twitter pointed out, a debug build of "hello world!" in Rust clocks in at 3.7mb. (No shade on Rust)
Users don't care what language or libraries you use. Users care only about functionality, right? But guess what? These two things are not independent. If you want to make something that starts instantly you can't use electron or java. You can't use bloated libraries. Because users do notice. All else equal users will absolutely choose the zippiest products.
I do think people nowadays over-index on iteration/shipping speed over quality. It's an escape. And it shows, when you "ship".
If queries can be dynamically written on the fly, we wouldn't need automation/agent to interact with the UI (as is the case with chatGPT operator or anthropic computer use). Instead, an intelligence layer for the frontend could dynamically query based on a graphQL schema and render with some basic html elements.
Thoughts?