Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The issue is, most code only runs so few times that it doesn't really matter. Only when the code requires so much cloud resources that it's worth to spend an engineer's salary for a few hours/days to optimize it you should do it.


That excuse is fine in theory. In practice it's overused in places where performance actually counts.


Or if your software aims to be successful on end-user devices. Only because you don't pay for the electricity or the faster machines, that doesn't mean that no carbon is emitted for producing them.


Slack is extremely slow and sluggish. Outside of the hn bubble, people seem to care more about features than about speed or carbon use.

That being said, there are areas where users care about speed. For example, FPS is very important to gamers, so games are often highly optimized.


And cars are way too heavy. Just because users don't care about it, that doesn't mean that it's not important.


Many users are not aware that software can be made faster so they don't complain. They simply assume that's how things are.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: