8 ms·
Calling this embedded system feels like insult to the spirit of 'running light without overbyte', because it's so comically capable. My first PC had 66/33 MHz
by nabla9 7y ago
Calling this embedded system feels like insult to the spirit of 'running light without overbyte', because it's so comically capable.
My first PC had 66/33 MHz 80486 processor and 8 MB ram, 320 MB HDD. You could run AutoCAD, play Doom, Civilization, have dual boot for Linux, Windows 3.11 etc. It could compile Linux from source.
- zimmertr 7y agoOh geez I can't imagine how long it would take to compile Linux on that slow of a processor.
- CreRecombinase 7y agoI once read somewhere that the time to compile Linux from source on high-end desktop hardware has remained remarkably stable over the years.
- lisper 7y agoYes, that's true. It has been O(1 hour) for pretty much the entire history of Linux. And if you think about it, this makes sense. If it were significantly less than that, the development cycle would speed up so it would be easier to add capabilities, which would slow down the build. If it were significantly longer, the addition of new features would slow down until the hardware started to catch up. So the compile time acts as a sort of natural control mechanism to throttle the addition of new features.
- cyphar 7y agoI'm not sure that is the primary reason -- many other projects have had their compile times explode over many years, even though the same logic should apply. Not to mention if you build the kernel regularly, you benefit from incremental compilation. If you change a few non-header files the rebuild time can be as little as 2-3 minutes. Oh, and "make localdefconfig" will reduce your from-scratch compile times to the 5-15 minute mark. I highly doubt most kernel devs are building a distro configuration when testing (especially since they'd be testing either in a VM or on their local machine).
- lisper 7y ago> many other projects have had their compile times explode over many years Like, for example?
- brantonb 7y agoWhen I worked at Microsoft, Windows took far, far longer than an hour to build from scratch. I remember walking a few buildings over to the burn lab to pick up DVDs of the latest build. I don’t have any hard data, but running a full build on your dev box was very rarely done.
- pretty_bubbles 7y agoWas it just the windows kernel? Or did it include all of the utilities in Windows?
- lisper 7y agoThe dynamics of commercial projects can be very different from open-source. You're much more likely to tolerate sitting through long builds if you're being paid to do so.
- fest 7y agoUntil management notices, does the X hours saved multiplication by number of developers, and the resources for improvement will be found soon.
- cameronbrown 7y agoDefinitely not. People are far more expensive than machines.
- lonelappde 7y agoIt's a lower bound for a highly active project.
- giancarlostoro 7y agoI'm convinced that compiler speed is all a matter of how it was initially designed. Take for example Delphi which can compile millions of lines of code in under a minute or something ridiculous. Then we have D, Go, Rust, and such, they compile rather large codebases that would take C++ a good 30 minutes on high end hardware of today in shorter spans of time (not as familiar with how fast Rust compiles, but I know Go and D do pretty nicely, especially if you enable concurrency for D), which probably takes those same 30 minutes on high end hardware from about a decade ago. Sadly from what I have heard C / C++ has to run through source files numerous times before it finally compiles the darn thing into anything meaningful. Facebook made a preprocessor in D to speed things up for them, it technically didn't have to be coded in D, but Walter did write the preprocessor for them, so he gets to pick whatever language.
- anchpop 7y agoRust doesn't compile very fast unfortunately, but it's being worked on. General wisdom says it's about as fast as Clang but comparing compile speeds across languages in a meaningful way is difficult
- giancarlostoro 7y agoFair enough, thanks for that, I wasn't sure, all my Rust programs have been small enough to where I havent noticed. I wonder if it would of made sense for Rust to consider this earlier on in the same way that Pascal did. I believe I heard Pascal was designed to be parsed easily by machine code.
- steveklabnik 7y agoParsing is not the reason why it takes a while to compile.
- Sharlin 7y ago"Parsing" was probably not the best choice of word on the GP's part, but they meant that Pascal was specifically designed to be implementable with a naive single-pass compiler; of course that would exclude many optimizations we take for granted these days.
- pbhjpbhj 7y agoMy first Linux, Slackware, took me a week to download (Slackware), was on something like 12 disks. I compiled a kernel, took two days. That was on a second-hand Pentium-S. I probably wasn't doing it right.
- anyfoo 7y agoLong. I remember it being something like an hour or so to compile the kernel, but the kernel was also much smaller then. I specifically remember Linux 2.0.0 coming in a 2MB tar ball. Because it probably took me longer to download with my 28800 baud modem from an over saturated FTP server than it did to compile. 8)
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- TkTech 7y agoRemember there was a lot less to the Linux kernel at the time. Wasn't too bad. The single-threaded compile time for Linux has stayed fairly consistent for awhile, since the tree grows about as fast as the average desktop improves. The big improvement in compile time has come from being able to compile with 8-32+ threads.
- jlgaddis 7y agoIt used to take me just over two hours to compile a (very minimal stripped down) kernel on my 25 MHz 80486 with 4 MB of RAM (in the late 2.0.x/early 2.2.x days).
- icedchai 7y agoLinux in the 90's wasn't as bloated as it was now. It definitely took well under an hour to compile a kernel. My first Linux box was a 386SX-16. I later upgraded to a 486DX4-100.
- ce4 7y agoThat doesn't sound right, it's still not bloated. The majority is drivers then comes the cpu arch folder that takes a big cut. You can check yourself with cloc: http://cloc.sourceforge.net/ http://cloc.sourceforge.net/
- icedchai 7y agoLinux 1.0 was 1 meg, gzipped and less than 200K lines of code, total. Linux 4.x is over 150 megs, gzipped. Just the lines in the arch/x86 folder are more than the total lines in Linux 1.0.
- znpy 7y agodepending on how you configure your kernel and what storage you're using, it might be doable.
- jbuzbee 7y agoYou were living large! My first Linux computer was a 20Mhz 80386SX with a 40MB hard drive partitioned half for Windows 3.0 and half for Linux (SLS) and swap. It had a whopping 4MB of RAM and I also compiled my own kernel making sure to trim down features as much as possible. It was magic seeing X11 come up for the first time just like the big-bucks Sun boxes!
- tarruda 7y agoI was a kid when my father first acquired a similar computer. We ran Windows 3.0 and my father configured a boot entry for running Doom or Ultima 7, which required so much memory that it wasn't possible to run Windows, only DOS. I remember feeling a bit envious about my neighbor having the more powerful 486, which could run Doom much faster than in our PC
- shakermakr 7y agoMade me laugh about “Dad configured a boot entry”...I remember the hours with my Dad trying to stuff whatever device drivers into that 640K via Autoexec.bat and Config.sys. Got the CD-ROM running but damn if sound now doesn’t work. Those were the days trying to get Tie Fighter in my case to work. Worse part was my Dad in his wisdom bought a family PC without a Pentium, but a Cyrix P166. Had zero floating point processing. Ran like a damn dog on any 3D game. Any Brits out there might remember Time Computers. On every back page of any newspaper ever selling PoS computers with whatever subpar hardware they could cram into a big beige box ;-)
- GordonS 7y agoHah, you had it great! My first PC was a 286, which IIRC either had no HDD, OR. 20MB HDD (might be mixing it with our next PC, which was a 386). I'm pushing 40, and still shake my head in wonder sometimes about just how much is possible at such small scale and cost. But this is now turning into "when I were a lad..." :)
- serf 7y agoOh, you kids! My XT had an 8088 @ ~4mhz in it, and we pushed it uphill to school both ways, in the snow! It was multi-functional though. The power supply was inefficient enough to heat the room, while simultaneously being heavy enough to bludgeon large creatures for sustenance. Something inside me misses the radiant heat, sitting here on a cold day with my chilly metallic laptop.
- detaro 7y agoThere's embedded devices with an order of magnitude more CPU and two orders more RAM, if you're being strict about what counts as "embedded". If you're not, probably another order of magnitude on each.
- nabla9 7y agoFor example Nvidia's Jetson AGX Xavier. 512-core NVIDIA Volta™ GPU, 8-core ARM, 16 GB RAM,...
- agumonkey 7y ago'computing progress' seems mostly resolution increase.
- deleted 7y ago[deleted]
- ljm 7y agoMy first few PCs weren't even PCs, I didn't know what they were until I was a little bit older. Somehow I intuited them naturally though; I liked exploring and being curious about what I was looking at. First one I remember was a Commodore 64, along with a 600 page book full of BASIC that you could type out and record on cassette to have your own game. The book was total gibberish to anyone else; it was just pure code with no explanation. But that's what the C64 gave you; an interactive environment on boot where you could program a new game and write it to a cassette. By default. If you wanted to play a game you had to type `RUN` or maybe one or two other things to set it up. But you wouldn't know that, because you just had an interpreter on a basic blue and white screen. Worst bit was the 10 minutes of spasmodic strobe animations that showed you the game was loading. But also each game controlled those loading animations. You had to know what game you wanted to play, and be sure of it, or otherwise you could just flip to the B-side and get a different game. After that I think we had a BBC Micro at school but I'm not sure. All I remember is an adventure game and one of those classic 5" floppies. I still really love the look and feel of inserting a floppy and manually locking it in. Floppies and cassettes and VHS's minidiscs were truly fantastic for the time. They were still mechanical, unlike CDs. Then on my dad's side I and my siblings got an Acorn PC and a bunch of random floppies. None of them made any sense but some of them did cool things when you ran them. I remember hiding from my family and putting in the floppies that made flashing colours and watching it until time passed. Must have been 11 or 12 years old before we first got a PC and by that point I was utterly fascinated. It was some shitty off-the-shelf eMachines thing but it was the best we could get; I managed to retrofit a decent graphics card in it a little bit later.
- 1123581321 7y agoLucky! We had the same 486 system but only a 40MB disk. I had to spend some lawn mowing money to get a 400MB second drive so I could install Sid Meier’s Gettysburg. :)
- jmull 7y agoWell now I feel old. I remember buying a 486 with 8MB and thinking "I'm really living in the future now!" The mhz were ridiculous and -- according to my memory -- most instructions ran in a single cycle too! (Warning: my memory is not a reliable gauge of the state of computing at the time.) 8MB was pretty extravagant but it turned out to be a good call even though it could be had for half the price within a few years.