Operating Systems > Linux and UNIX
Serious question for WIN advocates
badkarma:
From a programmer who has been working with linux a bit over a year, but never used it before that time (i.e. me):
I would kill myself if I ever had to program using windows again. Buggy and crashprone IDE's, sloppy MS API's (puh lease... the WIN32 API is a fucking joke, MFC is a OO wrapper around the W32 API which makes it even more horrible, because there are a lot of functions with a zillion parameters of which you only use a small portion, if you see the code a few months later you'll have to look twice to see what's going on)
If I had to code for windows again, I'd just use a cross compiler, code under linux and once in a while build a windows version (using magnificent toolkits like Qt or SDL)
Visual Basic teaches you *extremely* bad programming habits (it is not ok for a programmer to get used to the fact that his language has some kind of magical built in typecasting system, which makes for some incredibly ugly code).
The only thing which could be considered an advantage a windows developer has is autocompletion, however this is a moot point imo because it does not greatly speed up a programmers work and it creates mindless programmers who don't truly know the tools they use, and this is also available for linux (with Borland's Kylix 3.0
And the greatest advantage yet is that for practically any library you use you have the source code available, now this greatly speeds up development time because it is much easier to find out what is going on if you can step through library functions with a debugger.
The miriad of debugging tools available are pure heaven, nothing (and I mean nothing) available for windows can touch the strace command.
Compile times under linux are a lot faster then compiling the same program under windows. Linux caches all the files it needs for the make process and has no HDD activity while compiling (I have a lot of RAM ;) ), windows has a lot of HDD activity. On big projects this can differ a few minutes per build.
Now these are all technical (and imnsho irrefutable) points linux has over windows.
oh and eh....
[puts on spelling nazi cap]
you had thirty years (according to your profile) to become at least a little bit proficient with your own language yet you manage to create sentences like the following:
quote:
So this was your points???!!!
--- End quote ---
quote:
What you've been smoking?
--- End quote ---
quote:
You can read your email without getting virus? I can also!
--- End quote ---
Now excuse me, but I'm nine years younger then you, english is not my first language and I can even produce better sentences than that crap.
Let me guess, english is the only language you know too?
[takes off spelling nazi cap]
www.unixsucks.com:
No, English is not my native language. My native language is Russian. Satisfied?
Have you seen VB.NET? If you have not then please don't post article about how bad VB is without digging down.
voidmain:
I knew you would lie, just like Microsoft always does, about getting out of our hair. No, I have not seen VB.NET. Can you give us some reasons as to why we should switch from our tried and true languages to this one?
dbl221:
Every company or Hopital I have worked for has had a policy of testing ALL software in the lab before it is installed in production. This is done for very solid business and technical reasons. With the new M$ OS versions and Licence arrangements you are forced to have unauthorized software installed throughout the organization. This is of course NOT in the best interests of the organizations which use M$ crapware...er I mean software.
I would love to know why BIG and I mean BIG companies put up with this situation. Perhaps unixsucks dude can explain this to me.
badkarma:
quote:No, English is not my native language. My native language is Russian. Satisfied?
--- End quote ---
ok, then I will leave my spelling nazi cap off ;)
(it's just that your credibility is directly related to the effort you put in your posts)
quote:
Have you seen VB.NET? If you have not then please don't post article about how bad VB is without digging down.
--- End quote ---
Without ever having seen VB.NET I am 99% sure that they did not change a damned thing to my biggest gripe with VB, the magical typecasting (i.e. use a integer DIM, then use it as a string, then use it as a double). You cannot imagine how hard it is to maintain code like this, further most time critical stuff is done in C/C++ and then used as a .OCX or a .DLL with visual basic.
Visual basic programs are slow, and on most win9x systems you'll get the added bonus of having to download a few Mb's of DLL's over a 56k6 modem to run a program of 500Kb.
Furthermore, all my other points still stand (if you would have read my post you might have noticed that it didn't only cover VB).
[ August 21, 2002: Message edited by: BadKarma ]
[ August 21, 2002: Message edited by: BadKarma ]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version