My time with a Chromebook…and Linux

For those of you who know me, this is my laptop. It’s massive. It’s heavy. It gets a little under two hours of battery life in power save mode. And I wait for nothing. I game with the best, I render video with the best, and the 3.5 terabytes of storage means that I don’t delete anything. As a pet project, I adopted a second laptop. This is that laptop. It’s small, it’s not nearly as powerful, I had to order a 64GB SD card to give it any meaningful level of storage, and it doesn’t even run Windows. It’s a major change.

This time around, running Linux has been easier than my prior attempts. I’ve been running Linux Mint, and it’s been the epitome of the term “mixed bag”. Now, don’t get me wrong, installing Linux on this particular Chromebook was quite the challenge, and involved some incredible support from Mr. Chromebox, who is a wonderful individual to work with, and highly recommended for anyone looking to embark on a project similar to mine.

The usability of the Linux-running Chromebook has been greatly assisted by the number of applications available for it. Between my remote access software for work having a Linux port, along with our chat software and VPN client, the majority of my “daily grind” applications are covered, though the real assistant has been the number of browser-based control panels I interact with. Having all of that covered and genuinely not needing to worry about battery life, while also carrying it around in one hand with no need for a bag of accessories is a huge help. For the first time basically-ever, the suspend/resume function works so perfectly, I don’t shut it down. My relatively-obscure Samsung printer was automatically found on the network and configured without ever needing a driver download. The Synaptic package manager does an incredible job of being an “App Store” for actual applications, making it easy to find needed programs and browse through categories while also ensuring that updates are handled effectively. I really do like all of these, and when combined with the lack of concern regarding telemetry from either Microsoft or Aunt Google, it really is a good experience.

I used the word “good”, not “perfect”, with intention; it’s the little things that get frustrating. ‘Home, ‘End’, and ‘Delete’ are conspicuously absent. The F1-F10 keys have their Chromebook functions on the caps, requiring me to add P-Touch labels for their “F-Value”. Conversely, the lack of any sort of an “Fn” modifier key means I have to use system try icons for screen brightness and volume, rather than shortcut keys. Actually, the biggest issue has been the audio; despite following a tutorial I found online, I still can’t get audio playback independent of the HDMI port. Then again, in this day and age of autoplaying video ads, one may argue that it’s not a bug, but a feature.

The one application I was not able to find a reasonable analog for was Outlook. Now, don’t get me wrong, Linux has no shortage of e-mail clients. What it does have a shortage of, however, are mail clients that work with Activesync. I tried Eudora, Evolution, Thunderbird, Zimbra, and one or two others, none of which natively supported Activesync. In this process, I did manage to find out that it’s possible to install Android apps, which led me to installing the excellent Touchdown client. This solves my problem, but not without issues of its own. Using a touchpad as a replacement for a finger-driven UI paradigm makes it difficult to select text for copy/paste, instead generally assuming you want to scroll or change focus. Additionally, it is amazing how much there is a necessity for multiple windows when dealing with e-mail, which mobile apps simply don’t provide. My Remote Desktop client connects seamlessly with Windows servers, but I cannot copy/paste text through the RDP session.

You’ll find no shortage of articles online discussing different people’s takes on why Linux has not become a viable contender in the desktop market. I think there’s at least a grain of truth in some of the major ones – my Adobe production studio and DJ software will always ensure I need to keep Windows around, at least provisionally. However, what about the “Word and the Internet” crowd? I think that there are no shortage of people for whom desktop Linux would be more than practical, as can be seen in the success of the Chromebook itself.

I do think, however, it’s largely psychological. People “know Word” and “know Excel”. There is a sense of familiarity that will always be tough to overcome; I would argue that the splash screen that says “Microsoft Word 2016” is the most desired feature of the suite. On the heels of that, I submit that formal computer education today teaches “Microsoft Word”; it does not teach “word processing”. When software titles are taught, rather than principles, it makes change more difficult because there is more perceived different than what truly exists. I think that this reason, along with the “death of a thousand paper cuts”

My experience of “switch hitting” between Windows and Linux will continue to evolve. I am happy I did it. 

Why Communicators and Tricorders will never exist…or shouldn’t.

I decided to dust off my copy of the Star Trek TNG Technical Manual, and see what it had to say about the famous communication devices and “exposition boxes” that became as much a part of Star Trek as Klingons and transporters. By what I read, I’m pretty certain they will never exist.

