Some background I dug up quickly:
Snark Barker creator's blog: http://tubetime.us/index.php/2019/01/19/sound-blaster-1-0-pr...
http://www.os2museum.com/wp/sound-blaster-the-french-connect...
Some background I dug up quickly:
Snark Barker creator's blog: http://tubetime.us/index.php/2019/01/19/sound-blaster-1-0-pr...
http://www.os2museum.com/wp/sound-blaster-the-french-connect...
The NSA, Google, and many other who have reached a point here single buildings are not enough computing power.
If anything the number of orgs with building sized computers is probably similar. Which feels strange but it’s more about budgets than anything else.
Are you referring to this part of the parent comment? "Old building sized computers often supported multiple organizations via time sharing etc."
I worked at Tymshare in the early 1970s, and I can assure you that we supported many simultaneous users and organizations who dialed into our Tymnet nodes with their Teletypes and other terminals to connect to our building sized computers. That was the whole point of the company, and the very thing it was named after.
He said those nights were the best experiences of his time at University (aside from meeting my mom).
This might not be your scene at all, but someone made drawings and read from Gilles Deleuze's treatise on "stratoanalysis". It's long winded and completely unlike that paper but it generalizes the idea, or at least I think it does.
Well, on the other hand, it's unfair to say it's an abuse of computing power, since if you do have the power, making autonomous devices does make a system much more elegant and manageable, and not even talking about the advantages of general processor over specialized chips.
Take another look, it also tells us something about early home computer designs - the actual CPUs were usually irrelevant, there were no technical difficulties on the CPUs themselves and you could easily put TWO CPUs in a hard drive. And unlike modern computers, it was not even the most expensive part and the choice was limited, a cheap "trainer" computer with only hexadecimal keyboard, and an expensive home computer with a color CRT often shared a single CPU. The vast majority of the cost and troubles was system design, or putting these parts into a usable computer, with your own solution of input, storage, interface, graphics, software, or a chassis. The standardized IBM PC hasn't came yet, and one needed to create a solution of every subsystem. Every computer was a unique design, often with custom-made ASIC chips for peripherals.
So we don't have to necessarily constrain ourselves to Assembly and C on those tiny devices.
Naturally it depends on the use case.
Good point.
> something like an ESP32 runs circles around the PCW1512, which we had on the school computer club
I think as long as people are having fun with them, the hardware already served a good purpose. Even if the LED blinking is implemented by running Linux.
But in my opinion, people who are interested in these popular embedded boards should also learn about the basis of electronics, or just be aware of its existence, and understand the things one could do without buying a premade "board", and that it's possible to blink an LED with a few transistors. Well, I think most will find out by themselves, it's just a matter of time and guidance.
Or as John Carmack has said, low-level programming is good for the programmer's soul, it's hard to imagine that programmers do have souls if they has never been exposed to low-level programming. Unfortunately, in the modern computing world, the chances are becoming fewer and fewer, most systems are far beyond a complete understanding for most people. I think I'll never completely understand the x86_64 instruction set (w/ SSE, SSE2, FMA, AVX), or the signal path of the PCI-E interface on my motherbard.
Recently, I think some popular microcontroller projects may be the solution for a bare-metal programming experience.
But we can also looking it from another perspective - the proliferation of mobile devices changed everything, nowadays, even using a general purpose computer is not an experience that many members of the new generation may have (there was a Hacker News article about it). Some don't understand a hierarchical filesystem of files and directories anymore, and others have problem typing on a physical keyboard. In this sense, to blink an LED on Raspberry Pi is already a big step forward, and it was exactly the motivation behind Raspberry Pi.
I like to think that it is possible we'll one day develop a CPU architecture that is both simple enough to reason about and also highly performant.
RISC-V is getting there, with open-hardware cores such as Rocket (in-order) and BOOM (out-of-order). Too bad that many and perhaps most of the peripheral components even on a general-purpose SiFive SoC are still closed hardware blocks. But people are working on opening these up as well.
Needless to say the whole thing was replaced by single ~$20 chinese FX1N clone (which also neatly solved how to drive 24V industrial loads from RPi/Arduino/ESP...).
I say the point is that you should try to do trivial things with complex control systems and vice versa. You’ll do it better and more efficiently the second time. And the third. And if you decide to scale it, you will quickly learn the cheapest way to blink 10,000 LEDs.
I disagree a bit with you (I do agree that if all the RPi ends up doing is flashing a LED, then that is a waste) You have to start somewhere and if it is flashing a LED with a Pi then cool. The path to ESP32 or ESP8266 is not far away and there is a lot, lot more to discover and play with and learn and frankly have fun with and maybe do something useful or change the world (or a tiny bit of it) with.
I had some of the best opportunities available to me in IT and electronics and electrics, schools, teachers etc etc etc. but I didn't have today's opportunities. If I was growing up today I think I would probably have started with a Pi and blinked some LEDs.
[0] https://www.digikey.com/product-detail/en/texas-instruments/...
I checked that site and "medium quantities" is 5000 of them :) (for a total price of $493). Somewhere on the page it says minimum amount is 2500, but I tried and wasn't able to successfully add that to my cart (only 5000).
So I guess that's nice, but how are you going to put even 2500 of these chips to use? That's a LOT of soldering to do. Unless you have some kind of machine to do that for you? But even then what are you going to use 2500 of them for, if not for reselling?
I remember struggling to find the right settings to play monopoly and double dragon. And IIRC there was a version of MSWORKS for this too
I'm not sure I entirely believe that explanation.
Back in 1982, the Commodore 1541 [1] was basically another C=64 with no keyboard, and a built-in floppy disk. It was big and heavy and hot and not terribly reliable.
4 years earlier, the Apple's Disk II [2] was tiny, light, and had only 5 ICs [3] -- it was described as "a state machine made of a prom and a latch" [4]. The computer's CPU drove it -- it's not like the 6502 would otherwise be running other threads or processes during I/O!
[1]: https://en.wikipedia.org/wiki/Commodore_1541#/media/File:Com...
[2]: https://www.youtube.com/watch?v=ESDANSNqdVk&t=28m30s
[3]: https://www.folklore.org/StoryView.py?project=Macintosh&stor...
[4]: https://www.folklore.org/StoryView.py?project=Macintosh&stor...
The problem was that the C64 never really sold to businesses. If you were buying Visicalc, you bought an Apple II.
"With its 12 MHz 68000 CPU, the LaserWriter was 50% more powerful than existing Macs, and with the 1.5 MB of memory necessary to download Postscript fonts and print a page at full 300 dpi resolution, it had three times as much memory as the top-end Mac."
i.e. you'd start connected like this: (drives were daisy chained)
[C64]--[1541]--[1541]
Then remove the C64 and dupe away for the rest of the evening, swapping in disks as they completed. [C64] [1541]--[1541]I had some vague idea that the chips had some autonomy (ie, when playing digital sound, they knew enough to request/fetch more data via interrupts, DMA, etc) but I'd never spent the time to really learn what was going on there.
Some were even a bit unimaginable today: for example, we had Z-80 Softcard (https://en.wikipedia.org/wiki/Z-80_SoftCard), a Z80 expansion card made (by Microsoft!) for computers with 6502 CPUs (Apple ][) to run existing business applications written for CP/M, like WordStar. It can also be connected with a modem to utilize its additional processing power to run a BBS server. There were also cards that packed multiple CPUs to implement a poorman (home computer) version of parallel processing.
The simplicity of single-task operating systems and hardware architectures of that time allowed multiple independent computers to shift control of a physical computer back and forth. Today it's - pretty much - impossible, but nobody needs it either, you can just run everything simultaneously.
At some point while playing around with the program I discovered I could also load simple DSP effects onto the signal chain (EQ, pitch shifter, even echo delay I think). It took me a little while to realize that these DSP effects were in fact not running anywhere on my CPU, but instead were running on some kind of DSP chip on the soundcard itself!
The Emu10k2 is a surprisingly overweight audio DSP that was being included for... unfortunately, no good reason, as Creative Labs sold these to gamers, and games just didn't use it outside of what could be exported via DirectSound (pre-Windows 10 sound mixing, EAX extensions (which they, themselves, are often a source of constant game crashes and/or BSoDs)) or the non-adopted Creative variant of OpenAL.
This is what you ended up discovering. I, too, had one, but never really found a use for it, as the audio quality was pretty poor due to being just a generic DAC and a generic opamp on a generic PCI card. Better than onboard sound, but not as good as inexpensive external solutions.
Going up the model range Reply SB Vibra 16 clone http://ohlandl.ipv7.net/sound/reply.html had some external eproms too.