The top 5 programming languages on the current Evans Data Corporation list

Decide for Yourself..!!

Was .NET a Mistake?

If .NET lives on with added support for HTML5+JavaScript, then of course .NET was not a mistake. But if Microsoft ditches .NET for JavaScript or something completely different, then .NET — the last great legacy of Bill Gates — will indeed be all for naught.
.NET showed great early promise as a unified multi platform framework, but Microsoft made a terrible mistake right out of the gate by splitting Win Forms and Web Forms, thus requiring two sets of code for Windows and Web applications. Over the years, many new flavors of .NET popped up, such as the Compact Framework, Silverlight, WPF, MVC, etc. Each is very useful in isolation but represents yet another fork in the .NET road.

Some may claim that a multi platform framework is an enduring, unachievable fantasy. Maybe HTML5+JS on PhoneGap will eventually deliver on this promise. But the key point is, because Microsoft failed to build a unified, multi platform framework in the 2000’s, it found itself seriously behind the technological curve when the smartphone and tablet markets exploded in 2010. Now iOS and Android have a firm grip on the mobile markets, WebOS is dead, RIM is dying, Microsoft is desperately trying to hold on to its measly 1.6% market share.

Regardless of what happen in the future, .NET was not a mistake. The mistake was Microsoft failing to deliver on .NET’s original promise as a unified, multi platform framework.

Is .Net Dying?

The perception – and rightly so – is that .NET is dead. As a result, developers are fleeing .NET in droves, either to Objective C on iOS, Java on Android, or HTML5/JavaScript for web apps. Of all my .NET developer friends I have accumulated over the years, only one remains committed to the .NET platform, and that’s because he has an employer paying him good money to build .NET business applications. Actually the total is two, if you include me.
Microsoft has committed a major FUBAR on .NET.

Microsoft promises to reveal all at its BUILD Conference in September. But six months is an eternity in the technology business. Meanwhile, all of the hype and energy seems to be flowing into iOS and Android, and Windows Phone seems deader than a doornail.

My hope is that .NET isn’t dead, and that Microsoft will reveal a new, improved .NET that includes some sort of HTML5/JavaScript generation that will allow .NET developers to build true web apps. On the other hand, if .NET isn’t dead, then why is Microsoft ignoring it? Hopefully perception is not reality in this case.

So what’s a developer to do? If I was starting out fresh today, I’d
learn XML+ HTML5+JavaScript. It’s the current best bet for building
truly platform-independent and vendor-independent software for Web v3.0.
I probably wouldn’t learn .NET first unless I had a good paying job
that required it.

But what if you are a VB.Net or C# veteran like
me who has a significant investment in .NET code, tools and experience?
Microsoft will likely come through with a workable solution for .NET
developers, so your investment in .NET will probably be preserved. But "change is a constant in software development, and if you’re
itching to learn something new, XML+HTML5+JavaScript is an excellent
choice."

As a disclosure, I have no alliance or allegiance
to Microsoft. I’m just a paying customer and vocal critic. But I’m
also a .NET fan. Though I’ll have to admit that I’ve been spending a
lot of my free time lately messing around with PHP+JavaScript+XML, which
is powerful yet flawed and needlessly complex in places. And i Strongly Believe its the Future of Web B'Coz XML is designed to
transport or to store the data as well as it is language Neutral That
Means a java Program can generate an XML file and this file can be
parsed by Pearl...! Moreover XML Files are OS Independent Which is the
Future of Technology..!!