4 ms·

My time doing deployments and dealing with Windows Server issues is not free. We don't have any issues with our Windows servers, but I guess the number of issu

My time doing deployments and dealing with Windows Server issues is not free. We don't have any issues with our Windows servers, but I guess the number of issues you run into is proportional to your experience. We would have a lot more problems dealing with Linux servers. YMMV. Neither is the time lost using RDP instead of SSH Practice makes perfect... dealing with licenses What? You buy it, you install it, done? requiring much more HD space than the alternatives Now you're just being silly. Are you worrying about HD space in this day and age? Seriously? and lacking real scripting solutions. I'll give you this, but I've yet to see the need for such an environment. I have yet to hear anyone using LINQ on anything that's not SQL Server Don't use it then? I think LINQ is a horrible idea, and horribly implemented, so I'm staying far, far away from it. I would never use it or SQL Server in a startup, that would be insane. I see how you could accidentally recruit someone who thinks it's the best thing EVER and starts using it all over, but recruiting people addicted to the wrong bleeding-edge technologies is a hazard no matter which technology you use.

epochwolf 16y ago
Have you even looked at how much bandwidth RDP uses compared to SSH? I can have 7 or 8 ssh connections open and monitoring files where windows can't get one remote connection working properly. As for installing, Debian/Ubuntu can't get any easier. apt-get install <package> And if you need the very latest nginx? wget <url> tar -xzvf <tar.gz file> cd <folder> ./configure make make install Even better, you can script this with bash with little effort. (Complex scripting can be more difficult but that's not what we are doing here)
- pbz 16y ago
  You're comparing apples to oranges. One is graphical while the other is text based. I've personally never had issues with RDP and bandwidth. If you have multiple connections open you can minimize the RDP window; the connection is maintained but the window is not refreshed so it doesn't use your connection.
Daishiman 16y ago
Deploying a Linux server on my environments takes exactly 5 minutes. Most Windows Server installations run over half an hour, require babysitting, and quite a bit of time previous to that if I want to make a custom image, a process which I can't really automate. Using SSH is a much, much better solution for administration. I don't depend on having a large screen or fast connection. Believe, when you're managing servers 8000 miles away it makes you want to tear your eye sockets out. Licensing. You must be kidding. Keeping track of license numbers, WGA validation, and being artificially limited in how I can move OS images around is nothing pleasant. I don't want to depend on anyone's approval for purchasing licenses; I need to download, burn, and deploy. > I'll give you this, but I've yet to see the need for such an environment. I've been a UNIX sysadmin, I've seen my Windows counterparts. Please do take the opportunity, if you have the chance, to learn about shell scripting on Unix. It's incredible. > Don't use it then? I think LINQ is a horrible idea, and horribly implemented Alternatives? I don't know of comparable alternatives. I don't think NHibernate would be right, neither do I want to go back to validating raw SQL.

epochwolf 16y ago

Have you even looked at how much bandwidth RDP uses compared to SSH? I can have 7 or 8 ssh connections open and monitoring files where windows can't get one remote connection working properly. As for installing, Debian/Ubuntu can't get any easier. apt-get install <package> And if you need the very latest nginx? wget <url> tar -xzvf <tar.gz file> cd <folder> ./configure make make install Even better, you can script this with bash with little effort. (Complex scripting can be more difficult but that's not what we are doing here)

pbz 16y ago
You're comparing apples to oranges. One is graphical while the other is text based. I've personally never had issues with RDP and bandwidth. If you have multiple connections open you can minimize the RDP window; the connection is maintained but the window is not refreshed so it doesn't use your connection.

Daishiman 16y ago

Deploying a Linux server on my environments takes exactly 5 minutes. Most Windows Server installations run over half an hour, require babysitting, and quite a bit of time previous to that if I want to make a custom image, a process which I can't really automate. Using SSH is a much, much better solution for administration. I don't depend on having a large screen or fast connection. Believe, when you're managing servers 8000 miles away it makes you want to tear your eye sockets out. Licensing. You must be kidding. Keeping track of license numbers, WGA validation, and being artificially limited in how I can move OS images around is nothing pleasant. I don't want to depend on anyone's approval for purchasing licenses; I need to download, burn, and deploy. > I'll give you this, but I've yet to see the need for such an environment. I've been a UNIX sysadmin, I've seen my Windows counterparts. Please do take the opportunity, if you have the chance, to learn about shell scripting on Unix. It's incredible. > Don't use it then? I think LINQ is a horrible idea, and horribly implemented Alternatives? I don't know of comparable alternatives. I don't think NHibernate would be right, neither do I want to go back to validating raw SQL.