▲ 190 ▼ Intel demos 528-thread chip with 1TB/s of optical bandwidth (www.theregister.com) submitted 2 years ago by Geert@lemmy.world to c/technology@lemmy.world 8 comments fedilink hide all child comments
[–] Rakust@kbin.social 23 points 2 years ago (2 children) I don't even want to think about programming for that permalink fedilink source hideshow 4 child comments replies: [+] Maticzpl@programming.dev 20 points 2 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [+] BobKerman3999@feddit.it 10 points 2 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Aceticon@lemmy.world 4 points 2 years ago* 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. permalink fedilink source parent [–] Taringano@lemm.ee 14 points 2 years ago Why are you making light of the subject? permalink fedilink source parent
[+] Maticzpl@programming.dev 20 points 2 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [+] BobKerman3999@feddit.it 10 points 2 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Aceticon@lemmy.world 4 points 2 years ago* 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. permalink fedilink source parent
[+] BobKerman3999@feddit.it 10 points 2 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Aceticon@lemmy.world 4 points 2 years ago* 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. permalink fedilink source parent
[–] Aceticon@lemmy.world 4 points 2 years ago* 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. permalink fedilink source parent
[–] Taringano@lemm.ee 14 points 2 years ago Why are you making light of the subject? permalink fedilink source parent