Yes, I remember feeling pride in the stability of my systems when I saw a large uptime. I had a server that had 1000 days of uptime, once. Now when I see a large uptime, I'm terrified of what security patches the kernel may be missing!
A Sam's Club in my area has started selling fresh squeezed orange juice. It's quite delicious. (And yes, it's pricey.) I've looked around at many other stores (including places like Whole Foods) and nobody else seems to be doing this.
Yes, the latest chips were very expensive back then, and out of reach for most people who would continue buying new computers with older chips. (As opposed to how most people today buy an iPhone or a Mac or whatever with the latest semiconductor technology.) I got my 25MHz 386 in 1991, over two years after the 486 was announced, and I had one of the fastest computers of anybody in school... for a short time.
Wow, that takes me back. It reminds me of the pre-web days when people would set up telnet services for providing information about the weather, ham radio callsigns, lyrics, FTP search engine (archie), and of course BBSs. An acquaintance of mine maintained a list of telnet BBSs and services that was fairly popular at the time. [1]
I was excited earlier this year to discover that Micron (Crucial) was manufacturing 64GB DDR5 "laptop memory" modules, allowing me to pick up a couple in early September to build an ASUS NUC VM server with 128GB of RAM. It was a little hard to get even then, but I found a vendor selling it at a reasonable price.
It worked out so well that I decided to get some more. Needless to say, it went from unavailable to being available for double the price. Now, I guess it won't be available at all in the future. :(
I don't think it was ever common, since earphones weren't that popular until people started calling them "earbuds", but the term was historically used in at least some circles in the U.S. The 1988 Radio Shack catalog [1] seems to mention "earphone" 57 times, including two mono earphone products.
When you become good at using Palm graffiti, it's not too bad. I remember playing through all of the _Hitchhiker's Guide to the Galaxy_ game on a Palm IIIx while commuting on the bus between Boulder and Denver back in 1999 or so, and being amazed that I could play an actual computer game on a handheld device.
It's just a matter of buying from the right web page at Microsoft's web site. At least as of June, I was able to buy a license with a traditional license key here:
I was in this same situation earlier this year with one machine that was using a license attached to my Microsoft account. From what I read online, I thought I was freeing up the license by running "slmgr /upk" and "slmgr /cpky" on the old machine, but I guess not. I was eventually able to get the license transferred to the new machine, but only after a very painful morning of working with an MS support person.
I learned that there are two ways of buying a Windows 11 license. One way results in getting a traditional license key that can be reliably transferred, and the other way (tying the license to your Microsoft account) risks losing your license. :( I'm very careful to only buy licenses the former way, now.
I don't think it would exactly be "create a fork of this repo", but if a developer invests significant time and effort solving hard problems where the solutions are implemented in the released source, once an LLM model is trained on it, then someone else could quickly and easily have the LLM generate a new program that implements the novel solutions. Whether this is a problem or not may depend on the motivations of the developer, but this potential for IP laundering may very well begin influencing the licenses and methods of distribution that people choose.
(Of course, I suppose at some point AI will be able to analyze and learn from binary executables or obfuscated source...)
However, ‘Hard’ is a subjective term. The deeper you are in a trade or the longer you have done it, the easier it comes to feel.
I agree with this. I don't think mail is particularly harder than other serious Linux and network system administration tasks. But it does require those sysadmin skills, and it's not something I would recommend to a typical software developer unless they were interested in broadening their sysadmin skills or had a particular need that could benefit from a self-hosted mail server.
I've been operating mail servers continuously since 1992, so I guess that's the buffalo I'm milking.