|
|
|
|
|
|
by p_ing
98 days ago
|
|
|
> So many software developers have gotten so lazy with RAM usage in the past few decades. Fewer developers want to write ASM or C, today. Slower to market, slower to roll out features, etc. While that may seem like a good thing, and probably could be, the market doesn't like it. Developer choose heavy weight frameworks or don't make use of modern features in said frameworks to improve performance. And in some cases, performance can be 'good enough'. If I pretended to be a developer, if my app performs well enough, it's not my problem what else is running on your system. Besides, the OS governs it all regardless. That said, macOS has a terrible memory leak _somewhere_ that impacts even OOTB apps and this hasn't been corrected for the last two major releases. |
|
|
Usually you just have to actually look at memory usage and trim the obvious fat. But so many developers these days treat memory as an infinite resource, and don't have a clue how to use profiling tools to even investigate memory usage. That and, maybe stop shipping a copy of Chrome with your application.
I'm hopeful that LLMs will improve the state of application development. Claude can write sloppy code, but it also knows how to write rust and swift, and it knows a lot of tricks for optimisation if you prompt it.
There's 3rd party libraries which know how to interact with spotify. I wonder how many claude code tokens it would take to make a simple, native spotify client. Or discord client. Or client for Teams or Slack.