Making a Ubuntu Laptop Useful to Me

Reading the headline, you might think that I don't think that Linux or the Ubuntu distribution can make for a good laptop experience. That's not the case at all. A lot depends on the applications you use, what frameworks and stacks you build your workflows around, and what your general needs are. For me, that means the Microsoft ecosystem including Office 365 and Windows.

The Windows part is pretty easy. Ubuntu is east enough and similar enough to the Windows experience that it's easy to navigate for a Windows user. At least for a Windows user with technical expertise. As it turned out, the apps were the real problem.

I have a functional laptop that was my main travel computer. It's a solid Dell machine. Unfortunately, it's just old enough that it can't be upgraded to Windows 11 so, I bought a new laptop as my travel computer. With Windows 10 now end-of-life, it seemed to be the time to upgrade. My daily drive is a desktop by Alienware.  For years, I've had a Microsoft 365 subscription, originally purchased for work. Needless to say, the majority of my computing, outside of gaming, lives in the Microsoft world. 

As an experiment, I wanted to see if I could convert my old travel computer to a reasonably functional laptop that would, at least, approximate the experience of my Windows computers. That means run the same apps, access the same cloud storage, and be otherwise useful for my everyday needs. I wasn't looking to duplicate the development environment that I have on my desktop or run resource taxing games. I just wanted to be able to do relatively normal tasks that I use my other laptop for.

Getting Ubuntu installed and configured was easy enough. I did some simple modifications such as moving the launcher dock to the bottom, like it is in Windows 11, and arranging desktop icons so that it was similar to my Windows configuration. Some changes required using terminal commands, which is a bit irritating and might not work for an average user. The power policy, for example, turns off the screen after a maximum of 15 minutes according to the GUI settings. You have to set using gsettings on the command line if you want something more. 

The primary launcher also just dumps most of your programs into a grid with a few in program group folders. I had to organize my applications manually. That's not much different than Windows 11 though the latest upgrade to the Windows 11 Start menu does some of that organizing for you if you want. 

A major hurdle to using Linux int he past was accessing cloud drives, especially OneDrive. Gnome, the display manager used by Ubuntu, makes that easier. You can connect to your OneDrive drive and access it like a network drive directly from the file manager. It doesn't sync to a local drive, however, so without a network connection you won't have access to your files. That's certainly a consideration for a travel computer.

Adding applications is where things get really dicey. The majority of Ubuntu applications are snaps or Debian packages (DEB file) available through the Ubuntu App store. That fine for installing most Linux applications. Getting the same applications that I use on Windows was ranged from easy to impossible depending on the application. For example, some applications are available on Windows and Linux. All I had to do was install the Linux version. That wasn't always as easy as it might seem. 

Software developers often have a bit of religion around package managers and will only use one of them. That's okay if it's a DEB file or a Snap. Not everyone likes those though. I ended up installing Flatpak as well to get at some applications. That resulting in two app stores that didn't support all formats. 

Unfortunately, even that wasn't enough. Ubuntu finds applications store in specific repositories. Some developers insist on releasing through their own repository which has to be added at the command line or in the Software and Updates app. Even when it is added, it still has to be enabled before those applications can be installed. Microsoft Edge required the adding of a Microsoft Linux repository. Again, it's part of the Microsoft landscape and using another browser, such as Firefox, would not allow for bookmark and setting synchronization. I had no choice but to jump through all the hoops to get it installed. Once installed though, I was able to download and configure Microsoft Teams as well.

Several applications that I use a lot only came in a Windows flavor. The solution there was to install Wine. Wine creates a compatibility for Windows applications at the API level. Once installed, Windows applications supported by Wine showed up in the App store and could just be installed. Wine, however, is not magic. Even though the WineHQ project says you can install Microsoft Office 365, it proved impossible for me to get it to install, even with detailed instructions. By the way, those instructions were command line instructions that were not for an inexperienced user. I tried using some of the GUI interfaces for Wine but, no matter what, the installation choked. So, I'm stuck using a different office suite or the online versions of the Office applciations. The latter is not really the same experience and relies upon a decent Internet connection. That's a heavy lift on an airplane.

