How to Turn Windows into Linux


Recommended Posts

Albeit misinformed but it was a bit funny. :)

[insert mandatory I-use-*nix-too excuse]

Link to comment
Share on other sites

The video would be funny if it wasn't based on ignorant misconceptions and clinched stereotypes:

1. Argument: Linux doesn't use file extensions.

Rebuttal: Most mime based desktop environments, including Gnome, KDE, and XFCE, use file extensions to associate different types of files with specific programs. Even the example provided, a .dll (dynamic shared library) has an equivalent file with an extension in Linux - .so, or .la for statically linking. Moreover, configuration files also often have a .conf extension.

2. Argument: Linux doesn't have a registry.

Rebuttal: Like having a registry is a good thing? LOL. The registry is the bane of Windows, and most applications store configuration files in the ApplicationData directories anyway. In Linux, data, program, shared, and configuration files tend to be highly organised based on standard locations such as /usr/bin, /usr/share/ApplicationDir/Data, /etc/init.d/ | /etc/rc.d/ and so on. The Autotools for instance provide a simple mechanisms to do with your program.

Where does the application data get stored in Windows? It could be in the registry, in the AppData for a single user, all users, or the Program Files directories, or even in C:\. It's a stab in the dark unless you know specifically where the app installs the files. With a Linux package manager, I can easily find all installed application files. And any which are generated at run time are only stored in a handful of standardised directories.

Beginning with a dot makes the file hidden. No great mystery there. Ending in 'd' usually signifies a daemon or something related in one. Once you know the names in Linux, they appear very standardised.

3. Argument: Linux fonts appear jagged

Rebuttal: If you use a bad font or no hinting/antialising, it will appear jagged on any platform, including Windows.

I use Candara with slight hinting and RGBA antialiasing, and mine aren't jagged at all, unless of course you get close enough, at which point any font gets jagged/blurred due to being composed of pixels.

4. Argument: Linux file systems pretend to be case sensitive.

Rebuttal: They are case sensitive, no pretending involved. Just like when you type in a password, it's usually case sensitive. It affords Linux greater flexibility. It's well known that *nix file systems are superior to Windows' NTFS.

And the rest? Well it's just mindless nonsense from a clueless Windows user (the person who made the video, not all Windows users).

- Almost all files in Windows have extensions. File extensions indicate the file type, it is a declaration of what the file is. AFAIK - the only exception is the hosts file. The only reason to not specify file extensions is to hide their purpose - like a communist government hide the facts from its people.

- There is nothing modern in storing configuration settings in separate text files. Registry is more of Windows settings, setup, file information, etc. Things stored outside of the registry are more related to programs and things that simply do not make sense to keep in the registry - data bases, thumbnail caches, etc. Want an example of a program that doesn't know how to use the registry? Emacs for Windows. I do admit that Windows does not have such strict Communist-style control over this.

- There is also nothing modern about having to name a file a certain way to have it be hidden. Just like communist-states tend to be less developed.

- Windows does not require any tweaking/additional setup to have fonts look nice. Just like a true democracy, you really cannot simply kill those that oppose you - like certain communist leaders did when they rose to power.

- This makes things more confusing because now you have to remember capitalization as well. Just like how confusing the economic standing of the Soviet Union was when it fell apart.

Link to comment
Share on other sites

2. Argument: Linux doesn't have a registry.

Rebuttal: Like having a registry is a good thing? LOL. The registry is the bane of Windows, and most applications store configuration files in the ApplicationData directories anyway. In Linux, data, program, shared, and configuration files tend to be highly organised based on standard locations such as /usr/bin, /usr/share/ApplicationDir/Data, /etc/init.d/ | /etc/rc.d/ and so on. The Autotools for instance provide a simple mechanisms to do with your program.

Where does the application data get stored in Windows? It could be in the registry, in the AppData for a single user, all users, or the Program Files directories, or even in C:\. It's a stab in the dark unless you know specifically where the app installs the files. With a Linux package manager, I can easily find all installed application files. And any which are generated at run time are only stored in a handful of standardised directories.

Most of your points I more or less agree with, but (my opinion) the registry is hardly a "bane", it's pretty handy and much less likely to be messed up by user error. It's a relic from long long ago that frankly needs to go away. As you said, data could be in the registry or stored in AppData or in the user's documents. In Linux, it might be in /etc, it might be in a directory off of home, or it might be elsewhere. Not much difference there really.. maybe it's here, maybe it's there, maybe should dig through the man files to be sure. It's still a stab in the dark, except you you're dealing with hundreds of little text files versus browsing a single database. Besides, working with the registry is quite easy; it's clearly organized and has an easy to use unified API to work with it, a lot easier than playing "hunt the INI file" and then guessing at how it's laid out. Besides, some Linux applications are picking up on the concept, for example GConf.. very similar, except it only handles GNOME specific stuff of course.. other applications are still elsewhere the developers decided to throw it.

