this post was submitted on 29 Jun 2026
13 points (93.3% liked)
Programming
27504 readers
108 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This will be a bit of a writeup, so i'll make it a separate post soon. Mostly about, how the triangle higher clock speeds <-> higher integration and centralization <-> more powar for more waste is a dependency cycle to the disadvantage of the consumer and some ideas and new aproaches to doing things with the goal to get out of it. And also, how our general computing is a stack of historical baggage ill-suited for desktop use, down to the hardware (like, clock-cycles: great for number crunching, bad for desktop metaphor) and we work around it with a increasingly huge and brittle stack of software since around the 80s.
The conclusion is basically, that we could get away with modular MHz computing (that could be done in widely available node sizes and fabs) without detrimental effects to productive computing use (but maybe 3D gaming), if built for desktop. Honestly, i get the feeling that it's high time that we get computing out of it's infancy (playing around phase) and to a reliable tool and engineering discipline.