this post was submitted on 24 Oct 2025
248 points (98.8% liked)
Technology
76813 readers
2513 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Our hardware has its own problems.
We rely way too much on x86 and ia64 architecture, both of which have only two big manufacturers in the world. That's not good because it's almost monopolies.
It would be better to have simpler chipsets that can be produced by more manufacturers worldwide, and especially ones that can be produced by smaller regional manufacturers.
On top of that we shouldn't distribute compiled binaries for the x86 and ia64 chipsets; instead program code should be distributed like
.wasm, in a hardware-independent way, and compiled on the target device. That would enable that hardware can use any chipset it wants and there are no software incompatibilities because of it.On the high performance compute / GPGPU side the AdaptiveCPP JIT compiler seems very good for cross-platform operation
What does this do that C# doesn't?
GPU stuff and ideally easier parallelism. The same binary could be executed on a GPU from any vendor, any CPU, anything that supports OpenCL, and could maybe even be extended to support FPGAs in the future.