“But Joey! We’ve surpassed comm badges already! They’re called cell phones, and you have one! How can you say they don’t exist?” Well, that depends on how we define “communicator”. A thing that lets someone else who has a thing talk to each other? Sure, cell phones fit that role in the broadest mindset. However, dig just a little bit deeper and you’ll likely agree with me that they are likely to forever remain a plot device, rather than actually existing.

Let’s start with the most obvious example of this: Neither Kirk, nor Picard, nor Sisko pay a Verizon bill, and Janeway was too far away to do so. While cell phones require the PSTN to function, communicators and comm badges clearly do not. Even if we get as close as currently possible – fully decentralized, open source, peer-to-peer voice communication software, the call is still being carried by one’s ISP, rather than communicating directly between the initiator and recipient.

According to the technical manual, the maximum range of a comm badge is 500 kilometers. Even if we cut that down to 100km, that’s still beyond the horizon of virtually any planet that could be landed on by an away team without the gravity being a crippling problem, meaning that communicators can punch through at least some of the curve of a planet. By contrast, current technology would require roughly 5,000 watts of FM transmission power to achieve something even remotely close without a line-of-site, something very seldom seen between sections of an away team engaging in dialogue. Now, to be fair, it’s highly irregular for parties to be more than a mile or two away from each other when using communicators, but while some high quality Motorola walkie-talkies might get a mile range, they require both batteries and antennas which each exceed the size of a comm badge. Moreover, communicators and comm badges only experience static when relevant to the plot – literally no cell phone owner can say that they’ve been able to thoroughly avoid dropped calls or audio dropouts.

Let’s assume that the range issues are addressed by way of “subspace”; the magical portion of the space-time continuum that powers both warp and communications in the Trek universe. The next massive concern is how communicators decide the recipient of the message. When Kirk says, “Kirk to Enterprise”, does everyone in the ship hear it? Just the bridge? Furthermore, the “Kirk to Enterprise” is frequently heard by the recipients. Even if the computer onboard the ship is ascertaining that the message is for them, do away team communicators have that same ability to discern? Ultimately, the future has no concept of ringtones, except one time toward the end of the Voyager episode “Future’s End, Part 1”. The rest of the time, the message is heard ‘on speaker’, making that scene rather strange. In another episode of Voyager, Chakotay calls “to anyone who’s left”, as the ship has been largely taken over by aliens. How does the communication system know to reference explicitly Starfleet crewmen, and do so ‘on speaker’ without the hostile aliens hearing? I hear you all saying, “It’s just a plot device”, and that’s fine, but it doesn’t jive well with the notion that cell phones are akin to the communicators in Star Trek. The amount of technology required to facilitate communication between the communicators, over great distances, establish the recipient, do so without static or interference, and perform all of these tasks without a communication infrastructure beyond the devices themselves, is far beyond anything we presently possess.

Let’s then discuss tricorders, devices that have a sensor for basically-anything, and a tiny display that makes it nearly impossible to display the results which is only eclipsed by the minuscule size of the controls. Sure, today’s phones have gyroscopes, ambient light sensors, cameras, compasses, even temperature and pressure sensors, but how accurate are the readings? Enough for a racing game, sure, but does anyone use the onboard sensors for measuring with scientific accuracy? No, they do not. Would anyone be comfortable with a doctor taking measurements with an iPhone rather than dedicated tools? That’s unlikely as well. There is still a world of difference between the capabilities of a tricorder as a scientific measuring instrument, and the capabilities of current smartphones. As a counterargument, however, it’s surprising how infrequently (if ever) data communications between tricorders and/or the ship itself are used. If the comm badges in TNG are able to communicate 500km, shouldn’t tricorders have some circuitry of that nature implemented as well? They really should be better at that, and there are no shortage of moments where data transmission or nonverbal communication would have been helpful. I’ll close that thought by addressing the idea that my thoughts on that front only stem from pervasive text messaging that was not prevalent at the time of TOS or TNG. To that, I will say that the inclusion of a small CRT display in TOS implies an intended output, and by TNG, there was no shortage of text-based communication happening over BBS systems, IRC, and Usenet. The idea of transmitting messages that way was far from foreign.

The next time you’re watching an episode of Star Trek and think that their handheld devices already exist in more usable ways, the deeper implications illustrate that there is still plenty of work to be done to achieve the levels of functionality we see used to advance the plot.