5 ms·
I feel like at this point we should be teaching History of Computing in CS programs. The old people cry, "This is all the same (stuff that's been going on fore
by hinkley 6y ago
I feel like at this point we should be teaching History of Computing in CS programs.
The old people cry, "This is all the same (stuff that's been going on forever," the young cry, "This is the future, old man."
The truth is somewhere in the middle.
"The future is already here, it's just unevenly distributed," very much describes the cycles, but I feel like in some ways this was more obvious 15 years ago, when PC evolution was the focus (nowadays it seems like mobility takes up a lot of bandwidth, which is a huge thing that feels small).
Things like GPUs hitting a tipping point where some feature that had been around for 4-8 years was now ubiquitous enough that software would assume that it was available - and fast. UI expectations ratchet up almost overnight even though the underlying technology has been simmering for years. This was quite pronounced in the 90's, but continued well into the 00's.
Everyone I think can see those, but the epicycles take a bit more study or time. Big architectural changes are driven by cost inequalities in our technologies, and those cycle. Eventually the right somebodies gets fed up and we get SSDs, or 10G Ethernet. Each of those makes some previously abandoned solutions viable again, and they sneak back in (often having to relearn old mistakes).
This multiprocessing idea dates back almost to the very beginning of private sector computing. The ILLIAC IV (1975) was intended to scale to 16 cores but some hardware problems capped it at 4 cores. Those processors were 64bit, and connected to ARPAnet a year before the Cray 1 was born.
Sequent revisited this idea in the late 80's, early 90's, using Intel x86 processor arrays.
We now have a handful of programming languages that have features that could be useful in aggressively NUMA systems (in particular,Scala, Elixir, and Rust). We'll probably see single-box clusters coming around again.
- thaeli 6y agoBetween GPUs and increasing core counts on CPUs, in many ways we've had single-box clusters for a while as normal current-gen workstations.
- dfox 6y agoDuring the last 20 years the typical x86 box went from single CPU, through multiple CPUs, through multiple CPUs with non-trivial NUMA topology to the current state where not having non-trivial NUMA topology is meaningful point in marketing of the thing. The primary reason is that large class of somewhat interesting workloads do not cope well with NUMA and then obviously running such workloads on some kind of weakly coupled cluster is completely impossible.
- UncleOxidant 6y agoDefinitely should be teaching more history. I recall that neural nets were pretty popular in the late 80s into the mid 90s. I recall a local startup that was working on a specialized neural net chip back in the early 90s, but they couldn't keep up with performance/price improvements from Intel & AMD and folded after a few years. Now there must be dozens of companies doing specialized architectures for neural nets.
- brianobush 6y agoIt is much cheaper nowadays to make ASICs, which I think partially explains the expounding growth in NN chips.
- UncleOxidant 6y agoNot sure I completely agree. I was in the ASIC biz back in the early 90s. I knew about the NN company I described above because they were a customer. Looking at NRE costs now vs then it doesn't seem all that different (considering inflation). (Sure, they can do a lot more gates now than back then)
- thescriptkiddie 6y agoI strongly agree that we should be teaching a history of computing in CS/CE programs. I fondly remember my intro to computing systems class taught by a greybeard who spent the entire first lecture going over history and then told us to learn emacs or vim for homework.
- flenserboy 6y agoHave a term where students, familiar with modern programming, have to deal with programming on older (80s?) machines (on VMs, at least). Not only will it force them to deal with constraints they would otherwise be unaware of, they will appreciate what they have available to them today much, much more.
- filoleg 6y agoPeople underestimate how useful it would be, despite it not being "directly applicable". If I had to pick one class that I would call fundamental to my understanding of CS, it would be CS2110 (Computer Organization and Programming) from Georgia Tech. It started off with building stuff using logic gates, like APUs. Then it moved onto other stuff. It all culminated into building your own simplistic CPU pipeline (in an emulator) and making a small game for Gameboy Advance. Dealing with hardware limitations of that handheld console, as well as learning some interesting tricks the devs had to employ for it to add stuff like parallax backgrounds, felt eye-opening.
- PAPPPmAc 6y agoThere's a quote from Alan Kay (who is full of delightful aphorisms) in an 2002 Dr. Dobbs interview "The lack of interest, the disdain for history is what makes computing not-quite-a-field." that is one of my favorite descriptions of the state of things. I'm a huge advocate for teaching History of Computing, and try to slip some into my classes (I teach computer engineering, but close enough) - maybe some year I'll manage to sell running a whole elective course.
- flyinghamster 6y ago> Sequent revisited this idea in the late 80's, early 90's, using Intel x86 processor arrays. Also, there were NS3200 versions, like the Balance 8000 with six CPUs I remember at UIUC around 1986. I was floored by how effortlessly it handled having just about everyone in the CS class compiling their assignments the night before they were due. Compared to the Pyramid 90x I'd used the year before, it was like night and day. It took a while, but that eventually percolated down to everyday PCs. It's kind of stunning that I can get 64-core CPUs these days, and even my much more modest first-generation Ryzen is no slouch.
- Maursault 6y ago> I feel like at this point we should be teaching History of Computing in CS programs. I am responding in trepidation, because I am certain you and everyone at HN must know what I am about to say. Computer Science is not the science of computers, nor is it remotely the history of computers. The "computer" in Computer Science is not a machine... it is a person, "one who computes." Nor is Computer Science programming, not strictly speaking, though programming is often among the tools utilized by a computer scientist. Computer Science is and only is a subset of Mathematics, and properly initially belongs in the Math Department of a university. The simplest analogy I have heard, which I think most now have, is that a computer is to a computer scientist what a telescope is to an astronomer. Astronomy is not the science of telescopes, nor the history of telescopes, though I would expect most Astronomy curriculums to include some overview of how telescopes work and their history, but not as some core and essential tract within the study. So in that many machines were utilized to forward the pursuit of Computer Science, so long as it is focusing on the computer science and not the nuts and bolts computer, your idea has merit. If I am not mistaken, Computer Engineering probably doesn't spend much more than a brief overview of the history of the actual hardware. The CE undergraduate degree is overflowing as it is. IMO, what you are suggesting belongs in the curriculum of the History of Technology, which is a perfectly valid and endlessly fascinating pursuit. This machine is neat, and I was using computers during this era, so it makes my mouth water, "what if I had access to that?" But unless it was actually used by someone, a computer scientist, for and to advance actual Computer Science (and that can not merely be programming or creating business applications or games, but needs to at least be efforts towards computational systems), it is entirely irrelevant to the field of Computer Science. Also, in the sense that Computer Science predates hardware by millennia, the History of Computing (i.e. the history of the activity of one who computes) is already covered in C.S. Suggested to me years ago, which I completely agree with, since "computer" is now an ambiguous term, Computer Science should change its name to avoid the all to common mistake of assuming CS has to do with desktops and servers. Computer Science is really the science of reckoning, so it should be called "Reckoning Science" to avoid further confusion.
- mlyle 6y agoThe central locus of study of computer science shifts depending upon what real computers do. We care about parallel and distributed algorithms more because we have real parallel machines and big distributed systems of many machines. It's not an obscure graduate offshoot about future hypotheticals and exotic high-end machines. We care about cache efficiency and memory access efficiency a whole lot more, because the ratio of speeds in a typical computer has changed. And we're not spending so much of our time studying n-way tape merges anymore... even though they may come "back" because of these shifting constraints. Real changes in what's typically limiting and what we're trying to do with computers shift the emphasis of computer science around. And the tick-tock cadence between individual resources and centralized resources... across scaling horizontally and scaling vertically... between single fast machines and distributed systems... can be expected to continue.