Sad...
Not only an article trying to wedge the 'greatness' of Linux into a 'journalistic' format, but this article is full of misinformation and pure lack of technical understanding - it is scary.
Things like: You can't change the UI of Windows? Really? Tell that to StarDock or 50 other companies that completely replace the Shell and even have their own Window composers.
(This is one place were OSS makes people dumber, because they assume that if you don’t have the original source you can’t read or modify the binaries as well. Sure reading code from the executables is ‘harder’ but not impossible, and something real ‘technical’ people have been doing for years. Go search for uxtheme.dll or even the modifications to Windows Home versions that turn on multi-user support, remote desktop, etc. Agreed not all these methods are considered within the ‘license’, but just because the original source is not available does not make it impossible or unreadable. The reliance on having the source for an executable is a dumbing down process that is a side effect of the OSS movement.)
Moving on, how about the crazy point about the command line? (Let alone not even knowing that command.com is DOS and is from Win9X and hasn't been used for over 10 years for anything but compatibility.)
Just on the CLI issue, the author fails to mention several things, or is unaware of them.
• Everything in Windows can be done in the GUI 'without' the need for a CLI, something even OS X can't say anymore.
• Powershell is also not mentioned, and it is more than just a Linux CLI competitor, it is a revolution in CLI interfaces, as it is the first CLI in HISTORY to operate from the notion of 'objects' instead of textual piping that is found in *nix. NT has a full Object Oriented OS model and Powershell uses this native Object based OS model. Powershell deserves a look from the *nix world to see what a an Object based OS model and a CLi offer beyond dated *nix concepts.
In NT you are not limited to piping textual references, as NT understands any Object not just generic text or generic I/O interfaces. Powershell taps into this model and offers features to a CLI that is IMPOSSIBLE on any *nix. (To be a *nix the OS model can't have a object based interface and must have a generic textual, I/O model.)
Sadly this stuff is too far above the author's head to even have a chance of 'getting it', let alone what features or power this offers even the most diehard CLI proponents.
Additionally, when the author explains that the only support Windows users get is from Microsoft, they don't seem to realize the same communities and networks the Linux users resort to for help are also used by Windows users. From sites, to mailing lists, to even the NNTP groups dedicated to helping users, are all available for Windows users, just as they are for Linux users, and used even 'more' since there are more Windows users.
Microsoft even realizes the community help and support aspect and has provided specific Newsgroups for Windows since the early 90s, and Vista and XP even install these in the built in Newsgroup clients for the users and reference them for users that need help with an issue.
Ironically, the Windows NNTP groups for example have existed longer than Linux has existed, and yet this author pretends like they only exist for Linux. WTH?
I don't have time to go through the rest of the article trying to offer some factual context of the article's bias or inaccuracies. So read with one eye open and even resort to freaking wiki or a technical search to gather real facts that are more than an author's love of their OS.
|