A lot of the posts on this blog are a bit over the top, foul language and completely biased opinions, but this quote is hilarious:
If you upgrade your version of Windows and an application breaks, it’s Microsoft’s fault. If you upgrade your version of OS X and your application breaks, it’s the ISV’s fault. If you upgrade your version of Linux and your application breaks, well, that’s your own damn fault.
Linux Hater’s Blog: Mini-Rant
Another win for ScottGu and Microsoft! Well done! And this I believe is the way Microsoft should continue to do business in the future. Some might see it as embrace and extend, and in some respects it is, but in a good way. Take my word for it.
jQuery and Microsoft – ScottGu’s Blog
Perhaps the biggest call we made for Rosario was to drop support for SQLServer 2005. Rosario will only support SQLServer 2008 and later. That was a controversial decision but it is a final decision. The primary driving force behind it is that the Report Server feature in SQLServer 2008 is sooooo much improved over that in previous versions that we simply could not pass up taking advantage of it for Rosario.
Huge change in the next version of TFS! No support for Sql Server 2005 is huge! Hope everybody is getting the message!
If I were to deploy TFS now and be prepared for the future I’d order two boxes; one with Hyper-V installed and running a VM with Windows Server 2008 and the application layer installed. The other box would be a W2K8 with Sql Server 2008 on. On box number 1 I’d also add at least one more VM to use as a build server. depending on what kind of software you’re producing you might want a third VM for test installs of your software (ISV). Hyper-V is cheap, fast and simple. It lacks a bit compared to VMWare ESX, but that’ll come in v.Next. I believe the 80/20 rule is in effect here.
bharry’s WebLog : Charting a course for TFS "Rosario