2 ms·
"You need expensive Windows Servers to host your stuff..." I guess that depends on your definition of expensive. I've hosted my .NET stuff with http://www.disc
by Spearchucker 12y ago
"You need expensive Windows Servers to host your stuff..."
I guess that depends on your definition of expensive. I've hosted my .NET stuff with http://www.discountasp.net http://www.discountasp.net for years and yes, they're not free, they're cheap. There are cheaper alternatives than them for IIS, but I like them. They provide a good service. Free doesn't float my boat because I don't want to worry about platform installation, patching and so on. I don't want to do more than FTP to publish.
Also interesting is that I could move to Azure without making a single change to my code. So Azure doesn't lock me into anything either.
"But that's [.NET] just a dependency when you opt for the Microsoft world"
Yes. It is a dependency. If I used Node, then Node.js would be a dependency. If I used Rails, then Rails would be a dependency. I don't get that dependency problem - we're all of us always going to be dependent on something, somewhere. Unless you code up your own OS, stack and tools, and make your own hardware.
Lock-in to Micro$oft is also something I've yet to hear a commercially convincing argument against. Is it really so bad? They've been around since the 80's. They're not going to disappear soon either. They strike me as a safe bet. Why is lock-in such an issue?
If vendor dependence is really such an issue, then design (architecture, if you will) is your mitigation. Abstraction solves that problem (actually any problem, bar performance).
As ever, when I hear these arguments against Microsoft and the .NET stack I hear consistency bias. Our nearly obsessive desire to be (and appear to be) consistent with what we have already done. Once we've made a choice, we encounter personal and interpersonal pressures to behave consistently with that commitment.
Node.js is cool. So is LAMP, .NET, COBOL and GW BASIC. Your choice is the right choice. For you. For your situation. If you're going to throw stones at my choice (not saying you are), I'd like to hear how lock-in to Microsoft will burn me. And after 14 years of hosting my stuff on IIS and developing with the Express Editions of Visual Studio, I'd love to know how it is more expensive than something else that provides a comparable development experience and service.