2 ms·
I think other users in here are more on the right track about where the blame for this lies. As you alluded to, a lot of programmers are happy to tweak and ref
by 8fGTBjZxBcHq 5y ago
I think other users in here are more on the right track about where the blame for this lies.
As you alluded to, a lot of programmers are happy to tweak and refine for ages so it's probably not that.
Is it just that programmers are lazy or need to care more or be better educated about optimization?
Honestly I really doubt it. I fully agree with the other takes that companies have incentives to ship working software quickly. Features sell subscriptions not performance. If it comes down to choosing between functionality and performance leaders will ship the slow feature every time.
I'm not even sure they're necessarily wrong most of the time. If you know where to look the internet is a graveyard of carefully engineered products that were beat to market and obliterated by three people with a shitty electron app.
- noobermin 5y agoYou're probably right honestly that bean counters are mostly to blame. I will say the attitude of being afraid of difficult code is a problem in modern IT (IT of any generation really) and doesn't help but companies not caring about users being the primary cause of bad, unperformat code is the correct take. Conversely then, the handwaving of the OP comment is wrong too, so if we limit the discussion of what one ought to do, I still stand by my point.