3 Reasons Why EVERY OS Fails as an OS

June 7, 2016 | Views: 5571

Begin Learning Cyber Security for FREE Now!

FREE REGISTRATIONAlready a Member Login Here

3 Reasons Why EVERY OS Fails as an OS

I recently read a post regarding Windows’ failings as an operating system and decided to call out some issues with every OS in the same format. I’m only going to focus on the three biggies: Windows, OSX, and Linux.

Moreover, I’m going to focus Linux on the distros with the most market share. Given the top two share a common base, I’m gonna stick with Ubuntu.


1)      Recognition of Files

a.       Windows recognizes files by extension. Things have to be named correctly or it’s going to get very confused.

b.       Linux and OSX also recognize files by extension. If you double click on a .dmg or a .deb file in OSX or Linux, respectively, and it’s a text file, the OS is gonna get confused and drop an error.

c.       If you’re writing applications, you should do pretty to call any file with any extension as long as the application knows to render the file properly.

2)      Single Point of Failure

a.       The Registry is Window’s biggest flaw. If it corrupts, the whole OS is going down.

b.       Linux has many of its config files in a single place (/etc, sometimes /proc). If either of those folders have any sort of corruption, the OS can fail pretty quickly.

c.       OSX has the properties lists. They do a better job of separating everything into different places, but if something breaks, good luck finding what you need.


3)      The OS is Spyware

a.       Windows 10 has some pretty controversial things in its EULA. It can look at your keystrokes and it can look at your files. It’s kind of terrifying.

b.       Linux has its own very similar demons to Windows:

i.      Ubuntu “may also send your keystrokes as a search term…” to Ubuntu servers, and selected third parties to help your search be successful. If you use their dash search.

ii.      Error reports can also contain personal information.

iii.      Some of these have opt-outs, others don’t.

c.       OSX’s EULA has its own terrifying section:

i.      Section 2 sub P states that “By using the Apple Software, you agree that Apple may download and install automatic updates onto your computer and your peripheral devices.” Essentially, Apple controls your updates, and could theoretically brick peripherals it doesn’t like. You don’t control any of that. (Sound familiar?).

ii.      Sections 4 and 5 essentially cover all of the ways Apple can access and manipulate your data. And, that you agree when using some services, your data is sent to Apple. (Don’t forget that using many of these also requires you to agree to the AppleID License agreement, which is a whole other beast).


The long and short of it is that no OS is perfect and you should always read EULAs. It’s just the way the world is. Keep an eye on what’s going on around you, pay attention to what you agree to and be careful how you use your tech. That’s really what matters.


Oh yea, Have a pleasant day. 

Share with Friends
Use Cybytes and
Tip the Author!
Share with Friends
Ready to share your knowledge and expertise?
  1. If Windows can record our keystrokes, then can a virtual keyboard be used? Will it still record them?

  2. btw, there is no solid way to do “Recognition of Files”. Even if you had to check heading…1) It’s definitely not a gurantee. 2) You would slow down OS too much…3) Half the time you will be wrong.

    • As for the development I was referring to importing non-binary files. When it comes to binary files things get trickier, but there is no reason you shouldn’t be able to import and render the information from a non-binary file in a development project. Even binary files should be ok to work with as long as you, the developer, understand what it is you are working with.

      When it comes to the O/S recognizing files by other than extension, you hit the nail on the head. An O/S is not going to be able to validly determine the type of a file without some sort of indication from the user (usually in the form of file extension).

  3. What about Juliar OS :)?

  4. Not every OS was covered here though. Misleading title aside, this is why on a Windows 10 platform I would use something like AntiBeacon to break their spyware abilities.

    As for Linux, stay away from Ubuntu. As for custom file system control, not much of that on Windows as far as I’m aware but Linux distros can be customized. Although I must also ask if you’ve come up with a system yet that can retire the way file extensions are read or would rid Windows of the registry. Otherwise the article is informative if someone doesn’t know about the file systems or some of the OS’s spyware.

    • It’s true, I could only cover some OSes, but for the layperson these cover the most well known. There had to be limits to the article, and I did what I could to get the most important things covered.

Page 1 of 41234»
Comment on This

You must be logged in to post a comment.

Our Revolution

We believe Cyber Security training should be free, for everyone, FOREVER. Everyone, everywhere, deserves the OPPORTUNITY to learn, begin and grow a career in this fascinating field. Therefore, Cybrary is a free community where people, companies and training come together to give everyone the ability to collaborate in an open source way that is revolutionizing the cyber security educational experience.

Support Cybrary

Donate Here to Get This Month's Donor Badge


We recommend always using caution when following any link

Are you sure you want to continue?