10 Linux features Windows should have by default
The battle between Linux and Windows will most likely rage on for years to come. I can foresee that even when all things migrate to the cloud, users in both camps will still be screaming the virtues of their favorite operating system. And, of course, I will be one of those campers (and I can bet you know just which camp I’ll be in). But being in that camp does not preclude me from seeing the benefits and strengths of the Windows operating system.
|
|
|
Comments (26)
6 earlier comments in the full thread.
I thought it was sheep dip.
It's interesting the assumptions the author makes. The assumption that everyone will move to cloud computing.
Same thing, Bob. It's a dip used on farm animals (sheep being a primary one) to kill fleas and ticks.
The interesting thing here, is that if they are genuine features, and not just something that some software or hardware manufacturer refuses to support Linux with, or has made impossible for a Linux hacker to write by the use of patents, then it will get developed for Linux.
I know, I just like the way "sheep dip" rolls off the tong. Toung. Tung. Tong. Oh darn, where's that dictionarey when I kneed one?
Of ten Windows things, at least one will lead to a security risk.
Quoting:phsolide: Is there any way to easily read all comments? Having to click each and every comment to read it become highly annoying after 3-4 clicks.
In ZDNet, click on "flat view," and you'll get all the comments in one chunk. I think I'm i_debian at ZDNet, but I rarely comment over there.
Oh, and it sucks at everything else too.
I'm doing a government contract as some of you know. They have Windows XP exclusively on the desktop and a mix of servers including Novell NetWare 6.5 and Windows Server 2003. I look at the amazing amount of work done to clean up the flaws and problems which are unique to Windows, everything from registry corruption to malware infestations which crop up despite all the best software to prevent them, and all the lost hours doing that work which is simply unnecessary on other operating systems and marvel at the fact that anyone still uses Windows. Heck, management is so sold on Microsoft and so convinced that Linux isn't really enterprise ready that I no longer waste my breath. Meanwhile I'm using a Linux live CD I created to track down and solve network issues that nothing else they have could track down. The waste of taxpayer dollars is staggering and yet nobody can seem to sell management or the politicians on anything other than Windows. Oh.. and I'm working in the state capitol which is also the home to Red Hat.
Anyway, I was assured over and over again that NT was in fact, multi-concurrent user back in the 1994-1995 time frame. What the heck? Was I mislead back then, by folks who went on to lead portions of Microsoft?
If you added cygwin or OpenNT (later Interix, later WSFU, later ???) you could have multiple concurrent logins. http://en.wikipedia.org/wiki/Interix
You just had to add the GNU stuff!
All kidding aside, I have always seen Windows boxes running in single user mode, but the last time I worked on Windows for a living was in the Windows 3.11 days running on Novell networks, so my experience is pretty limited.
Some people on the web seem to have achieved it: http://ajitmonteiro.wordpress.com/2007/03/13/how-to-enable-c... http://www.blogsdna.com/2336/enable-multiple-user-accessconc...
Gee Windows is soooo hard! you have to type all that command line stuff to do what comes with Linux already! Windows will never make it the marketplace because of that! (OK, all kidding is not aside!)
Primarily it is for remote administration but it can be set up for multiple simultaneous users. I first used it as NT 4 Terminal Server Edition with a MRP/ERP application. It was later released as a part of the desktop OS but with a lot of monetary-based restrictions. I've used it with the Linux terminal server client for running Adobe Illustrator remotely from a customer's workstation.
This doesn't mean it's secure or stable. With Vista I found it convenient to reset the workstation by launching Access 12 (2007). This usually caused the workstation to reset within a few seconds.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Sign up and post (it is free) or Log in and post

There are two standard answers to that. The more family friendly one is flea dip.