I don't even want to think about programming for that
this post was submitted on 01 Sep 2023
193 points (97.5% liked)
Technology
58061 readers
31 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
how would it be any different the io type would be abstracted away
I mean multithreading is hard
Nah, it's just a steep learning curve and then you'll be naturally using a few patterns - stuff like immutable classes, have yours function take the entire context of their operation as a variable and returning in changed in the output or check-condition, process, commit-if-still valid operation - to make your life easier.
It's only hard if you keep trying to design your program using the usual design patterns.
(Also how easy or hard it is to use does depend on the programming language).
What's really unforgiving is when your processing is spread over multiple machines with comm overheads in the order of milliseconds where a seemingly fine design decision can totally tank your performance.
Why are you making light of the subject?
528 threads? Sounds perfect for my Chrome tabs.
Oracle / Microsoft licensing team: 👀💦
But can it play doom?
I was just thinking to myself if it was possible to have more threads than 2 for each core. I guess this answers that but I didn't know you could have that many per core!
Why isn't it more common to have like 4 threads per core?
Multi-threading should just really be called "intelligent scheduling." It's making more efficient use of a CPU core by scheduling multiple different lines of code to run on a core at the same time. Some bits of code take longer to run then others and don't make full use of the CPU during the time they run, so the CPU will schedule another thread/code snippet to run in that gap of downtime.
I'm certain someone will correct me and add clarity to this explanation, of course.