Language Selection

English French German Italian Portuguese Spanish

Looking at the computer experience

Filed under
Linux

I want to start at the basics. Just like when I first went to computer networking classes and we worked on Novell Netware. Yeah, it's been awhile.

Question, what is a computer?

Answer, a computer is the material components connected together to perform specific tasks. ie... motherboard, memory, processor, video card, usb ports, serial ports, monitor, printer, mouse, keyboard, etc...

Question, what is an operating system?

Answer, an operating system is a collection of software that allows all the material components of a computer to communicate and interact. It creates an environment in which other software applications are able to interact with the computer in order to perform their intended purpose.

Question, what is an application?

Answer, a software application is software that works to allow a person or another program to perform tasks. It interacts with the operating system and the computer to complete those tasks. ie.. a word processing application allows users to type on a computer as if it were a typewriter then perform other tasks for editing, storing and/or printing those document files.

Now as I was going through my training as a network technician/administrator those years ago, our world, as network folks, dealt primarily with the computer and the operating system. Few end user apps really held much interest or use for us except where they related to connectivity, network access, etc...

Back then, Windows was still in DOS and by the time I was done, Windows for Workgroups 3.11 was the new thing.

Believe it or not, Netware wasn't altogether too different from Linux in my opinion. It was all command line, you had dang well better make sure your syntax was correct and people still complained that Windows wasn't playing nicely.

Back then we talked about our role as support providers for users on a network. What do people "do" on a computer?

People need to access or "log in".

People need to create and store files locally and on remote network servers.

People need to access services and devices both locally and remotely such as printers.

Back then, there was somewhat of a divide between systems. Local computers were said to run a Disk Operating System. Servers ran Network Operating Systems.

Local computers ran Windows or Apple. They were focused on the GUI and that's what the typical user saw and interacted with.

Servers ran Unix or Netware or the like and were command line oriented and it was considered a digital sin to suggest using a GUI on a server.

Now Linux is based on Minix which is based on Unix which is historically known as a network or server operating system.
My perspective is that Linux is suffering from the same problem as Windows and even Apple to a degree, but mostly Windows which is trying to be everything to everyone. Essentially, it wants to be the powerhouse, stable and reliable server operating system but be a user oriented, local machine operating system at the same time.

Let's go way back to mainframe days for a minute. The server operating system had to be a multi-user system by the nature of it's design and implementation. Lot's of people sitting at dumb terminals all logged in to the server and frequently, the same apps, at the same time.

Windows came in and initially, reversed that. One computer meant one user at a time. There was no way you were going to log in multiple users simultaneously. MS had to adapt Windows as it went along when they realized that the "one computer, one person" rule they had set wasn't going to be sufficient.

Linux is coming from the opposite direction. It has multi-user access natively built into it. It IS a server OS before it is anything else. The adaptions have to come from the single user end for Linux.

Hundreds of Linux distributions have been created trying to make that ideal mashup of Linux into a single user like OS.

Why do people use computers? To do things, to complete tasks. What aspect of the computer do people interact with the most? The apps that allow them to do those tasks.

Linux needs apps. You might say that Linux has apps, thousands, tens of thousands of them. You would be correct. At the same time, Linux developers who want Linux to be used by people other than technicians and developers need to understand that the average user wants "pizazz".

Finally, we have some apps that are nearing that goal. Open/Libre Office is one for example. Thunderbird, chrome, firefox. We need more however, many more.

In terms of solving the ideal single-user system for Linux, I think Android has the ticket. They make use of the powerhouse capabilities of the server operating system, but only show the user the stuff they want to use, the apps.

A smartphone is not a laptop or desktop and people like to keep familiar things familiar. The efforts by many developers to turn desktops into smartphone look-alikes is going to backfire because end users are usually smart enough to know they are not using a phone.

To be honest, I don't think Linux will hit it's desktop "sweet spot" until the main user interface/menu is voice driven and frees the monitor real estate up to show the user only the apps they tell the computer they want to see.

More in Tux Machines

Openwashing: Zenko (Dual), Kong (Mere API) and Blackboard (Proprietary and Malicious)

Games: Descenders, War Thunder’s “The Valkyries”

Kernel: Virtme, 2018 Linux Audio Miniconference and Linux Foundation Articles

  • Virtme: The kernel developers' best friend
    When working on the Linux Kernel, testing via QEMU is pretty common. Many virtual drivers have been recently merged, useful either to test the kernel core code, or your application. These virtual drivers make QEMU even more attractive.
  • 2018 Linux Audio Miniconference
    As in previous years we’re trying to organize an audio miniconference so we can get together and talk through issues, especially design decisons, face to face. This year’s event will be held on Sunday October 21st in Edinburgh, the day before ELC Europe starts there.
  • How Writing Can Expand Your Skills and Grow Your Career [Ed: Linux Foundation article]
    At the recent Open Source Summit in Vancouver, I participated in a panel discussion called How Writing can Change Your Career for the Better (Even if You don't Identify as a Writer. The panel was moderated by Rikki Endsley, Community Manager and Editor for Opensource.com, and it included VM (Vicky) Brasseur, Open Source Strategy Consultant; Alex Williams, Founder, Editor in Chief, The New Stack; and Dawn Foster, Consultant, The Scale Factory.
  • At the Crossroads of Open Source and Open Standards [Ed: Another Linux Foundation article]
    A new crop of high-value open source software projects stands ready to make a big impact in enterprise production, but structural issues like governance, IPR, and long-term maintenance plague OSS communities at every turn. Meanwhile, facing significant pressures from open source software and the industry groups that support them, standards development organizations are fighting harder than ever to retain members and publish innovative standards. What can these two vastly different philosophies learn from each other, and can they do it in time to ensure they remain relevant for the next 10 years?

Red Hat: PodCTL, Security Embargos at Red Hat and Energy Sector

  • [Podcast] PodCTL #50 – Listener Mailbag Questions
    As the community around PodCTL has grown (~8000 weekly listeners) we’ve constantly asked them to give us feedback on topics to discuss and areas where they want to learn. This week we discussed and answered a number of questions about big data and analytics, application deployments, routing security, and storage deployment models.
  • Security Embargos at Red Hat
    The software security industry uses the term Embargo to describe the period of time that a security flaw is known privately, prior to a deadline, after which time the details become known to the public. There are no concrete rules for handling embargoed security flaws, but Red Hat uses some industry standard guidelines on how we handle them. When an issue is under embargo, Red Hat cannot share information about that issue prior to it becoming public after an agreed upon deadline. It is likely that any software project will have to deal with an embargoed security flaw at some point, and this is often the case for Red Hat.
  • Transforming oil & gas: Exploration and production will reap the rewards
    Through advanced technologies based on open standards, Red Hat deliver solutions that can support oil and gas companies as they modernize their IT infrastructures and build a framework to meet market and technology challenges. Taking advantage of modern, open architectures can help oil and gas providers attract new customers and provide entry into markets where these kinds of services were technologically impossible a decade ago.