"We're busy teaching you to program in a programming language that has semicolons all over the place. What that means is that it is not at all obvious how to split those tasks up into things which can be done simultaneously on different cores,... 1/5
Because your program structure says 'first do this and then, maybe, using the results of that, do something else'. And you have no choice but to wait for the first thing to finish before you start the second thing, and... 2/5
...in the context of what's happening to processors this is a *disaster*!
We are teaching you to program with a technology which was great last century, but something's gotta give if you're going to be able to survive in programming this century! 3/5
We are teaching you to program with a technology which was great last century, but something's gotta give if you're going to be able to survive in programming this century! 3/5
So, no, it's first year we've got to teach you the sequential story before you can even begin to think about what might be better in terms of being able to do
multiple stuff simultaneously. 4/5
multiple stuff simultaneously. 4/5
All I'm saying is you're learning Java now, that's the beginning of the story but it's definitely not the end of the story,
because this picture tells you that the execution model of Java is in deep trouble" - @PTOOP 5/5
because this picture tells you that the execution model of Java is in deep trouble" - @PTOOP 5/5
'what's happening to processors' is cores going up bc of power management. Indeed, 'this picture' refers to, well, this picture: 
Hopefully @PTOOP won't mind I share this tiny bit of his lecture, but I so much wanted to quote it
• • •
Missing some Tweet in this thread? You can try to
force a refresh
