Comment by codelion
1 day ago
I think there's a balance to be struck. While users don't directly care about the specific tech, they do care about the results – speed, reliability, features. So, the stack is indirectly important. Picking the right tools (even if there are several "good enough" options) can make a difference in delivering a better user experience. It's about optimizing for the things users do notice.
All modern tech stacks have those properties in 2025.
They absolutely do not. In fact, relatively few do. Every single Electron app (which is a depressing number of apps) is a bloated mess. Most web pages are a bloated mess where you load the page and it isn't actually loaded, visibly loading more elements as the "loaded" page sits there.
Software sucks to use in 2025 because developers have stopped giving a shit about performance.
This is so true, and yet. . . Bad, sluggish performance is everywhere. I sometimes use my phone for online shopping, and I'm always amazed how slow ecommerce companies can make something as simple as opening a menu.
happens when you use a react library with 30000 lines to show a simple select menu
Having worked on similar solutions that use Java and Python, I can't say I agree (the former obviously being much faster).
Yeah, those languages do a really good point of demonstrating the original point! Java would lead to a lot better performance in a lot of cases (like building a native application say) but Python despite being slow, has great FFI (which Java doesn't) so is a good shout for use cases like data science where you really just want a high level controller for some C or Rust code.
Point being, Python despite being slow as a snail or a cruise ship will lead to faster performance in some specific contexts, so context really is everything.
1 reply →