A bright spot was gaming. I was able to install Steam which, using its Proton compatibility layer, was able to run some of my Windows games. I didn't try anything too taxing since the graphics card on the laptop likely could handle those games, but some older games were quite playable. If the computer itself was more capable, I don't doubt I could play most of my Windows games on an Ubuntu laptop. 

At the end of the day, I got about 90% of where I wanted to be. I can already hear the Linux apologists saying to switch to a different browser, cloud storage from someone other than Microsoft's, or use LibreOffice. That's a major switch of infrastructure, applications, and workstyle. You can't ask regular people to do that. 

So, the Windows hegemony will remain as long as key Microsoft applications such as Microsoft Office 365 are unavailable as native Linux applications. Maybe that's the point of not supporting Linux in this way.

Things I Like About Linux

Ok, a few weeks ago, I gave my list of things I hate about Linux as a desktop operating system. Now, I want to counterbalance that list with the things I like about Linux. I will state upfront that none of the items on the list will be of the "Because Windows does this..." or "Unlike Windows...". I really dislike that about a lot of discourse around Linux as a desktop environment. It's more Microsoft or Apple bashing than Linux cheerleading. 

So, without further ado, here are the things I like about Linux as a Desktop OS. Keep in mind that none of what I like will depend on which distribution, or distro, that you are running. A distribution is a packaged set of software that includes the Linux kernel, graphical user interface (often Gnome, or KDE, through there are literally dozens of choices), and application software. Choose wisely.

1. It runs on extremely underpowered machines. It's true that you need to find the right distro to match your computer's resources, but Linux does this better than anyone. I'm not talking about running an older version of the operating system; I mean a fresh new version of a Linux distro on practically ancient hardware. Right now, I have a laptop from 2006 running MX Linux. It's not great but it's serviceable and still useful. All of this is due to the design of Linux. It is not monolithic. The kernel stays quite small and creative distro makers find collections of applications and GUIs that fit in under resourced machines. This is why single board computers such as the Raspberry PI run Linux. 
2. All the distribution choices. I can choose a distribution that suits me or my machine. Low resources? There's a half dozen distros for that. Something modern and zippy? Sure, there are lots of mainstream distros for that. What if you don't like the user interface? Choose a distro with something different, weird even. 
3. On that note, there are distributions tailored to functions. There are distributions that are designed for software development, creatives, office work, security professionals, specific update methods, certain languages, some for use as a LiveCD, education, beginners, Mac users, Windows users, and many more. 
4. You can still change almost anything. If you find that no Linux distro gets you 100 percent to where you want to be, you can alter something to get you all the way. Package managers, applications, even graphical interfaces, can all be changed easy enough. You are even able to load multiple GUIs on your computer and switch between them effortlessly. You can also adjust so many small things, allowing you to tweak your installation to your needs and likes.
5. The cost can't be beat. While nothing is truly free, the initial capital cost of many distros, even major ones such as Ubuntu, is zero. You can pay for support if you don't want to rely on community support and your own talents, and there are some distros only sold as commercial products. The vast majority of Linux distros, however, are available for download for free.
6. The difference between a server and desktop is basically only the GUI. You can run all the server software on any Linux installation, alongside the desktop environment. In fact, the main difference between a server distro and desktop distro is that the server distro comes prepackaged with the server software and the desktop distro with the GUI preinstalled. If you want to load the desktop distro, so that you have access to GUI tools, and then load up a bunch of server software, it's pretty easy.
7. There are a multitude of ways to install and manage software. Most desktop OS' come with what is called a package manager. As it sounds, it is a way to package, install, and then manage (remove, update, list) the software on a machine, along with their dependencies. Most distros come with either apt, yum/dnf, or pacman. Most distros have a GUI for searching catalogs of software and then installing, removing, and updating software in those catalogs. You can choose the one that works best for you or stick with whatever came with your distro.
   Ubuntu uses a system called Snap which not only installs and manages software but runs it in a container system similar to Docker. It provides easy control over running software, in addition to installation. Flatpak is similar in that it installs and manages software but runs it in a sandbox to ensure that applications can't harm the system overall. Both have GUI front ends. Snap and Flatpak represent the future of package managers - containerized systems that not only manage software installs, but the runtime environment as well.
8. Even when they look different, Linux systems can interoperate. Assuming that you have installed all the dependencies, pretty much anything that runs on one Linux machine can run on another of equal resources. Ultimately, Linux is Linux, no matter the distro. Sure, if you have something compiled for a completely different microprocessor architecture it may need to be recompiled, but all Intel architecture machines will run all run the same software.

My home lab is a prime example of the versatility and interconnectedness of Linux. I have an ancient (2006) laptop running MX Linux which I use for small monitoring tasks. I have two machines running Debian derived Ubuntu Desktop OS, but configured as servers for various services within my environment. Finally, I have a laptop from 2010 running Pop_OS, itself a variation on Ubuntu, that performs the majority of monitoring and observability for the system. That's four machines with three different Linux distributions, running a host of file and cloud services, plus monitoring. All are capable of running the same modern browser, despite vast differences in age, system architecture, and resources. There was no cost for installing and managing the operating system, outside my labor. This is what I like most about Linux.

Things I Hate About AI

Anyone who knows me will tell you, I'm not a Luddite. Quite the opposite. I like shiny new technology. I have a closet full of broken tech dreams i.e. all kinds of cool gadgets that were either ahead of its time or outlived its rather cool usefulness. So, when I tell you about the things I hate about AI, it's not a knee jerk reaction. In fact, I wrote a number of papers in the mid-2010s about the potential of AI to help us mere humans.

I don't think that AI is reaching that potential. My list of things I hate about AI is partly why I believe that. 

1. It's often wrong but sounds right. Unless you have expertise in an area, you can't tell if the AI answer is true or not. If you do have expertise, you don't need it. This is an example where no answer is a better answer. I've learned to only use AI in situations where I can truly evaluate the answer's veracity.

2. It makes us lazy. We stop doing learning simple things because the AI does it for us, just, you know, wrong. Lazy isn't necessarily bad. A lot of great software was created by people too lazy to do a simple task. Lazy plus wrong, however, is a toxic combination.

3. All that typing or speaking when a couple of button clicks will do is not progress. We moved away from command lines for a reason - they were too much work for a lot of tasks and error prone. GUIs, designed right, have democratized computing. Which brings me to…

4. AI is being used to make up for bad UI design. Instead of spending bazillion dollars on AI, try fixing your horrid interface or placing that one important selection right up front. I guess we're back to the lazy thing again. Seriously, if I have to ask an AI agent to find and change a setting for me, then the UI is not working out.

5. Generative AI slop is ruining art for everyone simultaneously. Art has soul. Art has creativity. A prompt doesn't count as either and all AI can do is mimic something already created. The problem is that people are getting used to the idea that AI can create art and that what it spits out is art. 

6. AI slop in general but especially code. When revered open source projects like cUrl have to stop bug bounties because of it, you know it's destructive. It's another effect of the intersection of lazy and wrong. You get code, plans, writing, and search results that are not useful. So, it's a waster of everyone's time and resources.

7. The environmental impact is not worth the results. Is the consumption of massive amounts of energy, and the pollution that comes with it, worth what we get from AI? The true ROI is lousy when you take the damage into effect.

8. RAM, once a cheap commodity item, is increasingly expensive because of AI needs. The irony is that there may not be PCs capable of running AI apps because of AI. Once the cost of the endpoint exceeds the benefits of the service, which will be discarded first? I'm betting on the AI.

9. General AI is purposeless. Domain specific AI adds value to whatever tasks you are doing. General AI, especially chat, is a time suck. It's like voice activated everything. It makes sense in the car but not in a crowded office, or church. AI is like that. It has to be used where it makes sense and it's not. That means it needs to be tailored to and restricted to specific domains. Copilot for Microsoft 365 is actually useful. General Copilot on Windows? Less so, by a lot.

It is apparent from my list that I doubt the long-term ROI on AI. That's a money problem and hence, not my concern. My chief concern is that using AI doesn't yield consistent, high-value benefits in most instances. The societal costs - cost of RAM, environmental damage, relying on false information, and the laziness it breeds - are everyone's problem.