When a programming product is first released, the public has the opportunity to try it out and accept or reject it. Microsoft also has time to create service packs to address issues that are discovered during real-life use.
Looking at Microsoft programming and operating system products, there is a window of relative stability spanning from when the product is “bleeding edge” until when it becomes obsolete. We consider “bleeding edge” to be the first 3-4 years of the product’s life when it is still being modified and updated by Microsoft. It becomes obsolete when Microsoft no longer supports it.
There are also products which are generally disliked for their lifespan. Windows Vista comes to mind. We generally recommend products that are proven reliable and we recommend using them during their lifespan between the bleeding edge, and before they have become unsupported. In other words, once they have achieved stability and are still supported.
We at msaccesstoweb.com don’t consider it our role or area of expertise to prove new products and we also recommend our users don’t get stuck with that. That’s we use well-liked products that are in the most stable part of their lifecycle.
Our default development environment currently includes Visual Studio 2010 and SQL Server 2012 on a Windows Server 2012, and we are constantly reviewing the best software and platforms available to optimize our ability to serve our customers.