Slashdot Mirror
Explaining The Windows/UNIX Cultural Divide
giampy writes "Joel Spolsky writes a review-like article on the last book of Eric S. Raymond (The Art of Unix Programming). His views on the cultural differences among Windows and Unix programmers are well explained. Overall, an interesting read." Also on the topic of Windows, badriram writes "Microsoft is reorganizing the windows team, it seems the are separating the
OS core development. Seems like things heading in the right direction in creating a more secure OS, and making it more business oriented. Read the
article here."
Windows programming is like playing golf, UNIX programming is like pig wrestling, after years of development on both platforms I feel that UNIX programming gives me the satisfaction of sport achievements, the unforgiveness of UNIX makes very thrilled.
Joel Sposky writes a review-like article on the last book of Eric S. Raymond
I hadn't heard that he died. My condolences to his friends and family. He will be sorely missed.
Why are you letting these clowns ruin our country?
Does the story of how the divide between windows and Unix came about start with fallen angels?
Don't worry, plenty of slow readers have gone on to lead successful lives.
The whole point of this article is to see how many /. readers actually get to the end of it.
"slashdot-karma-whoring sectarianism" is tucked way down near the end in the last paragraph. Over 40 posts already and nobody else has spotted it yet!
Skiing? Check out The Independant Skiers Portal
What? You expect Linux users to tolerated having to type in obscure commands in obscure places? That's just not a realistic expectatoion to put on the users!
I put it forth that this "review-like article" is competely "domestic bovine excrement"-like.
Here are some of the best/worst bits:
Huh? What exactly is return code 0, then? Or syslog entries? And how do you distinguish between cases where the program output was correct and cases where the output was incorrect but the program was unable to decide this?
By contrast, in the Windows culture, you're programming for Aunt Madge
Funny that. What does Aunt Madge do with all the hundreds of complicated scientific/industrial/financial/simulation software packages that exist for Windows (as well as Unix)?
Here again, we see that the Unix culture values creating code that is useful to other programmers, something which is rarely a goal in Windows programming.
Huh? What does reusability and well-documented interfaces between modules have to do with the platform? Did ESR really write this crap or is the "reviewer" making it up as he goes along?
The Windows programmer will tend to start with a GUI, and occasionally, as an afterthought, add a scripting language which can automate the operation of the GUI interface.
I wonder which specific Windows programmer this sentence refers to. Hopefully one that's been fired for incompetence by now.
When Unix was created and when it formed its cultural values, there were no end users. Computers were expensive, CPU time was expensive, and learning about computers meant learning how to program. It's no wonder that the culture which emerged valued things which are useful to other programmers. By contrast, Windows was created with one goal only: to sell as many copies as conceivable at a profit.
And commercial Unixes are created with what goal again?
Aunt Marge can't really use Unix
Can't even keep the lame metaphors consistent.
That's OK; he's not a Windows programmer; we'll forgive that.
Huh? If somebody writes a book pretending to be an expert on something they're clearly not, I'd call that bornerline fraudulent and at least take any viewpoints offered with a huge mountain of salt.
If the actual book is even half as bad as the review makes it out to be, maybe Eric S. Raymond should go back to writing the Nethack Guidebook. It probably has more insight on Windows software development.
that Windows programmers hurt their arms and wrists after clawing their way through one too many pull-down menus while Unix programmers hurt their pinky fingers after a heavy emacs session in the world of Control Meta.
As a result, Windows programmers have spastic arms from all this GUI action, looking like zombies from Night of the Living Dead, while UNIX programmers have hands curled up like Igor from Frankenstein's Lab.
"Provided by the management for your protection."
Would you mind sending me your IP? I'll send you a check.
My only hope is that slowly, without forcing him, he will see that there is something behind my comments and tips. Maybe a light will go on, and he will decide to take a look.
It sounds to me like you are trying to get fired. But, since I am looking for a job at the moment, what company are your working for?
I'm willing to get paid to sit around letting the system fall apart -- then heaping all the blame on the boss. That works for me... it's a built-in promotion.
Once the boss is out of the way, I can fix the stuff... built-in raise + respect from upper management.
Once I have acheived that state, then I can coast to retirement... built-in retirement plan. This part, of course, requires hiring people to do the actual work... and you'll need a job. I could probably talk them into rehiring you.
When will Windows be ready for the desktop?
Hey now, less works on Windows, too.
needs complete, fully functional, headache-free solutions for their specific needs
So they use Windows?????
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Thankfully slashdot wasn't spawned from the VAX world.
Think of colonbracketsemicolondotcom.com