Link to comment
Share on other sites

The only reason to not specify file extensions is to hide their purpose - like a communist government hide the facts from its people.

Not all files need to be associated with a specific program? The same applies in Windows too. There are files with extensions that provide no information about their purpose nor are they registered with a specific program. Are they communist programs too? The video used a .dll as an example, and I explained that Linux actually uses extensions for the same file types (shared libraries). If the video was even midly accurate, it might be amusing as a parody, but as it stands, it just highlights the maker's ignorance.

- There is nothing modern in storing configuration settings in separate text files. Registry is more of Windows settings, setup, file information, etc. Things stored outside of the registry are more related to programs and things that simply do not make sense to keep in the registry - data bases, thumbnail caches, etc. Want an example of a program that doesn't know how to use the registry? Emacs for Windows. I do admit that Windows does not have such strict Communist-style control over this.

Considering 99% of WIndows programs store files outside of the registry in various locations, I have no idea what you or the video are getting at. The registry is just a poorly implemented mess. Some use it, some don't. Its purpose is highly suspect. And finally, it's performance degrades horrendously overtime.

- Windows does not require any tweaking/additional setup to have fonts look nice

Nor does My Arch Gnome 3 machine, or Ubuntu, or Fedora, Android Phone, ....

- This makes things more confusing because now you have to remember capitalization as well.

I know what you mean. Why on earth we don't just do away with lowercase all together is beyond me. But then, that'd be communist wouldn't it. Lack of choice I mean, or is that Fascist. I can never remember ;)

Link to comment
Share on other sites

The part about turning the registry into 56000 files and shortening file names was amusing. But seriously though, the Windows registry sucks :p. I don't mind the 56000 files so long as they are organized into program folders and are therefore deleted when that program is deleted or uninstalled.

Link to comment
Share on other sites

What does that have to do with shortening the DOS Commands to be more UNIX Like?

It implies that Linux copied the commands from DOS but made them shorter just to be different.

Link to comment
Share on other sites

- Almost all files in Windows have extensions. File extensions indicate the file type, it is a declaration of what the file is. AFAIK - the only exception is the hosts file. The only reason to not specify file extensions is to hide their purpose - like a communist government hide the facts from its people.

Oh, you mean like how the default setting in Windows Explorer is "Hide file extensions for known file types"? That moronic setting is the first thing I turn OFF on a new install because it opens the door to all kinds of nasty stuff ( trojans, etc., with double file extensions such as .jpg.scr ).

Link to comment
Share on other sites

Funny how people still think that INI-files are better than the registry…

Actually, there are some advantages to having settings files stored in a file (.ini or whatever) along with the program. Much easier to simply move a program (with all of its settings) from one computer to another without needing to make special "portable" versions. Can't really do that when the program has its settings spread out in various parts of the registry, now can you?

Link to comment
Share on other sites

Oh, you mean like how the default setting in Windows Explorer is "Hide file extensions for known file types"? That moronic setting is the first thing I turn OFF on a new install because it opens the door to all kinds of nasty stuff ( trojans, etc., with double file extensions such as .jpg.scr ).

Explorer tells you what the file is. The icon and description is based on its file extension.

The normal user doesn't need file extensions.. or even understand them.

Actually, there are some advantages to having settings files stored in a file (.ini or whatever) along with the program. Much easier to simply move a program (with all of its settings) from one computer to another without needing to make special "portable" versions. Can't really do that when the program has its settings spread out in various parts of the registry, now can you?

Registry is more Windows settings than program settings and that works just fine.

Link to comment
Share on other sites

Besides, some Linux applications are picking up on the concept, for example GConf.. very similar, except it only handles GNOME specific stuff of course.. other applications are still elsewhere the developers decided to throw it.
You are aiming at dconf. And normaly the developers follow what comes from FD.o
Link to comment
Share on other sites

Registry is more Windows settings than program settings and that works just fine.

This! Futhermore data is stored in the registry with dedicated data types and in a defined way. Compare that to INIs: you may store value-keys, XML, care about white-space, ignore white-space, handle tab different from blank,… All information in INIs is stored as string and has to be parsed by the application into the right data type… There is no consistency in how data is stored in configuration files. To track Windows settings you use "regedit" on Unix you use a cli, an editor and a manual to find the damn file on the fs. Than you may also need a reference to figure out how data is meant to be stored in the files…

Link to comment
Share on other sites

I chuckled more at all the hard necks whinging about a joke in the last 3 pages.

If anything it proves certain linux distro users either need to get a sense of humour or mellow out before they fall off their high horse.

Microsoft can have a sense of humour, so I'm sure a lot of you can... :woot:

Link to comment
Share on other sites

This topic is now closed to further replies.