That is a personal opinion. To me it's not a "Con", just a personal choice. I work on both platforms (Windows and Linux) and I don't view either one as a Pro or a Con. Just a different environment. If it's not your first choice doesn't make it a bad choice, which I think summarizes a lot of the article in question.
It would be interesting to see someone build a Django-like platform on top of C#.
How does IronPython perform?
They do?! Oh dear, I'd better tell the DBAs about that.
They only need to use windows if they want to run IIS or Visual Studio.
There is a hell of a lot more to the sort of infrastructure a lot of people use .Net for than that. Hell I was working with a bizarre mainframe relic last year in it.
That isn't to say for a lot of usages, anything that isn't the latest windows is a poor relation, the latest debugging features for TPL require 8.1.
You mean the MS SQL DBA's? Cause generally that's what people in MS shops are going to be working with, should they not be able to run tests on MS SQL and write SQL scripts locally to actually test on their environment and get results? Perhaps I do not understand what being a DBA actually entails, but I assumed that it would necessitate extensive experience with the actual database, up to and including running it yourself locally for development?
I'm assuming you're talking specifically about Sql Server because there is no technical reason you can't use MS tech with Node, Mongo or MySql.
What about Sql Server doesn't scale horizontally?
Sql Server was scaling horizontally in the enterprise space since 2005.
And also, all the fancy middleware ( memcache, lucene, whatever ) that we put in front of MySql to scale it these days work just fine with Sql Server.
Re NoSQL solutions on windows, theoretically possible, sure, but which NoSQL solution targets windows as its primary platform rather than an afterthought? If you file a bug report, will they notice or care?
RavenDb.
It does if the target area is massively underrepresented in the tech stack in question. It's just a plain old fact that there are far more options for NoSQL storage layers built with linux first in mind than there are windows. Just like there are far more options for games toolkits and libraries built with windows first in mind than there are for linux.
RavenDB I had never even heard of before, but it does look like it fits the bill of NoSQL datastore that primary targets windows, compared to the competition though that doesn't come near to nullifying my point that it's a vastly outscaled matchup. Also, if you even want clustering in RavenDB, you need an enterprise license. There are many completely free NoSQL datastores for linux that handle clustering just fine without an enterprise license.
Re MongoDB, it's good that they fixed that, however;
https://jira.mongodb.org/secure/IssueNavigator.jspa?sorter/f...
So there are 117 Windows specific issues with mongodb, many of which have not been touched for years or months, and none of which affect linux.
I couldn't actually find any tickets which only pertained to linux, though maybe they're there they're certainly not as common.
Edit: I think one of the largest probmems is most developers doin't understand SQL or databases that well. Indexed Views for example are an incredibly efficient tools that allow you to avoid a lot of expensive joins without the normal risks of denormalizing your data. However, try and think of the last time a developer mentioned them.
I think performance is pretty similar between the two also last I checked. And you can setup PGSQL with a drbd failover without that much hassle. What are the licensing implications of running two windows servers with an MS SQL server failover? Do you actually need to purchase two copies for that?
Um,what? Please try out latest msysgit and tell me what's not great about it.
?
What about Visual Studio makes git behave badly?
"When you exit the program you get to keep all licenses free with all future patches. We exited the program 2 years ago and have yet to buy a MS license for IIS or SQL."
Are we really going to pretend that never upgrading their software is an option?
For the sake of technical correctness, I'll agree with you, yes its true that you don't get "hammered" when you leave Bizspark.
You get "hammered" when you get 5-7 years into the Microsoft ecosystem and realize that you can no longer put off the software upgrades.
At that point you have to do the math and figure out which is cheaper:
throwing away most of what you have learned and rewriting your software using completely different language and ecosystem
OR
Dropping "5 figures" on software licenses.
Where does the "5 figures" figure come from? An InfoQ interview with the guys behind Tekpub who dropped MS for Rails after being in Bizspark:
"RB: If the platform was holding up fine, what prompted the change of architecture?
RC: Money. We were enrolled in Microsoft BizSpark Program and it was great for getting off the ground, but projecting into the future we realized that everything - from our database down to our development environment would have to be paid for after 3 years. We also figured that we'd probably need a separate server to run videos properly (for streaming) to Silverlight (using Streaming Media) which would be another license cost - and, in addition, we'd need to buy Media Encoder in order to encode the video for Smooth Streaming.
This might not be an issue for a large company, but when we sat down to assess what the bills would be - well let's just say that it was about 5 figures. We put our business hats on and tried to justify that cost - and we couldn't.
Not only that, James and I both knew Rails pretty well. We realized we could push everything into the cloud with better streaming and throughput for a microscopic fraction of the price - so that's what we did.
JA: As Rob mentioned cost was one of the factors, BizSpark is great but it is basically a ticking time bomb. I think more than cost though the motivating factor was around what we both wanted to be using day to day. ASP.NET MVC and .NET are very lacking in some areas that are very important to us. The testing story on .NET is not the best, you have to jump through a lot of hoops to design your application in the right way to handle testing and then writing the tests themselves is not as clean or usable as some other languages. One of the other areas of high friction was deployment, there are ways to handle it in .NET but nothing as nice or clean as Capistrano.
RB: So what does the TekPub platform look like today?
RC: We moved to Rails 2.3.5 using MongoMapper against MongoDB. We have a reporting setup that uses MySQL to track stuff we need to report on which uses DataMapper. We also plugged in New Relic RPM to keep track of our site and it's health - all of this is less than 1% of what it would have cost us, on average, with BizSpark. "
None of your windows based software will scale well horizontally, especially at the storage layer compared to the competition, and if you're relying on bizspark for the price advantage, you should also mention it expires in 3 years and you then either have to go full in to microsoft licensing and massively increase your software spend, or drop your engineering investment in the past three years and go with something off the MS stack. It sure is a neat trap from microsoft's perspective, but it's a pretty shitty deal for anyone that actually looks at it economically and long term.
On the other hand, if you build your apps around a horizontally scalable storage solution (of which there are about fifty hojillion these days on open source stacks) you have near infinite ability to scale upward by just throwing more boxes at the problem. Visual Studio may be very pretty but for a nice IDE you drop a well behaved git, and everything that goes with it.
You also lock your software engineer options to people that are satisfied working on the MS stack, which whilst acknowledging that anecode is not data and all, in my experience means that you will get poor results.
If you look around and all you see is masses upon masses of startups pursuing fairly similar infrastructure strategies, you should probably think very hard about why everyone else thinks you're wrong before you're certain you're not.
From my perspective the equation looks like this;
Pros;
Visual studio.
MS CLR performs well against python / ruby / php.
In a single server environment, you can probably get away without any sysadmin expertise.
Cons;
Everyone has to use Windows.
Storage layer doesn't scale well horizontally.
Git not so great. (apparently this no longer applies and msysgit works perfectly well now)
CLR may perform well compared to interpreted languages, but not so great if you're willing to go a bit more esoteric or if you're happy with boring old java.
Application server scaling is largely the easiest part of any horizontal scaling stack at any rate, minimising the significance of your competition using even extremely slow interpreted languages.
Licensing fees are infinitely more than the (typically free) competition. When BizSpark expires, even moreso. And you bought yourself a nice solid vendor lockin by using their sandpit in the meantime.
You're stuck with microsoft monoculture and all the associated baggage that implies from a HR and strategy perspective.
Most of the stuff everyone else is using that you might want access to works either not at all or poorly on windows, meaning when you run up against the same problems as your competition, they'll have more ground on you from the get-go. (ansible, redis, practically every NoSQL db in existence, etc etc etc, pick a problem space you need to find a solution in and compare the MS CLR based options to "everything else" and MS rarely comes out on top unless it's dealing with MS proprietary formats or interfaces in some way)