QUOTE: 'This is a product that integrates with windows using XML to store all of your information on Microsoft servers, so any computer in the world can be used as "your" computer.'
TRANSLATION: This is a product that only integrates with windows using BUZZWORD to keep all of your DATA on Microsoft "servers", so any hacker in the world can use your "computer".
Lot easier to make client/server models with Unix
on
Why Develop On Linux?
·
· Score: 1
I'm a senior level developer who's done a fair amount of network development in both Windows and Unix environments. I can say first hand that when it comes to building complex client/server (or worse...n-tier) models Unix is much more efficient.
Bringing up multiple instances (read 64 Meg) of Visual Studio each with its own project or workspace brings the poor little Windows box to its knees. With VS 5 and above you can bring up multiple workspaces with a single instance of VS. In my experience this hampers the development cycle more than helps it as the 'multi-workspace' Visual Studio environment A)gets cluttered B) is hard to debug C) behaves extremly buggy.
In Unix it's no sweat. Just pull up multiple X terms each with an editor of your choice (nedit, emacs, vi, whatever). You can have one virtual terminal for your clients, one for your servers and your ready to rock. Hang a process? NO PROBLEMO. CTRL-C or KILL -9 (if you background some executabes) and your in the clear. God forbid you should hang a process in VS AND you have multiple workspaces 'alive' within it.
Slashdot Mirror
Buddy...a quick reality check.
Children born without deformities, defects or diseases is a *good* thing.
It's a little to early to be writing off our 'poorly inadequtate' society just yet.
Satan Oscillate My Metallic Sonatas
QUOTE: 'This is a product that integrates with windows using XML to store all of your information on Microsoft servers, so any computer in the world can be used as "your" computer.'
TRANSLATION: This is a product that only integrates with windows using BUZZWORD to keep all of your DATA on Microsoft "servers", so any hacker in the world can use your "computer".
I'm a senior level developer who's done a fair amount of network development in both Windows and Unix environments. I can say first hand that when it comes to building complex client/server (or worse...n-tier) models Unix is much more efficient.
Bringing up multiple instances (read 64 Meg) of Visual Studio each with its own project or workspace brings the poor little Windows box to its knees. With VS 5 and above you can bring up multiple workspaces with a single instance of VS. In my experience this hampers the development cycle more than helps it as the 'multi-workspace' Visual Studio environment A)gets cluttered B) is hard to debug C) behaves extremly buggy.
In Unix it's no sweat. Just pull up multiple X terms each with an editor of your choice (nedit, emacs, vi, whatever). You can have one virtual terminal for your clients, one for your servers and your ready to rock. Hang a process? NO PROBLEMO. CTRL-C or KILL -9 (if you background some executabes) and your in the clear. God forbid you should hang a process in VS AND you have multiple workspaces 'alive' within it.
end