After 20 Years of Linux Desktop, I Learned Cadence Matching

Read the full article: After 20 Years of Linux Desktop, I Learned Cadence Matching

After twenty years on the Linux desktop, more than a dozen distros, multiple desktop environments, a seven-year tiling window manager phase, and one detour through whatever I thought of as the stable answer at the time, I’m finally in a noticeably more comfortable place than ever before. The setup I’ve landed on now is Kali… continue reading.
4 Likes

For me, I can say that current life allows me to explore a blend of 1) Exploration, 2) Stability, 3) Cutting Edge and 4) Testing.

Throughout my life studying and exploring various types of computing has been in my veins. Once I decided upon pursuing a career with computers after taking a field trip with my 11th grade Algebra/Trigonometry class to the General Motors Research Labs (Research And Development | General Motors), I started using a teletypewriter with an acoustic coupler on it to communicate with a minicomputer at our county’s shared “Intermediate School District” offices. Good thing my high school was a member of that district - it gave me a FREE introduction to computers, albeit a clunky one.

From that I looked for a good place with a rich Math and Science curriculum with some kind of computer related degree. Michigan Technological University was the place of choice. In 1974 a Computer Science Department did not exist but a Computer Science Major was offered by the Department of Mathematics.

I learned about programming, design, Calculus, engineering principles, numerous programming languages, structured programming, data structures, as well as participating in project teams - probably the most helpful thing I learned!

As a professional, my organization was managing the company’s communication networks, so I learned more about the Telco industry than I did to become an accomplished programmer. In fact, that really was never a strength of mine, but understanding overall architecture, system planning and design were much more in my areas of strong understanding. In fact, I had wanted to become a systems analyst.

Once I got into UNIX systems, that greatly increased my interests; I thought I’d be an auto company employee for life; instead at least that experience got me into Telco stuff and that paved my way into a much longer career with Digital Equipment (13 1/2 years) Digital Equipment Corporation.

This is where I took that Telco background and they were able to get me into a Telco Standards organization, the T1Q1 National performance standards for telecommunications services | IEEE Journals & Magazine | IEEE Xplore.

It’s also where I learned Digital operating systems - Long gone, DEC is still powering the world of computing - Ars Technica which included this: “In 1977, DEC introduced the VAX, a new line of minicomputers that featured a 32-bit instruction set architecture and virtual memory. Its operating system, VMS, was a multi-user, multitasking OS that provided features we now take for granted, including virtual memory, file sharing, and networking. It amassed a wide variety of third-party software packages that made it the most popular system in its class.”

Windows NT: " VMS=WNT

VMS was popular because DEC supported it so thoroughly. It had a user-friendly interface and powerful command-line tools, and it was one of the first operating systems to support networking protocols, including TCP/IP, DECnet, and SNA. It had a powerful file system that supported hierarchical directories and file permissions, and it was highly customizable.

In 1988, a senior VMS engineer named David Cutler joined Microsoft to lead the development of the Windows NT operating system. Windows NT was a major departure from previous Microsoft operating systems, as it was a 32-bit, multi-user, multitasking OS. Windows client, still finding its way to usability, was a 16-bit layer that ran over MS-DOS. It wasn’t really an operating system; it was more like a program launcher."

"The second piece of the puzzle is the CPU. Unless you use a Mac, your computer’s CPU has its roots in a DEC processor that failed in the market.

In the late 1980s early ’90s, DEC was looking to change with the times and evolve its VAX line. In 1992, it introduced the Alpha AXP, later shortened to just Alpha, a RISC-based processor designed to compete with the other RISC chips on the market such as Sun Microsystems SPARC and Hewlett-Packard’s PA-RISC."

“Alpha had more going for it than just 64 bits. It was faster than an Intel processor and had a more efficient instruction clock. The one thing it didn’t have going for it was software. DEC provided multiple operating systems: OpenVMS, Tru64 UNIX (previously named DEC OSF/1 AXP and Digital UNIX), and, for a very short period, Windows NT.”

I’ve used ALL of these operating systems, including the other operating systems the competition was using while I was at Digital (referenced in the citation, which I also used for the direct quotations).

I got into testing cutting edge stuff in the Digital Equipment ULTRIX and Digital UNIX operating systems because I had direct access to Nightly Builds, most prominently when I worked on the UNIX team, but even in the era in the Telco Systems Engineering Group I was in frequent conversations and meetings with Advanced Development organizations, so that’s where testing and bleeding edge come into the conversation for me.

As a retiree now, I’ve since worked, levering these skills, as a team coordinator for testing services and back to a test engineer before retiring.

I don’t remember everything, but I have a lot of perspectives to offer on a wide variety of general hardware and software, but legacy stuff and general information is where I can be of most value at this point.

3 Likes

