4 ms·
#3 isn't even necessary -- you're telling someone to go learn calculus when all they really need is basic algebra, at most. 2-3 hours spent on layman's summari
by nknight 15y ago
#3 isn't even necessary -- you're telling someone to go learn calculus when all they really need is basic algebra, at most.
2-3 hours spent on layman's summaries of the practicalities of modern CPU architectures (special attention to cache coherence, what fun), user vs. kernel space and switching between them, select() and its cousins, and TCP would do most of the people involved in these debates a world of good.
- jarrett 15y agoI'd venture that 2-3 hours is far too little for someone to learn the topics you list from the ground up. But I'm just nit picking :). Your point is well-taken. But one big problem is that these are unknown unknowns for many people. Suppose a new but intelligent programmer finds Node and wants to decide whether it's good for some new project. How would that programmer know what to look up? How would s/he know that, e.g., user vs kernel space is even a relevant concern in the decision to use a single-threaded, event-based framework?