3 ms·
> concurrency .. has no business in a textbook for .. beginners. Why on earth not? Lots of people begin by wanting to program a simple real time game and conc
by kwhitefoot 5y ago
> concurrency .. has no business in a textbook for .. beginners.
Why on earth not? Lots of people begin by wanting to program a simple real time game and concurrency of some kind is absolutely required to do that.
Concurrency not being a first class feature of most mainstream programming languages and frameworks and being clunky in most of the rest is one of the biggest failures of language design in my opinion.
- turndown 5y agoThis is the kind of post where you really wonder if programmers even remember what it was like before they started programming. Concurrency is a legitimately difficult concept to understand and use correctly. In addition, I doubt you need concurrency in game design for a beginner project, or if you do, it's totally abstracted away by the game engine you're using to "learn".
- kwhitefoot 5y agoI didn't have a game engine on my Z80 Nascom-2 (1979-ish). I had to deal with concurrency using interrupts and assembler when I wrote a little maze game where the player was pursued by monsters. Until then I had only written a few programs in Basic. And lots of people program Arduinos and similar kit as their first attempt at coding now, are you going to tell them not to use concurrency?
- bmitc 5y agoJust because most programming languages are terrible at concurrency doesn’t mean it’s a hard concept. Surprisingly, most people have little trouble with email or snail mail processes. It’s just that a lot of programming languages, like Python, never respected concurrency in the first place.