Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Microsoft Windows Technology

Devs Worried Microsoft Will Dump .NET 440

joelholdsworth passes along a story summing up concerns from developers that "Microsoft seems to be set on adopting HTML5 and JavaScript as its main application development tools for Windows 8," and asking, "is this the end of .NET?" The article continues: "To bet the farm on HTML5 and JavaScript being the next big thing is a good bet, but it's not a bet that Microsoft can easily take and make good. Even if the world does turn to JavaScript and platform-independent apps, this still means that Microsoft loses. The problem is that Microsoft needs a technology that gives it an edge, and HTML5/JavaScript is everybody's edge. Microsoft developers feel left in the dark and very angry at the way they are being treated. You only have to browse the Microsoft forums to discover how strong the feeling is: forum post 1, forum post 2 and an open letter." Reader Sla$hPot points out a similar story at OS News.
This discussion has been archived. No new comments can be posted.

Devs Worried Microsoft Will Dump .NET

Comments Filter:
  • Why worry. (Score:3, Insightful)

    by LWATCDR ( 28044 ) on Monday June 13, 2011 @03:23PM (#36427826) Homepage Journal

    When has Microsoft ever just killed off a technology that they pushed? Next thing you know will be telling me that VB6 and FoxPro are in danger of going away.

  • Short Answer? (Score:5, Insightful)

    by OverlordQ ( 264228 ) on Monday June 13, 2011 @03:24PM (#36427836) Journal

    No.

    If you watch the presentation for what it really is, what they're saying is if you want the 'New Hotness' flashy canvas, yes your apps will have to be HTML/JS. No, they're not going to throw away everything out there, you'll be able to use 'old and busted'.

  • by EraserMouseMan ( 847479 ) on Monday June 13, 2011 @03:25PM (#36427840)
    HTML5 isn't a .NET killer anymore than LCD TVs are a Hollywood killer. HTML5 excels at the GUI. .NET is mainly used for server-side processing. Long live .NET. Long live HTML5.
  • by A Friendly Troll ( 1017492 ) on Monday June 13, 2011 @03:28PM (#36427900)

    The developers worry about Silverlight and WPF, not .Net in general. .Net will still have its place for desktop apps and it will still be used as a server-side web platform. Silverlight and WPF have nothing (well, almost nothing, to the point of being inconsequential) to do with that.

    But this is Slashdot, and that's Soulskill...

  • by Yold ( 473518 ) on Monday June 13, 2011 @03:28PM (#36427906)

    JavaScript is a great language, but using it for full-blown enterprise app development would be a major setback. Strongly typed languages are great for the enterprise, because you know (and Intellisense knows too) at compile time what to expect from objects.

    Furthermore, I'd speculate that the performance of the .NET Virtual Machine is miles ahead of any JavaScript VM. I cannot recall hearing about any JavaScript VMs that support multiple threads either.

    Shit like this makes me not even want to come to this site.

  • Re:Doubtful (Score:5, Insightful)

    by MightyMartian ( 840721 ) on Monday June 13, 2011 @03:34PM (#36427986) Journal

    And just imagine, all this effort just to reinvent what C did 40 years ago.

  • by JustSomeProgrammer ( 1881750 ) on Monday June 13, 2011 @03:40PM (#36428076)
    +1 Agree. Javascript and HTML 5 I think is great for client side, but server side? I don't really want to write JavaScript for talking to a database.
  • Re:Oh, dear, god.. (Score:5, Insightful)

    by afabbro ( 33948 ) on Monday June 13, 2011 @03:44PM (#36428120) Homepage

    I surely can't be the only one praying that they do drop .NET?

    Yes, you are. .NET is one of Microsoft's better ideas.

    Or perhaps you're a VB6 man...?

  • by MightyMartian ( 840721 ) on Monday June 13, 2011 @03:59PM (#36428308) Journal

    It's hardly "simple prejudice". First of all Mono sucks and does not offer anywhere near the current .NET experience. Mono developers are stuck a generation behind.

    Second of all, there are many reasons not to trust Microsoft or its technologies, and damned few reasons to trust it. It's not like .NET does things so incredibly well that other platforms are left in the dust. Mono is not a killer app, any more than .NET is.

  • by Jeremiah Cornelius ( 137 ) on Monday June 13, 2011 @04:15PM (#36428516) Homepage Journal

    Is there nothing so shrill, so piercing? When they finally realize that they directed enthusiasm - even affection - and invested personal identity in a corporation, they are still so enthralled that they feel betrayed instead of enlightened.

    Look. Microsoft, Apple, Google? You are just a bit of tissue and they will wad you up, when finished wiping. Apple wipes their nose, while Microsoft wipes somewhere lower in the anatomical procession... Small comfort to reflect upon, as you trace an arc through the air, upon disposal.

  • Re:No. (Score:2, Insightful)

    by BitZtream ( 692029 ) on Monday June 13, 2011 @04:25PM (#36428614)

    Because OpenGL support for Windows sucks! Sure, the drivers are fine, but if you actually want to use a modern version of the API, you need to do a lot of faffing about checking for extensions, and get a pointer to a fnction bofre actually using it. There's also no official OpenGL wrapper for .Net.

    Seriously? Your argument is that you don't like using the P/Invoke methods to deal with OGL extensions and you don't want to use a non-official OpenGL.NET wrapper even though there are several that work just fine?

    Your post SCREAMS lazy/crappy developer.

    You may not be, but your post really makes you sound like it.

  • by shutdown -p now ( 807394 ) on Monday June 13, 2011 @04:29PM (#36428690) Journal

    In this particular case, the reason why people are up in arms is because .NET stack is actually significantly better than HTML5/JS stack at pretty much everything except for portability. As a language, C# (as of v4) roundly spanks JavaScript - it has every single feature of the latter except for prototypes (and even that you can emulate), and deals away with most of the flawed design decisions that have to be maintained in JS for the sake of back-compat (like semicolon auto-removal, or dynamic scoping of "this). As a framework, it's so far ahead it's not even something you can compare.

    Of course, no-one said anything about .NET being dropped so far. People are making conjectures based on limited data, someone makes a pessimistic conclusion, and that enters a positive feedback loop where folks sit in the circle on the forums, and are exchanging opinions about how awful things are, with tone set bleaker and bleaker with every new iteration.

  • by Anonymous Coward on Monday June 13, 2011 @04:31PM (#36428708)
    Corporate developers use .Net because it is fast to build apps and get business done instead of fiddling with window handling routines and manually drawing things on screen. Surprisingly, many different development toolsets all have a place. Things like Java, .Net, Native Code, HTML5, etc. - all have a place where they make sense. However, the few folks who may be whining about HTLM5 and Javascript taking over for .Net are a bit clueless. .Net is actually very performant. Javascript - well, let's just say it is not performant. Javascript also isn't strongly typed, doesn't support robust error handling, and is only attractive at all as a least common denominator tool to allow web apps (like say Google Docs) to function. Ever tested the speed of something like Google Docs though against apps that do a ton more like say Open Office or MS Office? It isn't even close because Javascript just isn't something you would want to code an app that needs to do any code in for an app that requires performance. It also can't easily tie into the native APIs of any operating system services. So, .Net is not going anywhere. Native Code isn't either. It is just for those small apps like MS showed so far for Windows 8 touch devices - a weather app, an app that shows HTML5 video. A Twitter feed. Nothing serious. When they needed something more serious up came Excel and it wasn't done in Javascript.
  • by geoffrobinson ( 109879 ) on Monday June 13, 2011 @04:33PM (#36428730) Homepage

    .NET isn't quite the same thing as Silverlight. Dropping .NET would be a much bigger deal, and I don't expect that to happen anytime soon.

  • by Malc ( 1751 ) on Monday June 13, 2011 @04:42PM (#36428802)

    I don't know why JS gets such a bad wrap. It's got some really cool features, like closures and dynamic functionality like being able to compile and execute any string. With syntax very familiar to Java/C++/C/C#, it's easy to pickup and write object based code.

    For those wanting to break out of the sandbox on Windows, Microsoft has allowed creation of COM objects for a very long time. I guess those are the roots of AJAX too.

  • by Anonymous Coward on Monday June 13, 2011 @04:55PM (#36428950)

    No, his statement completely forgets about you and thousands of developers who use .NET because they don't know C/C++.

    Right. Because C/C++ is all there is. The only tool for every job. Plus, it's what Real Programmers(TM) use.

    Grow up.

  • Re:Why worry. (Score:4, Insightful)

    by Required Snark ( 1702878 ) on Monday June 13, 2011 @06:38PM (#36429956)
    Microsoft Flight simulator was dumped in 2009. It was not only used for aircraft simulation, but also for geographic information systems. Microsoft was lying to these users even after they shut down the group supporting the project, but the truth came out from the laid off employees. Locheed picked up the professional version recently and is supporting their version. I have no idea what this new version means to the GIS projects that were using it. I assume that many of the GIS users are completely screwed at this point no matter what.

    Why does anyone think that NET users are any less disposable then the GIS users?

Our business in life is not to succeed but to continue to fail in high spirits. -- Robert Louis Stevenson

Working...