this post was submitted on 19 Jun 2024
23 points (96.0% liked)

Tech

464 readers
1 users here now

A community for high quality news and discussion around technological advancements and changes

Things that fit:

Things that don't fit

Community Wiki

founded 9 months ago
MODERATORS
Vacant@programming.dev
23
AMD won Computex by extending AM5 support and launching new AM4 CPUs (www.xda-developers.com)
submitted 5 months ago by 0x0@programming.dev to c/tech@programming.dev
14 comments fedilink hide all child comments
 

...which is why i prefer AM for hardware longevity.

you are viewing a single comment's thread
view the rest of the comments
[–] mholiv@lemmy.world 3 points 5 months ago* (last edited 5 months ago) (1 children)

I think it depends on what you’re working on. If you’re working on some JavaScript web app you could say that CPUs are “good enough”. But even then larger more complicated apps will get annoyingly slow to “compile”.

It’s when you are working with larger and more complicated Rust or C or whatever code bases that compile time matters.

This all being said for me CPU important is a good thing. It was good in the 90s and it’s good now.

[–] grue@lemmy.world 1 points 5 months ago

But even then larger more complicated apps will get annoyingly slow to “compile”.

It’s when you are working with larger and more complicated Rust or C or whatever code bases that compile time matters.

If you are in the middle of doing a unit of work, iteratively making small changes to the code, compiling, and testing them, those compile times should be small too. If a small change in one file triggers your entire project to recompile, you fucked up the Makefile or structured the whole program poorly or something like that. There’s something wrong that a faster CPU will only mask, not fix.