- Risking Microsoft's ire by breaking the licenses
- Locking yourself in to long-term Microsoft licensing
This was a pattern I saw in many, many startups in the 90s -- organizations that relied first on UNIX systems for their servers (often times Solaris, Linux, and in the early-to-mid 90s, IRIX), would eventually adopt Microsoft products for some component of their infrastructure -- usually Exchange, based on heavy political pushes from the growing number of business users.
This always to the same effect -- the Microsoft products spread due to lock-in network effects until it began to near 100% MS on the desktop, e-mail, and corporate servers. Production servers generally remained UNIX due to the costs involved. The IT organization shifted to MS, costs went up as the staffing necessarily increased to support administering Windows systems, expensive political maneuvering arose between engineering and business as they both fought to move to systems that they thought better aligned with business priorities.
At the end of the day, everyone wound up locked to MS with heavily entrenched political interests in keeping the status quo (and the job security that went with it).
Having seen the fall-out from migrations to MS products in corporate IT, I can't imagine voluntarily implementing MS as the primary production and developer system at a startup. You're locking yourself out of alternative solutions, you're signing up for significantly increased capital and operational expenditures, and perhaps most importantly, you're excluding an entire class of software engineers that primarily work on UNIX-based (including Mac OS X and Linux) systems.
There's tremendous value if it's what you already know. The opportunity cost associated with learning and becoming reasonably competent in a different development stack can be non-trivial, especially if you had 5 to 10 years of experience with a different stack or set of technologies. I've yet to encounter a new framework/API/stack/language which I've been able to move to in only a few weeks and be 80%+ as productive as what I already knew, as there's often lots of useful minutiae, subtleties and new concepts you need to acclimatize over time.
>You're excluding an entire class of software engineers that primarily work on UNIX-based (including Mac OS X and Linux) systems.
The converse also applies. Granted, a competent engineer can learn anything, however you're initially inclined to pass on them because of the associated ramp-up time.
If all you know is Microsoft, then that's all you can do, and the organization's technical direction will almost certainly model that initial decision.
However, if you have the luxury of choice -- and I think most people do -- I'd advise against it. The short and long-term costs of Microsoft lock-in are decidedly "non-trivial". The considerable investment in staff, licenses, and technologies make it very difficult to migrate to a non-Microsoft stack in the future.
The converse also applies. Granted, a competent engineer can learn anything, however you're initially inclined to pass on them because of the associated ramp-up time.
In my experience, you're entirely locking out engineers who use Linux and Mac OS X when you move to a Microsoft stack, but you're not necessarily locking out Windows engineers when you use a cross-platform stack.
I speak from personal experience -- I know the .NET stack very well, and am very familiar with the LAMP stack from my days with PHP, but I've only dabbled in Ruby and Python. Before starting work on our startup, I considered writing it in Rails, but the reality is that it would have taken me much longer to get to market. We hit the market at a very opportune time, and were able to ride a nice wave of buzz to sustainability. If we'd waited another couple of months (my guess at the added overhead of learning Rails), we may have missed our window.
The same would naturally apply to someone who already was well-versed in, say, Rails -- it would make no sense to learn .NET unless there was a very compelling reason (say, you were writing a Windows desktop app).
Not to mention that the first app you write using any technology you don't understand well is going to suck. If I'm going to base my livelihood on a product, I want it to be as well-written as possible, so I'm going to go with what I'm best at.
Also, it's absolutely not true that you're locking out Linux and Mac developers when you write .NET. Some of the best .NET developers I know use a MacBook Pro as their primary machine.
Sometimes price isn't the only factor when deciding which tools are best for the job. After using C#, switching back to Java or a non-compiled language would be very painful. I'd lose a lot and miss it.
What do you use for desktops, e-mail, corporate servers, etc?
My goal was elucidate the hefty cost of Windows lock-in and Window's demonstrably strong tendency to pervade your organization in terms of political, staffing, and technological investment.
If it's considered the best tool for the job and these recognized costs are acceptable, then there's no reason to not use it -- but history should also provide some insight into how Microsoft behaves with organizations that become reliant on their technology.
Microsoft isn't being magnanimous with Bizspark -- they're trying to ensure that more startups are locked into their technology stack early, when the perceived immediate advantages may seem most attractive.
VMware is not an adequate solution for day-to-day development. There's a performance impact, significant memory overhead, and running Windows inside Linux/Mac OS X is not any more accommodating to users familiar with a UNIX environment than simply running Windows natively.
I have been writing .NET code exclusively in VMware for 5 years now, 2 years on Windows and 3 years on a Mac. The performance impact is there but it isn't a deal-breaker (especially if you have a fast HDD and enough memory (6GB)).
Confirming neither is a drop-in replacement, which isn't to say that Mono isn't useful or valuable, but simply that it is necessarily 2nd-tier in a Windows-focused development environment.
Given that you've spend 3 years developing C# in VMware on a Mac, I'd ask why you're not using native Mono/MonoDevelop entirely?
I have been writing .NET code exclusively in VMware for 5 years now, 2 years on Windows and 3 years on a Mac. The performance impact is there but it isn't a deal-breaker (especially if you have a fast HDD and enough memory (6GB)).
What do you see as the significant advantage of .NET that has warranted using non-native tools with an admitted performance impact exclusively for 3 years?
This sounds like individual developer inertia, not a high-level business decision.
In the last 6 months I have been investigating moving my application to Mono and running on Linux servers, when that happens I will use Mono and MonoDevelop exclusively for that project. Of course other client projects I will still use VMWare and Visual Studio since they will be deployed on Windows.
The reason I didn't look at Mono earlier is that I had dedicated Windows boxes and didn't see a benefit in moving, now that I am on EC2 there is a price motivation to move.
Running in a VM is not a big deal, most .NET developers I know do all their client development in a VM even if they are running Windows.
That's a very bad argument. If you're super strapped for cash what are you doing with closed source software anyway ?
It's not like there aren't plenty of free alternatives.
I think that mostly boils down to what your experience is.
But the GGP effectively encourages people to break both their license agreements and the law.
If you're strapped for cash you also don't get a free ride to go and steal stuff.
If the price of being strapped for cash would be to have to learn how to set up open source software then so be it. But given the fact that you could easily make a business turning over a couple of 100 grand annually using just apache and (forgive me) PHP means that if you choose to abuse an MSDN subscription to be able to use closed source proprietary stuff that you are doing so deliberately.
I really have a problem with effectively encouraging people to break the law in a public forum, even if the manufacturer of the product has some hidden gain from this behaviour.
I tried for a few days to use Visual Studio to link some C++ code to a DLL that was supplied by a third-party vendor. I never got it to work. This was literally "hello world" calling a function in a DLL, and I couldn't get it to compile.
After much googling and asking around, I gave up and used gcc instead. It worked the first time.
As someone who has always used free software, I always assume that if someone gives me very expensive proprietary software, it will be problem-free. It hasn't happened yet.
This is why you haven't success with MS stuff. For people who have always use MS stuff, it's faster and easier to stick on the stack.
Learn more at http://www.microsoftstartupzone.com/BizSpark/Pages/At_a_Glan...
Microsoft has been a great partner and deserves better from me. If I could still edit my original post I would. For the record, Loopt was and is always compliant with all commercial and OSS licensing.
> # Enrollment is free, just pay a USD $100 program offering fee at program exit.
That's like saying 'Free car, pay in 36 months'.
Well suited to a startup, whom are usually looking for minimal outlay from the get go.
I must disagree with this one point. I cannot see a justification for taking software illicitly like that. In my opinion, VS and SQL Server are well worth their price, but if you disagree the answer is to use open source software not take it like that.
Aside from that, I think you have some very good points. I am primarily a SQL Server DBA and I think that for many applications it is the best RDBMS available. I am also a fan of Visual Studio for certain types of projects (though I also make use of Python).
I really enjoy the tooling, the documentation, and the libraries. There is exactly one time we've run into an issue with the built in libraries: The documentation didn't match what really happened, but Microsoft confirmed this for free and fixed the docs.
Visual Studio is rather polarizing. I'd say the developers at Loopt fall into three camps: Like it, miss Eclipse, and still use Emacs. You don't have to use it. I can't type more than 20 WPM; Intellisense is so good I haven't felt the need to learn to type properly.
Cost wise it's really not a problem. There's BizSpark which is great for three years, but after that you can get into their SPLA licensing program. It lets you pay per month for only what you use. See http://www.microsoft.com/serviceproviders/licensing/default....
Loopt started before BizSpark, so we know what it costs. Here's a hint: we paid more per month for Office and Exchange than we did for the software running our service. All in it was less than hiring an intern.
If you're super strapped for cash, just get an MSDN subscription, and use it for everything. It's not legal, but Microsoft knows there's more money to be made by letting you become successful (at which point you pay real money for licensing) than there is in going after your initial few counts of infringement.
If you like getting into the guts of things you might not like .Net, even though they've released many of the symbols and source code. See http://msdn.microsoft.com/en-us/library/b8ttk8zy(lightweight... That said, you can't edit it. I'm ok with this though because in my experience it just works. I'd rather focus on developing my product than fixing the tools and runtime I'm using.
The open source .Net scene is a little touch and go. There are some great projects out there, many by Microsoft itself, but it's simply not as robust and vibrant as the Linux open source community. This seems to be changing (slowly), but as I said earlier we've found compelling reasons to have a mixed environment.
I'm not saying it's all good. ASP.Net is a valiant attempt to solve the wrong problem. Drag and Drop doesn't work for the web. .Net MVC is much better. Despite that, our website is written in Rails, and communicates with our back-end using Thrift. It works great.
If you want to know more let me know. Maybe I'll write a blog post.
Edit: Grammar