What a fantastic perspective to share, thank you. Your career covers ground that almost nobody writing about Linux today actually lived through. The teletype-and-acoustic-coupler era through DEC’s whole arc is the foundation a lot of us inherited without realizing it.

What stood out to me:

The MTU Computer Science major living inside the Math department in 1974 is a perfect detail. That’s the moment when the discipline was still figuring out what it even was. People who came up through that era understood computing as applied mathematics in a way the later CS-as-its-own-thing generations sometimes miss.

NT inheriting VMS DNA is one of those facts that quietly explains a lot about why Windows server stuff felt the way it did for decades.

What I take from your comment is that the explore/stability/cutting-edge/testing blend isn’t just a Linux desktop thing. It’s a way of working in computing that some people grow into over decades, across hardware and OS shifts.

Thank you for taking the time to share this.

1 Like

Yes; I had to think about it a bit because as you say, it was just a way of doing things that I had become accustomed to over a long period of time in the development work I was involved in.

2 Likes

Wow, that’s a really long article. Unfortunately, English isn’t my first language, so I’ll read it in several parts.

2 Likes

Hayden, after rereading your article about Cadence Matching, I guess that my main system has Cadence Matching present too.

For one thing, my antiX 23.2 Full Runit configuration is extremely stable. It has a window manager instead of a desktop environment; if anything, it changes even less often than Xfce; it is modest, offers just what I want and it is extremely stable. The Window Manager that I use, IceWM, has been around longer than Xfce; in fact it was around quite a while before Xfce switched to using Gtk+ for the libraries that provide the desktop; I think the original Xfce used something like Xforms - back before the GNOME project matured.

It also uses Bookworm, which only changes today when there are security updates; I call that STABLE.

To scratch that occasional itch I have multiple operating systems; I boot more than one distribution on all but one of my Linux setups; the one that’s by itself is the newest release of antiX Version 26, but it has a mature cadence too, with that same IceWM, rock solid tools, and just enough stuff to fool around with to keep things interesting but rarely rocking the boat and never leading to something that won’t boot or let me work; even in that case, I have my solid collection of Flash Drives that can be used to reinstall a working version of my system OR replace it with one of the other solid configurations I keep available.

That’s not quite your approach, but like yours, it gives me something absolutely trustworthy and with my USB Flash Drives, I always make sure to have several recently updated instances to SAVE me from any unplanned disaster.

I’ve created a few disasters by either intentionally or accidentally installing the wrong thing. I’ve been able to either save them or replace them and my “disasters” only cost some of my spare time; I’ve always had extra systems available to cover any “lame brained” mistakes; that has also been a part of the master plan, and it’s worked out well even in the middle of a disaster.

I couldn’t keep everything up when we had a tropical storm remnant from a hurricane dump rain, wind, knock down trees and lose power; I just turned everything off, it was all safe, and when power returned, I had no issues, but the preparations, back ups, etc. matched the idea of Cadence Matching, hardware and software backup (for the hardware and the software); the real life situations more than once proves that the approach does work - very well at that!

2 Likes

:100:

This is so important!

I DO love GNOME don’t get me wrong. BUT running it on top of a rolling release distro has almost always been the source of bugs and annoyances for me.

Over the years I’ve run into things like built-in Google account sync breaking, screenshots not working, and other little regressions. Because of that, I tend to prefer GNOME on an LTS or other slower cadence distro.

One of the reasons Xfce stood out to me during my DE/WM selection process is that they DO have Wayland plans. It’s just that, true to the Xfce philosophy, it’ll happen only when Wayland is fully stable and widely compatible. I’m not in a rush. I don’t want to be on a static DE or WM with no Wayland roadmap, but I’m also not ready for Wayland on mission-critical work desktops. I do beleave GNOME now defaults to Wayland already in the last version update.

And that’s the thing. Your setup may very well be better than mine. It really varies based on so many factors. In the end, only our own experiences, trial and error, and a willingness to try different things will get us to that sweet spot! :clinking_beer_mugs: :penguin:

1 Like

Well, I won’t insist on calling my setup “better”, but it’s definitely “better for me”. You made a very solid case that Kali Linux, albeit Kali Linux with your specific adaptations - including the choice of using the Xfce desktop environment, which, incidentally, is the ONLY desktop environment I take seriously at all. That’s not to say I do not check out and experiment with others occasionally, I definitely do, and that, all the more, helps me remain content with my primary configuration; which ironically enough, is something that I first spotted and enjoyed between one and two decades ago! Until something that truly makes some combination of my workflow and my interests tightly intersect, I’ll remain with my current choice until it’s simply not available any more - or I’ll do what anticapitalista (Paul Banham, founder of antiX does), I’ll grab some source code and build what I want! I hope that anti is able to continue doing that for a long time because I am NOT a good, prolific coder. What I can do is envision what I want, then I go out looking to find it; I found my sweet spot with antiX, so until that changes, that’s where I’ll be.

2 Likes