4 ms·
The key word here is “server”. Optimizing memory server-side directly translates to cost savings for companies. There is a lot less incentive to optimize memory
by dabinat 4mo ago
The key word here is “server”. Optimizing memory server-side directly translates to cost savings for companies. There is a lot less incentive to optimize memory for code that runs on the user’s computer.
- avarun 4mo agoThere's plenty of incentive if it causes your users to churn.
- remus 4mo agoIt is typically hard to directly attribute churn though, whereas some massive EC2 instance costing you $30/day is a clear line item where cost savings can be measured easily.
- znpy 4mo agoNah that simply doesn’t happen. Users routinely blame that on the hardware or on the operating system, occasionally rightfully so. My anecdotal data point: my MacBook neo with 8 gb of ram running mac os is much snappier than my thinkpad x13g1 (ryzen 7 pro, 8c/16t+ 32gb memory) running linux. Same user (me), same apps, same websites, same data. I don’t really blame the apps.
- Byamarro 4mo agoThat's a clever observation and is very true. Development time tho historically was also very expensive hence push for easy to work with dev stacks such as js
- throwaway2037 4mo ago> Optimizing memory server-side directly translates to cost savings for companies. Only if those cost savings exceed the cost of development. Optimisation work is usually done by the most experienced, and hence most expensive engineers. It is also possible that the optimisation efforts will fail to produce meaningful results. In my career, I have seen more optimisation efforts fail than succeed.