And in the dream I knew that he was goin' on ahead and he was fixin' to make a fire somewhere out there in all that dark and all that cold, and I knew that whenever I got there he would be there.
I most certainly do not miss ndiswrapper. Nightmare, indeed.It is hard to describe how big Larry's contribution was to Linux wireless if you weren't around for the early 00's nightmare. Thank you Larry!
My introduction to Linux was MKLinux; I was a die-hard NetBSD/OpenBSD user on x86 systems.I most certainly do not miss ndiswrapper. Nightmare, indeed.
This story takes me back to the late 90's when I REALLY wanted to have my computer be MY computer and not a bastardized form of lend-lease that was Microsoft (or, IMHO worse, Apple). I tried half a dozen times in 25 years to get on Linux, and each time, it wasn't ready. I couldn't do everything I wanted and needed to do in Linux. But open source software became my standard, moving away from the money pits of Office, Adobe and others who no longer sold software, but instead rented services on a monthly basis. Microsoft began moving toward the idea of "your computer isn't yours" with Win 8, and from there it went very downhill, VERY fast.Back in college none of these were in the mainline distros. You had to download the source code, compile it, and load it. Often times the compile would fail, and you'd have to make a few usually small tweaks to get it moving.
Then, when you happened upon a kernel update through the usual channels, you'd have to do it all over again.
Don't get me wrong. Finger did the work of God. I would not have been able to use Linux with this much dedication without the option of wi-fi, regardless off the inconveniences.
Thats exactly what surprised me most reading this article.. damn.. fingers crossed we will still be as healthy and savvy as he was post retiment age.This man is amazing and inspiring. He pretty much made all the contributions to the Linux kernel AFTER he reached retirement age. I can't imagine myself having the mental acuity to do that type of work at that age and he continued to do that into his 80s. Just...OMFG is how I feel.
Don’t worry man, the way things are going, none of us are ever going to be able to retire.This man is amazing and inspiring. He pretty much made all the contributions to the Linux kernel AFTER he reached retirement age. I can't imagine myself having the mental acuity to do that type of work at that age and he continued to do that into his 80s. Just...OMFG is how I feel.
Hell, I'm in my early 50s and my brain's so fried from severe depression, chronic pain and pain meds that I can't imagine doing all that at my age, much less into my 80s. This guy was a legend!This man is amazing and inspiring. He pretty much made all the contributions to the Linux kernel AFTER he reached retirement age. I can't imagine myself having the mental acuity to do that type of work at that age and he continued to do that into his 80s. Just...OMFG is how I feel.
There was so much to be learned working in the resource-constrained environments of earlier computing. Skills in writing tight, efficient code are still valuable today. The great thing is that it doesn't matter what languages you've learned to do it in -- it's really about being able to construct the logic as cleanly and efficiently as possible in any given language.'I have never taken any courses in Computer Science; however, I have considerable experience in coding, much of which happened when computers were a lot less powerful than today, and it was critical to write code that ran efficiently.'
The problem was, how do you get the half-dozen different companies making WiFi chipsets to agree on how their hardware should work? Especially when they were going for different goals -- some chipsets might offload more work to improve speed, others might be going for a low price point and do as little as possible in silicon, pushing the rest onto the driver.A lot of our pain that Larry alleviated is self-imposed. Why does EVERY printer, touch-pad, net-interface on every platform have to come up with a DIFFERENT way to do the SAME things? Yes, let there be improvements, like from TeleType to PCL to PostScript--- not more than once every 7 years!! Same on S100, ISA, and USB, beyond a defined set of channel control codes.
Indeed. I remember my eyes getting lit up the first time I’ve got my wifi working, this was all him, after retirement!This man is amazing and inspiring. He pretty much made all the contributions to the Linux kernel AFTER he reached retirement age. I can't imagine myself having the mental acuity to do that type of work at that age and he continued to do that into his 80s. Just...OMFG is how I feel.
Windows users can pick the generic Microsoft PostScript driver as well for many printers, though Mac and Linux users might have more option discovery when using their equivalent options.The problem was, how do you get the half-dozen different companies making WiFi chipsets to agree on how their hardware should work? Especially when they were going for different goals -- some chipsets might offload more work to improve speed, others might be going for a low price point and do as little as possible in silicon, pushing the rest onto the driver.
The situation with printers was similar. PCL took a fair amount of power to render, back in the day. Postscript took even more, and also required paying a license fee to Adobe. (The original Apple LaserWriter had more processing power than the Macintosh computer it was plugged into!) So printer companies each came with their own simplified protocol for their lower-end models, to make their printers less expensive. Now processing power is cheap, and we've come back around, with most printers supporting PDF as a page description language; Mac users (and Linux users, if they know the trick) have the joy of driverless printing, as a result.