Good job MS! :)
There's nothing to stop you working with HTML5 in Visual Studio. Except for the fact that you can't use many of the features that polish the .NET-editing experience. That wasn't a problem for Microsoft until it decided HTML5 was the future of coding on PCs, devices, and the web, unveiling a very Web- and HTML-centric next …
Good job MS! :)
It is _usually_ the case that 'the work of "passionate people done in their spare time"' is what makes a company valuable to other passionate people. Not the well-planned and misplaced grand ideas some manager has blessed. Most successes within a company are 'accidental'. At least, no one higher up gave their permission for any such success.
Short version: Any innovation at Microsoft is *without* the company's knowledge.
Sure hope those passionate souls have their names noticed somewhere else besides Microsoft.
I expect they will do much the same as last time.
Those starting new projects with no legacy will avoid the proprietary option like the plague because they've seen what happens down the line.
Perhaps this time round there just won't be a migration path. In which case we've gotta hope that those Web 2.0 developers maintained a strict separation between UI and business logic, so that their client sides are really thin and therefore easy to just re-write from scratch. (Well, I say "we", but obviously that won't include their competition who are now presumably rubbing their hands with glee.)
Icon: D'oh, for all those who forgot that vendor lock-in is a bad thing.
Phew, so go to see government supporting an ailing industry.
Bet that was cheap and will be cheap to replace.
It's a shame that Microsoft appear to be moving towards a standards compliant solution; because it will make it a little more difficult to justify choosing them over a technology neutral solution.
If no one uses Silverlight what were the thousands of apps in the WP7 app store written in? Neither Mango nor Apollo (more than a year away) are moving away from .NET or Silverlight. And why then are future releases of Silverlight promised? And what makes you think .NET sans Silverlight is a bad bet for the future? And how would you, using a Microsoft stack, provide JSON or any other services to HTML5 clients without using WCF and .NET?
The way this industry takes a single statement from a vendor in complete isolation and rapes the context - to promote some obscure personal preference or agenda* - doesn't cease to amaze me.
* Are you seriously entertaining or suggesting a move to Andriod/OSX/Linux because of an as-yet unannounced tools strategy from Microsoft? If you're a CxO or even an Architect I want to know where you work so that I know whom I should be avoiding.
Just had a look at your other Reg posts. Java nut. 'Nuff said. Some points though;
VB.NET is as strongly typed as C# and produces the same MSIL that C# does.
Wat you call the horror of web coding with none of the advantages of thick client is in fact available now - in two flavours: WPF and Silverlight. Both use XAML for markup and your .NET language of choice for application logic.
.NET will "sunsetted" as much as Java will.
"Does anyone use VB.NET much? It is not a genuine substitute for what VB6 was to most people (not saying VB6 was good or bad)."
Not now, they don't. But 10 years ago it was the only migration path that didn't require you to re-write every frigging line of code in your app, so a whole boat-load of VB6 developers used VB.NET as a way of "keeping alive" their commercially successful projects. I've also heard it wasn't a "genuine substitute", but it was certainly more genuine than anything else.
Once it is in VB.NET, it becomes possible to perform a "rolling port" to any of the other .NET languages, since they are link-compatible and have almost identical feature sets and so at a pinch can be treated as alternative syntaxes for a single language. (It is probably possible to machine-translate between them. Therefore, 10 years down the line, I expect any active codebase to have relatively little VB.NET left in it.
In my experience (software developer contractor for more than 15 years) VB.NET and C# are pretty much used the same, though VB.NET is slightly less - I'd say 40% v 60% for C#. Although in the early days it had some disadvantages compared with C#, these have largely evaporated.
Just my 2c.
To quote you:
MS themselves do not use .NET to program their own applications, for the most part.
Wrong my friend. Consider that Visual Studio 2010's interface is written in WPF. Consider that SharePoint is an ASP.NET application. Consider that Microsoft Expression Studio is written at least partly in managed code. Consider that Hotmail (bad example for quality I know) is also written at least partly with .NET code running at the server end of things. Exchange Server, which relies a LOT on the Windows PowerShell which is if I recall at least partly managed code.
I agree that the latest statements from Microsoft have created uncertainty, fear and doubt. I don't like the idea of going over to www.windowsclient.net and not seeing any new content since November of 2010 in the featured new section. It bothers me too that a once interesting section of MSDN called Coding4Fun has now become all about Windows Phone 7. (A platform I really don't want to get into and one I'm sick to the teeth of hearing about)
I'm a C# developer, mostly aimed at ASP.NET applications, but still, I'm not liking what I see here from Microsoft and it just seems to me that this company is lost entirely and without any clear direction.
"Silverlight has failed, no one uses it, neither consumers or corporates."
The Netflix streaming video player uses Silverlight. You know, the #1 Internet application, measured by network traffic.
So it appears that some consumers and some "corporates" are in fact using it.
until 1995 and IE1.0....
Still traumatised by the 1st .NETified Studio release, swiftly replaced by an 'upgrade' to an earlier, slimmer, faster, usable release. So bad it made Eclipse look good!
Looks like we're in the "we've got the Frankensteined beast working well again, let's break it" part of the cycle again. Better beef up your machines...
Nonsense, Microsoft are betting on HTML5, it's all going in the next official version. This is a beta test.
That HTML is not a langage (not turing complete) and that it is not even standardized yet
They had a wonderful solution to the web pains with silverlight IF only they were ready to truly open source it and let the technology go for later build on it new tools and better solutions.
The growing amount of it out there would seem to indicate otherwise.
.NET isn't going anywhere, we're talking about a sliver of application development: "rich" web experience inside a browser. Win32 will be around forever because frankly, HTML+Backend apps suck to do anything other than buy and browse on.
.NET will be used for Win32
.NET will be used for backend (windows services)
.NET will be used for web back end (web services)
.NET will be used for web glue (ASP.NET, MVCx, etc)
HTML5+CSS3 will be used for what SL is used for. To create (or attempt) a rich in-browser experience.
The "make everything web" was a hasty move hoisted onto CIOs by marketing people. Some stuff is good for web, many things aren't. HTML5+CSS3 might level the playing field with the usability of Win32 vs browser, but probably not.
Biting the hand that feeds IT © 1998–2017