Slashdot Mirror
Is Windows Ready For Joe Longneck?
Carewolf writes "Is Windows ready for the desktop? We have heard it year after year, that now is the time for Windows on the desktop. But is it really time? Richard K. Yamauchi at OSNews don't think so and has writen a piece that list a number of issues that needs to be solved before Windows is really ready for the masses and "Joe Longkneck"."
.NET Framework SDK is FREE
... so what exactly was your point about not being able to develop for free?
No, you don't get the Visual Studio development environment, but you CAN compile VB.NET, C#, or C++ code with it.
If you want a visual dev environment and still don't want to pay for it, try sharpdevelop
If you'd done some research before posting, you'd have realized that your criticism is unfounded. Additionally, there's nothing stopping you from getting GCC running under windows as well. You also have perl, python, or any number of other languages
"Therefore, since this is not a common failing (as you yourself admit it might not be), and since similar problems on Windows are as complex to find a solution for, your snide remarks at config file editing were uncalled for..."
.. uh. registry! Yeah! And it.. uh.. well I'll make up something and present it as a devastating blow to your case! That way, I won't have to answer the tough questions about how usable Linux really is! Yeah!!"
My comment was very much called for. First off, your example is not relevant. The problem with Nvidia's card (assuming that problem ever existed, let's pretend it did) was not Microsoft's fault. Video support in Windows works very well. If it took a registry hack to make the Nvidia card work, then Nvidia fucked up pretty bad. Know what that means? It means that Linux is just as vulnerable to problems like that. Only, to fix a problem like that, you better know your way around shell.
Secondly, MS provides you with a UI to install, configure, and troubleshoot video card problems. If KDE or Gnome has something like that, I've yet to find it. Strike 2 against Linux.
"I did point out that in the vast majority of cases your comment is inapplicable"
So let me get this straight: Having to enter shell and edit a text file is a totally acceptable way for Joe Longneck to maintain his machine? Sorry bud, you missed my point entirely. I'd try to explain it more clearly if I thought you would respond rationally, instead you're trying to attack my credibility. Pity though, you really should listen. I'm a Systems Analyst. My job is to make my company's products usable. If that's not credibiilty enough to let you know when something's broken from the user-end point of view, then you are ready to be promoted to Mindless Linux Zealot.
"Your sneer of 'how typical' is more typical of Linux-bashing MS astroturfer trying to deflect attention from the fact that he's been caught out."
Heh. I could say the same for your response to my comment. "Oh yeah? Oh YEAH?! Well Windows has the
You're nitpicking the details (like a true MS Bashing Linux Astroturfer) trying to prove that the problem I had didn't really exist. So yeah, you deserved the 'how typical' comment.
"Problems will happen on any system, but if you can't even do enough research to find out that your problem is not common, you shouldn't be surprised if people give you attitude."
How am I or John Longneck supposed to know if it's common or not? That's exactly what this thread is about. You Linux Zealots think the user has to know more about their computer than they should to make it work. It's your attitude that it's not called for. "Well your problem isn't commmon, so we don't need to address it'. Bull-fucking-shit. What happened to me is exactly the type of problem that'll make somebody say "Fuck it, I'm installing Windows. It works."
So yeah, I can undrstand your defensive attitude. You were 'caught out' just like the guy who started this thread predicted. Thank you for illustrating his point.