Mar 28, 2015
Lion Tamers; I'm about to get ugly.
"Madobe Nanami no Windows 7 de PC Jisaku Ouen Commercial!!"
To begin, I want to talk about advertising. While we all know that advertising can often exaggerate beyond the bounds of propriety, we try to assume the publishers of the advertisement in question, won't outright lie.
Not so with "Madobe Nanami no Windows 7 de PC Jisaku Ouen Commercial!!"
But first, let's get to the parts that were good.
1). The sound is passible, and the little tune, is cute.
2). The artwork is very good, but not to the standards of some of the high-art anime pieces. But what can we expect of a 1-minute commercial? It's very passible.
3). The story is, as we can assume from it being an advertisement, a bubbly piece with little relation to reality. Just like other pleasant and easy to watch anime.
4). Was the anime worthy of praise? Perhaps by genuine Windows Fans, but made me cringe.
Okay, now that I've gotten past the parts I liked, now I can talk about the stuff I don't. Which is, I absolutely hate Windows, and refuse to use it for meaningful computing. I own a lot of computers. None of them run Windows. I have become so disenchanted with it, that when I buy a Windows computer, I purchase it with the full knowledge that I'm gonna put something else on it. Windows is THAT BAD.
Let's describe Windows 7 another way. Let's concede that Windows 7 is probably as good as Windows will ever get. Keep in mind, everything following Win7 (Win8, Win10), are all based on the NT2 modules (Microsoft says so); which means all future systems will have all the problems we associate with Windows. That is, slow system updates, a really poor search engine, illogical software install procedures, drivers that don't work, games that install and work, until we load another one, and many other quirks. Even so, it is so poorly constructed (like all other versions of Windows) that all other systems; 15+ versions of Linux, 6+ versions of UNIX, MacOSX; and a few scattered alternate versions; WOULD HAVE BEEN ASHAMED TO PUBLISH IT!
Let's look at a few examples (all of which are well known by system managers and all of which create an embarrassing situation for all things Microsoft):
Let's try an example. A bank office uses an application server, and feeds many thin clients. This is a very common scenario. 17 users want to operate MS-Word. How many copies are in memory? There are now 17 copies in memory. One each for each user-call.
In any UNIX-like system, there will only be one copy in memory. But how can this be? Re-entrancy. This means that many calls from many users can be piped though the same application, and the data doesn't get mixed up.
This is a clear example of why Windows users need much more memory hardware, that any other system on the market.
Let's say we want to send data between our program and the System. We do this via the 'Shared-Memory-Page'. This memory is placed on top of any app entering memory, and is an exact copy, for all apps that are running. This is a component of the multi-tasking schema in the system.
Does it work? Yes. But since the stability of this methodology is now dependent on the reliability of each separate task, any task can corrupt the Shared-Memory-Page, and this always causes an instantaneous memory-based 'Blue-Screen-Of-Death'. Many of you have probably seen this. The system will recover from a restart in about 85% of cases. Other cases will find a re-install of Windows is required (all versions).
UNIX-like systems do this kind of communications by opening a port between programs, in the same way as Windows does to communicate with the Internet. Even if the port communication fails, which never happens (for lots of good reasons), the programs and the System task will not crash. A person can forcibly crash the Graphical-User-Interface and the System will still run.
3). The Dynamic Linking Tool
This tool is a Windows requirement for Windows Updates. But why? To understand this, we need to understand something of the internals of what makes Windows tick. Windows is what we used-to call, in the old days, a 'named system'. That means that all parts, know all the other parts.
It also means that Windows does not tolerate extensions of applications or linked-libraries (DLL). The only way to do this properly in Windows, is to use the Dynamic Linking Tool, especially useful for adding parts to a DLL, but also very useful for making sure a new part of the operating system makes proper connections with all of its' dependancies. If this isn't done correctly, you might obsolete another app, and orphan it. This would be embarrassing.
Let's look further. Windows Update sends you 14 new security patches and app-modifications. This many updates would normally take maybe 3-hours to install. We all know this. This is because, there is no quick way to install changes, or even new applications, without doing all of this dependency checking first. That takes a lot of time. It has all of the charm of repairing a knitted sweater.
But then, why do new applications install so fast? This is because most software publishers have no desire to use the Dynamic Linking Tool, to install their software. In some case, stuff like AutoCad, and some of the more serious game products, might take more than a day to install. This might piss-off a lot of Windows users. So they bypass the Dynamic Linking Tool, and install everything cold.
But how can they do this, if a given DLL needs new calls to run the program? Very simple. They have already constructed a direct replacement DLL. All they need to do is replace the old one of the same name, making sure it has the proper revision data; and voila! A fast install, including the proper DLL, which will include the new calls for their application.
Wanna guess what happens if another application wants to install, and has to use the same library as the previous example? That's right. It gets replaced again, but here's the rub, the calls needed to run the previous application won't be available. This is what causes the "... hey, the other program was working, what the heck happened? ..." syndrome.
UNIX-like systems can extend anything, anywhere. This is because every program and linked library contains hooks for inclusion of the extension. This means that the core OS files can be stored in one place, and the extensions can be installed in many other places.
One other benefit of this idea is, that when you 'Safe-Boot' a UNIX-like system, it's for real. It only boots the core modules, the extensions are ignored. With Windows, since all modules are part of a 'named-system', nothing is actually dropped in the startup, during a 'safe-boot. All that happens is that part of the exec-batch file is ignored (if there is one) normally involving some of the networking stuff. If there isn't one (like most Windows systems), tough luck, everything gets booted as always, and the networking becomes a single-stepper for diagnostic purpose. That's all.
Even worse, Windows Users are totally dependent on what Microsoft supplies, and then the user has to tolerate all the extras that come in from Windows-Update, and then have to tolerate everything that comes in by the grace of applications authors you've actually paid for; and you can begin to understand the witches brew that results. The damn things gets buggier and buggier and buggier ...
No amount of playing with the system, or cleanup, or repair tools can fix a system that has been extended almost to death. Windows literally corrupts itself over time. There used to be a webpage on the Microsoft website that pointed out that Windows systems should be restarted at least once a day, but that screen was eventually removed. Gee, I wonder why? It's interesting in that light, because if you think about your own usage of Windows, you will begin to remember that Windows gets more and more cobbled over time, and does not survive overtime well. A restart clears most of the cobbling, and all is well; for a while.
These irritations are not present in any other system. And if anyone wants to bet on the applications available for Windows, let's keep a cool head. 90% of the Windows library is junk, and nobody uses it. Most of the rest, was invented originally for Macintosh. Those are clear facts. This includes the entire Adobe Library and MS-Word and MS-Excel. That is a long story in itself, but even Microsofts' Macintosh Business Unit used-to brag about these facts for years. But since Mrs. Cho left that unit, you don't hear it much anymore.
I make this long post because I think this advertisement needs a rebuttal. This is only a partial rebuttal, there is much more. All factual, all correct; and all an indictment of virtually everything about Windows. Get away from Windows. Use something else. Virtually all versions of UNIX and Linux are free, and install on more that 80% of all Wintel hardware. I like to install UBUNTU-Linux on my Wintel hardware. Even MacOSX is built on top of FreeBSD-UNIX.
If you want to have a computer with a great software library, buy a Macintosh. I'd rather run a 5-year-old Macintosh than a brand-new Windows system. Maybe they are a bit more expensive, from the outside looking in; just remember, nobody's Windows hardware sits on a display at the Museum of Modern Art. Macintosh has two that I know of. And Apple gets kudos for industrial design every year. They work hard to produce the Cadillac of computers. UNIX Systems, including Macs, are everywhere. Remember, there isn't a single Windows server used as a stock-market transaction system on Wallstreet. Period.
Technical service approval ratings.
Apple routinely measures that at more than 75% year after year. The nearest competitor is HP at 49%
Still want to use a Wintel box? Apple is the only company in the World, that produces a consumer product that contains 12-cores of XEON chips ()yea I know about the Windows Servers with 24-cores and larger. But that's not a consumer product).
There is much more, but this is already a windy piece, because Windows is a windy product. Full of holes, instabilities, poor programming practices, functions that alienate, service plans that serve Microsoft and little else, patches that fix nothing and create problems that require more patches, performance problems which are legion and cannot be fixed because they are inherent in the Windows. Etc, etc, etc ....
I've done public lectures, and they go on for more than 3-hours, just talking about the absolute garbage that is contained in any version of Windows you wish to name.
Get away from Windows. Just leave it behind and walk away. It's the only hope you have. Or, just stick with Windows so that you can say; "... yea I have that problem too ..." Heaven forbid some of you might escape that little club (grin).
What did you think of this review?