Slashdot Mirror


Is Microsoft's .NET Ecosystem On the Decline?

Nerval's Lobster writes: In a posting that recently attracted some buzz online, .NET developer Justin Angel (a former program manager for Silverlight) argued that the .NET ecosystem is headed for collapse—and that could take interest in C# along with it. "Sure, you'll always be able to find a job working in C# (like you would with COBOL), but you'll miss out on customer reach and risk falling behind the technology curve," he wrote. But is C# really on the decline? According to Dice's data, the popularity of C# has risen over the past several years; it ranks No. 26 on Dice's ranking of most-searched terms. But Angel claims he pulled data from Indeed.com that shows job trends for C# on the decline. Data from the TIOBE developer interest index mirrors that trend, he said, with "C# developer interest down approximately 60% down back to 2006-2008 levels." Is the .NET ecosystem really headed for long-term implosion, thanks in large part to developers devoting their energies to other platforms such as iOS and Android?

164 of 250 comments (clear)

  1. Non-story by Anonymous Coward · · Score: 5, Insightful

    Submitted by Nerval's Lobster? Check
    Shilling for Dice? Check

    1. Re:Non-story by JMJimmy · · Score: 2

      Submitted by Nerval's Lobster? Check
      Shilling for Dice? Check

      I love that everyone hates the cross-promotional crap they try to do.

    2. Re:Non-story by jenningsthecat · · Score: 1

      But isn't it kinda cute that Dice thinks anyone *anywhere*, (never mind here on /.), takes their pontifications seriously enough to give a crap?

      --
      'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
  2. Dice? LOL by Lunix+Nutcase · · Score: 5, Funny

    According to Dice's data,

    Did they read tea leaves or chicken bones?

    1. Re:Dice? LOL by Anonymous Coward · · Score: 5, Funny

      According to Dice's data,

      Did they read tea leaves or chicken bones?

      I think they just rolled the.... never mind. That was way too easy.

    2. Re:Dice? LOL by Lunix+Nutcase · · Score: 2

      Nah, that seems to be way too accurate for Dice.

  3. Desktops vs Mobile by Anonymous Coward · · Score: 1

    Remind me again why phones and tablets needed a different programming language?

    1. Re:Desktops vs Mobile by lgw · · Score: 4, Insightful

      Remind me again why phones and tablets needed a different programming language?

      This is why the one hope for C# is MS's partnership with Xamarin (but I think it's a good one). C# as a cross-platform alternative to Java would be all sorts of wonderful - but I won't believe it until it actually plays out that way. If a year from now there were no gotchas, I can really write an app* in C#, test it on my desktop, then sideload it into an Android and an iThing and get appropriate interfaces, and no surprises have happened with licensing? Well, that's a bright future for C# IMO.

      It also doesn't hurt C# that Unity have become the "gateway drug" for game devs, giving another cross-platform venue for C# for those who choose it (it has hurt the Steam store, but that's another story).

      *cue the "app" troll

      --
      Socialism: a lie told by totalitarians and believed by fools.
    2. Re:Desktops vs Mobile by Guy+Harris · · Score: 2

      Remind me again why phones and tablets needed a different programming language?

      For iOS, the current main programming language not a different programming language for the one heavily used for OS X desktop applications. (And the language Apple would like to see be a main programming language is also intended both for iOS and OS X.)

      For Android, you have an OS with a different history; it uses a different language from the ones heavily used for applications on desktop operating systems, and, as they didn't try to make it into a desktop operating system (not many very open niches in that ecosystem), that didn't turn it into a popular language for desktop platforms. As for why they chose Java, well, maybe Andy Rubin liked it for some reason.

      For Windows Phone/Windows RT/whatever, Microsoft didn't go for a different language from one of the languages for the desktop. Why they went .NET-only, I don't know.

      So phones and tablets don't need different languages from laptops and desktops; the mix of languages is different for historical reasons.

    3. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 4, Interesting

      Perhaps, but that begs the "why not just go with Java?" question, since it supports both Android and every desktop OS (and lets face it NOTHING runs on both iOS and everything else, that's a pipe dream, unless you want to do QT stuff, which is great, but begs ANOTHER question, "why not just use QT/C++?").

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    4. Re:Desktops vs Mobile by Nethemas+the+Great · · Score: 1, Informative

      Java is increasingly being seen as problematic and a liability, particularly as it relates to security. Much of Oracles efforts remind me more of throwing stuff against a wall and crossing fingers. Its history has given it a lot of momentum but people are starting to get nervous.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    5. Re:Desktops vs Mobile by lgw · · Score: 3, Informative

      Perhaps, but that begs the "why not just go with Java?" question

      Java is .. not very good. I've alternated between Java and C# professionally over the past 8 years or so, and while they used to be quite similar, C# is worlds ahead now (thanks, Oracle!).

      lets face it NOTHING runs on both iOS and everything else, that's a pipe dream,

      Check out Xamarin. "With a C# shared codebase, developers can use Xamarin tools to write native iOS, Android, and Windows apps with native user interfaces and share code across multiple platforms. Xamarin has over 1 million developers in more than 120 countries around the world as of May 2015."

      There's a reason this is MS's last, best hope for C#. If the Xamarin stuff is bundled free with Visual Studio 2015's free version (as has been promised, but we'll see), it will be something special. If it were anyone but MS, I'd say right now this was going to be a huge win, but it's such a big change in attitude for MS - well, we'll see.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    6. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 4, Informative

      Actually Java ON THE DESKTOP has no more security implications than any code written in any other language. Worst case it does something nasty, and Java does NOT sandbox your primary application thread or any of its spawn unless you specifically configure it to do so. So DESKTOP Java is a non-issue.

      As for web-browser Java plugins, those are just like all other plugins. They've proven to be open to a number of exploits. If you wouldn't use Flash or Silverlight why would you expect to be able to use Java? I mean I wish Oracle would FIX these issues, but my guess is every piece of web-exposed code in existence is riddled with an endless supply of these security holes, not just plugins.

      On the SERVER side there's again no issue, Java is no more or less a security problem than any other application running on your server, all of which you presumably have locked down, vetted heavily, and watch carefully.

      There's really no special particular 'Java' security issue. Using .NET, Node.js etc etc etc won't particularly make you more secure on the server-side, and for the rest Java is the same as anything else too. Welcome to the world.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    7. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1, Interesting

      Well, you have your opinion, I've written millions of lines of Java code now, and I have my opinion. I don't really hate C#/.NET, there's just no reason to go with them when Java is already there and does the job quite well thank you!

      As for Xamarin, we shall see. Xamarin.iOS is sort of a bastard, your application has to be compiled down to static machine code to meet Apple's requirements. So it isn't really any more '.NET' than GNU's Java compiler is, which can also produce executables (and presumably can target iOS though I don't know of anyone bothering to do that). Of course Java on Android is also 'weird', but at least its still bytecode, even if it isn't java-compliant bytecode.

      Honestly I don't know how much of a difference any of this makes. If I were building a TRUE 'run it anywhere' codebase I'd use C++ and QT, it really does run ANYWHERE, including windows, OS-X, iOS, Android, and basically just about any other OS that has any sort of GUI.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    8. Re:Desktops vs Mobile by lgw · · Score: 3, Interesting

      just no reason to go with them when Java is already there and does the job quite well thank you

      Wow. Just wow. "I know X, so there's no reason the world needs not-X". All Turing-equivalent languages can do the same job, but Java does that job with about 3x the boilerplate of C# (otherwise they're fairly similar, as Java has finally caught up with every other real language in adding list comprehensions). The lack of proper generics/templates in Java is still a daily pain in my ass, however, as is the simple inability to do List<int>

      I understand a preference for the familiar, but when 2 languages are as similar as C# and Java, and one is just better implemented, it seems weird to form an emotional attachment to the other. (Unless this is all really MS-hatred, in which case fine, Win95 killed my pappy, whatever.)

      --
      Socialism: a lie told by totalitarians and believed by fools.
    9. Re:Desktops vs Mobile by west · · Score: 1

      I prefer C# to Java and have written a few hundred KLOC of both, but quite frankly, unless you have a horrible allergy to boilerplate, or are using cutting edge features, the two *are* similar enough not to warrant moving from one's comfort zone.

      99.5% of the code I encounter doesn't use above Java 1.4 or .Net 2.0, so all the nifty language features are pretty much theoretical sizzle on roughly the same steak. And even so, the nifty features often have negative value because they while save the programmer 2-3% of his or her time, the maintainers often end up breaking things because they're not all that familiar with the new hotness in language features.

      I do worry that the number of people who can competently handle closures and functional programming is small enough that we're in danger of not being able maintain the whiz-bang code we've written.

    10. Re:Desktops vs Mobile by bmarkovic · · Score: 1

      Java is .. not very good. I've alternated between Java and C# professionally over the past 8 years or so, and while they used to be quite similar, C# is worlds ahead now (thanks, Oracle!).

      I'm no fan of Java, but I'd really like to hear about where C# is worlds ahead of Java now. We've had "evangelist gone sales rep" from local Microsoft in our Java/OracleDB shop recently. I was somehow in-between .Net open sourcing and first Mono based on .Net Core release, so we were honestly interested, esp. since purchasing VS licences was an option, compared to running everything on WinServer, which simply wasn't.

      What was shown to us was visibly catching up, but still behind modern MVC frameworks, support for version control systems was also quite behind (I can assume TeamServe or what's it called must look like sci-fi to people who never used modern project management and CI software, but it's not) what is currently available in all FLOSS dev ecosystems, including Java (which, granted, is the most conservative one). Both are behind the curve compared to RoR, Python and node.js, and MVC6 is trying hard to be there where modern Node frameworks are (MS is very openly interested in node)... All in all, we weren't impressed very much.

    11. Re:Desktops vs Mobile by shutdown+-p+now · · Score: 1

      For Windows Phone/Windows RT/whatever, Microsoft didn't go for a different language from one of the languages for the desktop. Why they went .NET-only, I don't know.

      WinRT (which covers both phones and everything else) is not .NET-only. You get a choice of .NET, C++ (with some language extensions, think of it as Microsoft's Obj-C) or HTML5/JS. In theory, it's possible to add similar support to other languages, since it's an ABI that is explicitly designed for cross-language consumption.

    12. Re:Desktops vs Mobile by phantomfive · · Score: 1

      99.5% of the code I encounter doesn't use above Java 1.4 or .Net 2.0, so all the nifty language features are pretty much theoretical sizzle on roughly the same steak. And even so, the nifty features often have negative value because they while save the programmer 2-3% of his or her time, the maintainers often end up breaking things because they're not all that familiar with the new hotness in language features.

      That's a good point.

      I do worry that the number of people who can competently handle closures and functional programming is small enough that we're in danger of not being able maintain the whiz-bang code we've written.

      Yeah, closures work great with immutable variables (like in many functional languages), but when you start mixing them with mutable objects, where things have all kinds of side effects, the code can get inscrutable very fast.

      --
      "First they came for the slanderers and i said nothing."
    13. Re:Desktops vs Mobile by Bedouin+X · · Score: 3, Interesting

      It depends on your situation but, right now, C# is the only language that you can use to write programs for Windows Desktop (including Win32/.NET/Modern), Web, Mac Desktop, Android, and iOS.

      And with all of the OWIN stuff you'll be able to run pristine .NET apps on OS X and Linux.

      And you'll be able to host all of this code in one source-controlled Visual Studio project.

      It may not be a reason to switch a shop entirely, but there is definitely a unique value-proposition.

      --
      Dissolve... Resolve... Evolve...
    14. Re:Desktops vs Mobile by Bedouin+X · · Score: 1

      "99.5% of the code I encounter doesn't use above Java 1.4 or .Net 2.0, so all the nifty language features are pretty much theoretical sizzle on roughly the same steak. And even so, the nifty features often have negative value because they while save the programmer 2-3% of his or her time, the maintainers often end up breaking things because they're not all that familiar with the new hotness in language features."

      Obviously I can't tell you what you've seen but, in comparison, I see LINQ (.NET 3.0 I think) everywhere. Async/await is pretty popular too but it is newer and isn't as universally usable so it is not as common as LINQ.

      --
      Dissolve... Resolve... Evolve...
    15. Re:Desktops vs Mobile by msobkow · · Score: 1

      The problem with Java, C#, and every other language is that while the language and it's "core" libraries may be portable, the GUI layer never is. Mono has GTK+ bindings. Windows has Microsoft bindings.

      Java deals with five stacks of GUI code -- AWT, Swing, IBM's code (used by Eclipse), the latest GUI code from Oracle (whose name escapes me at the moment), and the GUI for Android. There had been this dream that there would be one set of bindings that adapted to the platform (Swing), but that got screwed after claims of "performance problems" and Google flat out fucking up their "implementation" of Java for Android.

      --
      I do not fail; I succeed at finding out what does not work.
    16. Re:Desktops vs Mobile by lgw · · Score: 1

      Java is no more or less a security problem than any other application running on your server

      My application running on my server is a fairly small target for black-hats, unless I'm writing bank software or something, exploits specific to my server are low-reward.

      But JVM exploits are freaking golden. Every website everywhere that runs java becomes your target if you have a viable JVM exploit (well, everyone who runs Oracle Java, but that's nearly all of them). I'm sure it's worth millions to find one.

      Yes, C# has the same issue, but IT departments are really very practiced at Windows Update, and MS is really very practiced at the work on their side. Oracle spent at least a year denying they needed to roll out frequent JVM fixes, and the large software corp I was working at at that time was similarly blithely unconcerned about potential risks. Everyone seems to get it now, and maybe the 2 will converge in terms of update tooling, but it's sure been an uphill battle for Oracle. Native languages don't have this problem.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    17. Re:Desktops vs Mobile by lgw · · Score: 1

      LYNQ is not a cutting edge feature in C# - it's been there many years, and I've maintained very lambda-heavy code.that was already years old. Nothing fancy, it's just so much damn simpler to process lists that way than a foreach loop. Java 8 is still cutting edge, I guess, sadly enough, but Java 8 "streams" add enough boilerplate to list processing that they don't seem worth using over foreach loops - and that's pretty sad.

      I often find it takes my three times as many lines of code in Java as in C#, for identical semantics. Lombok helps fix a lot of that, but Java+Lombok is almost a different programming language to read and learn.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    18. Re:Desktops vs Mobile by lgw · · Score: 1

      Xamarin's whole model is making the GUI layer cross platform (I've only just started, so I may be buying the hype, but that's the point of it). QT is the same - you write against their presentation abstraction, and they present something platform-appropriate on each platform. That said, you may want a differently-behaving UI on tablet vs desktop, but even there a sufficiently clever presentation layer could make that work as well.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    19. Re:Desktops vs Mobile by gbjbaanb · · Score: 1

      this , so much. C# may be Microsoft Java++ but at least they get updates on a weekly basis, Oracle... well, even if you do get notified of an update there's no guarantee it'll apply correctly anyway (possibly due to Windows security software preventing it, or firewalls blocking the download) and even if you do download and apply it, there's a small chance someone will forget to uncheck the ask.com toolbar and you're even worse off than you were before the update!

      The biggest issue is that if someone has gained access to your internet-connected server, they have massive amounts of bandwidth to launch all those nasty things they do. You want fewer DDoS extortion attacks, fewer malware botnets? Kill off Java. (note that, last time I looked a load of the security updates for the JRE was to do with webservice code, ie server-side connectivity. All those people saying "oh its only the browser plugin" are sticking their heads in the sand)

      Java sucks, it just needs to die.

    20. Re:Desktops vs Mobile by gbjbaanb · · Score: 1

      There's no reason at all not to use C++, but you do that for the real work your app does, and then you link your C++ library to a small front-end that is written in whatever the native toolkit is for your platform.

      So you can have your C++ logic accessed by iOS, or Android, or Windows phone or desktop. You can even hook it up to a webserver (or embed one) and have it running as a webapp.

      It does cost a little more, creating these different UIs, but the benefit is often worth it. Qt is great, ut native UI is better at being a UI on its intended platform.

    21. Re:Desktops vs Mobile by gbjbaanb · · Score: 1

      True in a way - you may not get the awesomeness of Django when writing webapps, and ASP.NET is pretty awful (they know - that's why keep changing it, which means your skills are always obsolete, ho hum). but you do get VS, which is pretty damn good.

      I don't do much C#, preferring C++ for heavy lifting and 'something else' for specialised bits (eg UI or webapp front end) and it works very well in these cases, but I wouldn't like to code WCF or WPF or ASP.NET daily basis at all.

      Team Foundation Server is pretty bad as well, they did stick git support onto it, but that's really just a git front-end on a centralised repo (which is not a bad idea, just doesn't work so well if you're used to git workflows). The back-end build system that's part of it is configured using 10,000 lines of XAML code, which is just truly awful.

      Its still better than Java though!

    22. Re:Desktops vs Mobile by gbjbaanb · · Score: 1

      actually WinRT is not any language specific. You don't even need the C++/CLR bindings for it.

      What happened is Microsoft took the .NET runtime (which was mostly a wrapper around win32 anyway) and turned it into a different wrapper that is now much more native code directly exposed to .NET apps, but that native code is also directly exposed to all other languages.

      They have the WinRT wrapper for it which looks very much like the old .NET runtime,but it more like COM than a managed API. You can also access it via a c++ style API (that's known as WinRL) that was inspired by Microsoft's ATL APIs.

      So technically .NET no longer exists, its all native runtimes bundled into the Windows core.

    23. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      Well, considering that iOS is only supported through a 'compile to binary' option, that's not quite as clean and easy as you make it out to be. You can also compile Java to binary BTW, and presumably execute it on an iOS device. Eclipse and GIT will give you all the tooling you need to push your code around between various platforms. Its really pretty much a tossup. I think Java has focused more on back-end and Xamarin is making a play for strictly the user-facing app side of things, but they're both broadly capable of doing the same things.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    24. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      AWT and Swing are both obsolete and aimed at the same niche as JavaFX (though in all fairness you will use a number of Swing APIs in pretty much any UI project). AWT and Swing were never intended to be 'run anywhere' UIs, they were just intended to be 'if you have Java you have this API' UIs. The whole reason Oracle sued Google over Android is that they've been breaking that. As for SWT (IBM's Eclipse GUI toolkit) it can in principle work anywhere there are bindings to the underlying UI toolkit (it is a thin wrapper), but it hasn't proven to be super popular aside from corporate applications built on top of the Eclipse core (RCP). I think Google's motivation was to simply have the best and most convenient UI toolkit for the Android platform. Swing was built to work with desktops, it would have had to be totally reworked ANYWAY to adapt to the modern age.

      So, in essence, Java is in no worse a pickle than .NET, who's existing UI toolkits were also poorly adapted to mobile devices, fractured (GTK+ vs WFC/WinForms), etc. Xamarin hopes to unify that, good luck to them. It could be as well done in Java as .NET frankly.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    25. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      I don't understand the fetish with LOC. All that crap that you bemoan is just crap that's generated by the IDE, or often not really needed at all if you know what you're doing. Nor is it true that C# is free of all that jazz either. You still have to define your classes and for any specific design pattern it is going to be pretty much the same classes, subclasses, etc.

      If you are constantly implementing generics then you're doing it wrong IMHO. Implementation of generics should be VERY rare. I wrote and continue to extend and maintain a very complex and large Java code-base. There are maybe at most 6 generic classes in there, and I'd say 3 of them were probably mistakes that you'll only encounter if you dig deep into some very specific code. The others work fine.

      While I don't have any beef against list comprehensions or whatnot they're just loops. There's nothing special about them, or lambda's either really. Its a perfectly valid stylistic choice to avoid the implicit nature of such things and simply write for(String value : props.values()) { ... } or whatever.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    26. Re:Desktops vs Mobile by godefroi · · Score: 1

      Do you really see LINQ, or do you see lambdas and extension methods? LINQ is the query DSL, lambdas are a more syntax-friendly anonymous method, and extension methods make it much more convenient to put this all together.

      I look at a lot of code, and LOTS of it uses at least .NET 3.5 features, including a -lot- of lambdas and a -lot- of extension methods. I RARELY see any LINQ, though.

      --
      Karma: Poor (Mostly affected by lame karma-joke sigs)
    27. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      Personally I think QT beats the pants off any other UI toolkit on any platform, but that's just me. I'd kill to have something that good in Java (IBM reputedly built QT bindings for SWT, but they were never released for whatever reason, assuming they really even existed).

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    28. Re:Desktops vs Mobile by shutdown+-p+now · · Score: 1

      You have some valid points, and some confused points.

      First of all, .NET very much still exists. WinRT did not replace it at all. WinRT is an ABI for all the new Windows platform APIs, and .NET supports interop with that new ABI (much like it supported COM Interop since 1.0 - but better, because WinRT was specifically designed to be seamlessly projected to modern programming languages). But .NET runtime is still the same as it has always been, it runs managed code, and all the standard .NET libraries are still managed, too. The implementations of the standard WinRT libraries, OTOH, are all native (though you can author managed WinRT components if you want to), so a C++ app using WinRT won't have .NET runtime loaded in its process.

      WinRT is actually not "more like COM" - it literally is COM, complete with IUnknown, AddRef/Release/QI, interface marshaling etc. It adds a bunch of other stuff such as a (new) metadata format and a way to obtain it from any random object, a new optimized opaque string type, composition-based inheritance, and a bunch of other things. Mostly it adds enough to be convenient to project to your typical class-based OOP language such as C#. I have worked on a project where we did WinRT projection for Python, and that worked pretty well, too.

      WRL is not so much an API as a bunch of helper wrappers that take care of things such as refcounting or properly implementing a WinRT class for you. It's to WinRT what ATL is to COM. You don't really need it to call WinRT from C++, but it reduces the amount of boilerplate that you have to write.

    29. Re:Desktops vs Mobile by lgw · · Score: 1

      All that crap that you bemoan is just crap that's generated by the IDE

      Yes, exactly, that's the problem. The language is so flawed that most of it is written by automation in the IDE. Why not have a language that's what you type in the IDE instead. C# finally, recently, got the idea right with properties that don't need backing fields: no more getters and setters, except where you're doing something more trivial, a great example of boilerplate reduction. List comprehensions that replace for loops with a single line are another great example.

      Removing the boilerplate lets you read just the business logic when maintaining the code. The more business logic that fits on one screen, the more maintainable the code.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    30. Re:Desktops vs Mobile by micahraleigh · · Score: 1

      7 years of Qt development here.

      Gave up on finding Qt work in the RTP area and started over in C#.

      After 3 years I'm making more money, but I had to take a pay cut for a while.

    31. Re:Desktops vs Mobile by david_thornley · · Score: 1

      The question is how much better one language is than another. I'm proficient with C++, so I'm not really interested in learning a similar language, even if it's somewhat better. It would have to be considerably better (or considerably different) to get me interested, or somebody's going to have to pay me. If GP is proficient with Java, then even if C# is somewhat better it might well make sense to continue with Java.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    32. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      Removing getters and setters matters? pfff, right. If you have logic in your value entities in general its a bad thing, so why do you even look at these files? Mine were all generated automagically 10+ years ago by some Hibernate tool. Once in a while I add a constructor, tweak an .equals() method, etc. A few have get/set methods that include some logic (caching some expensive to calculate value or somesuch) but I could care less. I mean, really, if you want to avoid getters and setters in Java, just declare your fields to be public, it works fine, except of course for the lack of information hiding, which is of course ALSO the problem with C#'s set/get notation. If I make something a calculated value, it changes the consumer's syntax, potentially. Its also a bit unclear to people when you start mixing pure value fields with calculated ones and using the same syntax that they expect to be reserved for one of those.

      I don't think C# is BAD, I just think its much vaunted 'advances' over Java are at best minor tweaks, and Java does some things better than C# too. It would be great if we had the best of both in one, but it isn't happening, so really its 6 of one and half-dozen of the other.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    33. Re:Desktops vs Mobile by Bedouin+X · · Score: 1

      You're right, it is mostly lambdas and extensions. After all these years my head has conflated the concepts as they all came around the same time.

      --
      Dissolve... Resolve... Evolve...
    34. Re:Desktops vs Mobile by Bedouin+X · · Score: 1

      At no point did I say iOS was "clean and easy." I said it's possible with C#. Having said that, I use Xamarin a lot and their AOT compilation technique - while a little unwieldy if you're not on a Mac - works surprisingly well.

      If Xamarin can do what they've done with C#/.NET then obviously it's POSSIBLE to do this in Java, but I haven't seen any actual implementation. This is why I said "right now." Or maybe I've missed the Java project that allows you to share 90% of your code between iOS, Android, and Windows.

      If by "back end" you mean server side infrastructure you are correct, but only because Xamarin doesn't have to pay much attention to the back end. .NET has an entire stack devoted to such matters and Microsoft foots the bill on maintaining it. Xamarin just focuses on the "last mile" if you will.

      --
      Dissolve... Resolve... Evolve...
    35. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      Well, at any rate, I think the notion that .NET is 'in decline' is probably dubious at best. I don't know where its going, but it hardly seems likely that MS is about to abandon the whole technology. I WOULD say however that MS's hold on the 'back room' is pretty tenuous these days. They never really won the argument as to overall value proposition of Windows in the server room over *nix. They have virtually no penetration in the OSS server space, and Mono really went no place there either. Its a pretty hard sell to suggest a .NET/IIS based line-of-business solution to larger IT organizations these days. The more sophisticated shops just stick with Java and the smaller ones tend to either utilize some tool specific to their vertical or built PHP apps or something.

      I think that pretty well explains MS's push with open sourcing a lot of stuff, and getting behind .NET both on every client device and on every server platform. The dream of the total end-to-end dominance of Windows was a LONG time dying, but its finally dead. Its an interesting situation. Java hasn't exactly penetrated the client side space in a consistent way either, so there's plenty of room for each toolset to try to differentiate itself.

      The bigger question might be whether Oracle really cares enough about Java to keep playing this game. They've done a lot, but OTOH they're basically selling database server licenses, with OAS as a sideline that supports the consulting side of the company. Even if they stopped supporting Java it wouldn't really impact their core business that much, at least in the near-term. MS OTOH is in a more ambiguous position. Its not even clear what their core business is going forward. MS Office? SQL Server? MSVS/dev tools? I don't think they know...

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    36. Re: Desktops vs Mobile by BlackHawk-666 · · Score: 1

      Java, for when your code absolutely positively must execute...at some <GARBAGE COLLECTION> future point.

      --
      All those moments will be lost in time, like tears in rain.
    37. Re:Desktops vs Mobile by lgw · · Score: 1

      Mine were all generated automagically 10+ years ago by some Hibernate tool

      Oh, I agree, if you're just doing simple stuff where you just have some web form that "looks like" the backend storage, without complex logic in between, and no scale concerns, there's little enough difference. You're barely writing any business logic in the first place, so any tool will do, and Java has better frameworks.

      In a sense, Java frameworks are a great programming language where they make sense, but they're only tangentially related to Java. Solving complex problems with the raw language, however, is where Java is constantly irritating compared to C#.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    38. Re:Desktops vs Mobile by Giant+Electronic+Bra · · Score: 1

      Eh, no simple correspondence here. I mean, sure there are a couple of forms that correspond pretty closely to some entities in the management UI that we use, but there's a lot of rather complex logic and many of these entities are used in a number of different processes. Its just that Java, and certainly JavaEE, heavily encourages the 'DTO' or 'Bean' model where entities are generally containers and if they have logic its purely related to things like interrelated properties, consistency, etc.

      I don't find your characterization of Java to be that accurate, but what you find 'irritating' may be far different from what bothers me. I want simple regular syntax that doesn't offer a ton of alternatives. That leads to consistent maintainable code. Making things explicit also leads to more thorough and comprehensive testing and documentation. I have LOADS of 500 line class files that implement complex business logic. I need them to be intelligible to anyone that looks at them, not models of clever syntax that manage to get trimmed down to 425 lines, but are less clear. I am happy with conciseness, its good, but its not always the primary goal.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    39. Re:Desktops vs Mobile by DuckDodgers · · Score: 1

      In the browser, Chrome has a builtin PDF viewer and builtin Flash player, and it auto-updates silently for you. Oracle doesn't do that with the Java plugin. The security problems were so severe that if I recall correctly. Firefox and Chrome both added code to disable the Java plugin automatically if it was out of date. But the end user still had to manually update Java every time.

      If Oracle was really serious about Java's image with the general public and its ease of use for average people, they would have bought or built a silent auto update feature for the Java Runtime Environment.

    40. Re: Desktops vs Mobile by DuckDodgers · · Score: 1

      Neither you nor the parent post author are correct. In benchmarks for server side code, a long-running, JIT compiled Java application will typically blow Perl, Python, PHP, Ruby, and similar languages away for performance in all ways, beat C# and F# by a smaller but still significant margin, but still lag well-written C or C++ by 1.5-5x for execution speed and 5-100x for memory usage.

      Now as it turns out, much of Facebook is written in PHP, much of Reddit and Youtube is written in Python, and Wordpress powers millions of websites with PHP. So Java is good enough for a massive number of server use cases. But the Java Virtual Machine's HotSpot and all of its optimizations still haven't caught up with GCC and LLVM for speed yet, there's a lot of ground left to cover.

    41. Re:Desktops vs Mobile by DuckDodgers · · Score: 1

      LOC by itself isn't useful - people can and do write incomprehensible short Perl applications that tens of thousands of competent Perl developers couldn't read or modify.

      But writing and especially reading code that exists for the sake of ceremony does slow you down. Say you have a simple Plain Old Java Object for a person with ID, last name, first name, date of birth, occupation, and set of skills. In Java that's a package declaration plus two to three imports (java.util.* or java.util.Date and java.util.Set and then your Skills class) plus class declaration plus six instance variables, six getters, and six setters. With common Java code format conventions that's 48 lines of code. The Scala language has its own warts, but in Scala that would be a package declaration, one line import for your Skills class, one line import that includes Date and Set without using a wildcard import, and a one line class declaration (well, it will probably spill onto a second line). You've gone from 48 lines to 5, and it's every bit as easy to understand.

      Now that example is a trivial one, but you have the same getter syntax, imports, and method signatures and checked exceptions and so forth throughout the language. I haven't used C# in a serious application, so I can't compare there from personal experience. But Scala (and the similar language Kotlin) let you write code that looks like Java and works with Java but cuts 50-90% of the boilerplate nonsense out, and you're left with something that's just as clear as Java and much faster to write and read.

    42. Re:Desktops vs Mobile by zenkey.zencode · · Score: 1

      Sorry, There is and we do. http://kivy.org/ It may not use native widgets, but that's a good choice to my mind. It's entirely consistent across platforms and in many ways, that's a lot easier to handle that catering of OS specific behaviour.

  4. Dice numbers different than other boards? by Anonymous Coward · · Score: 1

    Maybe they should spend less time trying to monetize slashdot and more time getting the cruft out of their job board.

  5. hogwash by Anonymous Coward · · Score: 3, Insightful

    hogwash

  6. Slashdot layout by iONiUM · · Score: 5, Informative

    My Slashdot layout just changed, there's no more 'read more' button. Just 'share'. You have to find the small annotation in the top right for the comments? What the hell.

    1. Re:Slashdot layout by Lunix+Nutcase · · Score: 5, Informative

      Yeah they're dicking with shit again. Luckily that button is easily blocked by ABP. They've also broken the layout a few times in the last couple of minutes when I've refreshed.

    2. Re:Slashdot layout by afidel · · Score: 1

      They even changed it for classic.slashdot.org, wrtf?

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    3. Re:Slashdot layout by XxtraLarGe · · Score: 1

      Or you could just click the article name. Still, kinda messed up. but whatever. I figure the more people who ditch this site, the better chance I have for first posts.

      --
      Taking guns away from the 99% gives the 1% 100% of the power.
    4. Re:Slashdot layout by alvinrod · · Score: 2

      Does anyone ever click those share buttons anyways, other than perhaps accidentally?

      I don't use much social media so I have no idea if they show up frequently, if at all. The only time I can ever recall seeing one was in an image capture of someone who had (perhaps accidentally) shared a porn video, which for whatever damned reason had Facebook integration.

      One would think that people come here to get away from the Facebook crowd and that the Facebook crowd has little interest in what's posted here, so why they bother incorporating such a feature is beyond me. Never mind that the layout seems fucked, but it could just be my browser.

    5. Re:Slashdot layout by drinkypoo · · Score: 1

      Does anyone ever click those share buttons anyways, other than perhaps accidentally?

      I click the one on Youtube that sends stuff to G+ sometimes, I figure that actually makes sense. But yeah, it's conceivable that I would use that button myself... again, to send stuff to G+. It's more often I see stuff there that I post here (my last accepted submission, for example) but I do get some good results resharing slashdot stories to G+ on occasion.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Slashdot layout by Travis+Mansbridge · · Score: 1

      But how, oh how will I ever direct people to this article without the use of a button??

    7. Re:Slashdot layout by antdude · · Score: 1

      I got a 503 error earlier and not logged in. :/

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    8. Re:Slashdot layout by OhPlz · · Score: 1

      No doubt the work of another fine "UX Engineer".

    9. Re:Slashdot layout by vivaoporto · · Score: 5, Insightful

      Fellow slashdot webdevs, please don't test in production. Below is how it looks like on Safari for Mac.

      http://s7.postimg.org/5rhru2q6z/image.png
      http://s7.postimg.org/qacnz544b/image.png

      Not to spoil but the main problems are:

      1. People that remained on classic Slashdot theme expects just that: the classic theme. Please don't change it. Considering that the main elements of the articles didn't change much (title, summary, number of comments, submitter, link, etc), the same going for the comments (title, score, commenter, date, etc) it shouldn't be hard to make a separate theme for this (admittedly stubborn) users and leave it alone.

      2. The new "cartoon balloon" showing the number of comments is overlapping when the article is collapsed (see first screenshot above)

      3. Seems like the old way to show the number of comments was forgotten below the cartoon balloon (see first screenshot above)

      4. In the sidebar, seems like "This day on Slashdot" was completely forgotten in the new style (see second screenshot above)

      5. It's really acceptable after being bought by Dice to show "Latest Tech Jobs" prominently in the sidebar, we understand that's one of the perks of being the owner. But at least put back the Poll above the fold and push Slashdot Deals and Featured Videos below the fold. 6. It may not have been the intention but it feels really underhanded to replace the (probable) most clicked link in the homepage (Read More) and replace it with the "Share" button. That will more likely to be the main complain, will cost Slashdot a lot of old timers and probably will be as loudly rejected as Beta.

      Please put Read More back where it was, I'm sure you guys already realised we are not much a sharing bunch, privacy concerns and all that.

    10. Re:Slashdot layout by dmomo · · Score: 1

      Yeah, It's annoying. The new corporate overlords are trying to force us to be "social". They do realize that if we DID want to share, we're savvy enough to share the original link, not a link to slashdot, right? No.. let's not give them that credit.

    11. Re:Slashdot layout by seven+of+five · · Score: 1

      you can also click on the title.

    12. Re:Slashdot layout by vivaoporto · · Score: 1

      Fellow slashdot webdevs, please don't test in production. Below is how it looks like on Safari for Mac.

      http://s7.postimg.org/5rhru2q6z/image.png
      http://s7.postimg.org/qacnz544b/image.png

      Not to spoil but the main problems are:

      1. People that remained on classic Slashdot theme expects just that: the classic theme. Please don't change it. Considering that the main elements of the articles didn't change much (title, summary, number of comments, submitter, link, etc), the same going for the comments (title, score, commenter, date, etc) it shouldn't be hard to make a separate theme for this (admittedly stubborn) users and leave it alone.

      2. The new "cartoon balloon" showing the number of comments is overlapping when the article is collapsed (see first screenshot above)

      3. Seems like the old way to show the number of comments was forgotten below the cartoon balloon (see first screenshot above)

      4. In the sidebar, seems like "This day on Slashdot" was completely forgotten in the new style (see second screenshot above)

      5. It's really acceptable after being bought by Dice to show "Latest Tech Jobs" prominently in the sidebar, we understand that's one of the perks of being the owner. But at least put back the Poll above the fold and push Slashdot Deals and Featured Videos below the fold. 6. It may not have been the intention but it feels really underhanded to replace the (probable) most clicked link in the homepage (Read More) and replace it with the "Share" button. That will more likely to be the main complain, will cost Slashdot a lot of old timers and probably will be as loudly rejected as Beta.

      And most important of all: please to eat the comments. I tried to post this exact comment, it went through and suddenly it disappeared (see below). As I had the submitted comments in another window I managed to take the screenshots and to save the text I wrote so carefully

      http://s1.postimg.org/5e5aqjjnj/image.png

      http://s1.postimg.org/3l2e27ygv/image.png

    13. Re:Slashdot layout by turp182 · · Score: 1

      I'm just UXing here, but point #6 was terribly confusing as it seemed to be part of point #5.

      Otherwise spot on. Slashdot should have the community comment/vote on changes and then have a true "beta" (not the shit we had before of course) that people could comment on.

      Actually, they should just leave it all alone. There's enough change in the real world, can I have a consistent, expected Slashdot experience?

      --
      BlameBillCosby.com
    14. Re:Slashdot layout by mars-nl · · Score: 2

      I'm old-fashioned. If I want to share, I copy/paste the URL in the social network of choice.

    15. Re:Slashdot layout by vyvepe · · Score: 1
      The rule is:

      ##div[class="popularity menu-trigger"]

  7. Yes. by 140Mandak262Jamuna · · Score: 1

    Next question, please.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  8. Know what's on the decline? by Anonymous Coward · · Score: 4, Insightful

    Fucking Slashdot is on the decline.

    WTF do you think we want ot share Shashdot to Facebook and other shit for?

    Fuck you guys suck at maintaining a fucking website. Stop changing everything. Stop trying to be all fucking social media. Just fucking stop.

    Fuck you dice, and fuck you Nerval's Lobster -- your apparent function is to write fucking shill articles which point to fucking dice.

  9. Yeah... this is just wrong by Anonymous Coward · · Score: 1

    Many more things are becoming .NET dependent. Everything is being PowerShell-intergrated... and PowerShell is a .NET Shell, basically. Exchange was rewritten in .NET with Exchange 2013. Basically the entire Windows Server ecosystem is going that way.

    1. Re:Yeah... this is just wrong by xombo · · Score: 1

      I think your right in that it's also safe to say that the entire Windows Server ecosystem is going the way of .NET's decline.

  10. He's leaving C# for... Java? by Anonymous Coward · · Score: 1

    Oracle is pretty much actively trying to destroy Java.

  11. Too soon to tell? by Squatting_Dog · · Score: 5, Insightful

    With the .NET platform now being available for cross platform development I can't see how there could be a decline in C#. It's only been about 6 months since MS offered .NET for other platforms I don't think that's enough time for any valid conclusions to be made. Wait another 6 months to a year and then take another look. I think we will see an increase in C#/.NET reflected in those numbers.

     

    1. Re:Too soon to tell? by Gr8Apes · · Score: 1, Flamebait

      It was already in decline. Another 6 months with the "opened" up .NET for other platforms won't help a bit. You know why? Because Mono was already out there. It's not an expanded market, only attempting to eat the other fish in the "new" pond.

      --
      The cesspool just got a check and balance.
    2. Re:Too soon to tell? by phantomfive · · Score: 1

      I see cross-platform development as a non-issue to the .NET world. The people who were really excited about it were already invested in the Microsoft ecosystem, and the ones who wanted to do .NET on Linux were already doing it with Mono (which was actually fine).

      I think it's great that Microsoft is open-sourcing parts, but it isn't going to make a huge impact.

      --
      "First they came for the slanderers and i said nothing."
    3. Re:Too soon to tell? by Ravaldy · · Score: 1

      Yeah but Linux developers will use C++. It wouldn't be very friendly to the Linux Dev community if the framework wasn't C++ compatible especially since it's the most used language for app dev on Linux.

    4. Re:Too soon to tell? by Dadoo · · Score: 1, Flamebait

      With the .NET platform now being available for cross platform development I can't see how there could be a decline in C#.

      You'd have to be an idiot to use .NET for cross-platform development. In five or so years, Microsoft will discontinue cross-platform support, giving some BS excuse, like "no one was using it." What will the cross-platform developers do then, rewrite their code in a language that's really cross-platform? Doubt it.

      As I've said here, before, this is just more Embrace, Extend, Extinguish.

      --
      Sit, Ubuntu, sit. Good dog.
    5. Re:Too soon to tell? by phantomfive · · Score: 1

      We'll see how it goes, but after developing in My Eclispe/Java, XCode/Objective-C, and Visual Studio/C#, I can say without a doubt that VS/C# was the most productive IDE/language I've dealt with.

      I seriously have to question people who say this kind of thing. How are you measuring this? In amount of code written? Are you talking about prototypes, or are you talking about maintenance?

      --
      "First they came for the slanderers and i said nothing."
    6. Re:Too soon to tell? by Nethemas+the+Great · · Score: 1

      Let's assume the data is valid. What can we deduce? .NET/C# is the language of the desktop/server. Did they bother to normalize the data accordingly? I doubt it. What I see is considerable buzz within the web/mobile space and the jobs resultant from that. For the most part I don't think they represent replacement jobs, they represent new demand.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    7. Re:Too soon to tell? by RingDev · · Score: 1

      In the amount of time not spent beating my head against the wall.

      I'm in management these days, so I only have to deal with it as it impacts my schedules and retention. Upgrading My Eclipse Blue was incredibly painful. I get complaints about memory management, crashes, and EARs missing files. The integrated SVN system makes me weep when I have to try to explain to devs what /move and /switch SVN commands are. Or the inane restrictions our support team puts on our use of the product because they're trying to steer us around issues that will corrupt workspaces and configurations to which their only solution is uninstall/reinstall.

      Same crap with XCode. We use to have a daily pool to see who could pull off the longest up time.

      Now, if you want to get into code, things get a bit mirkier. Java is catching back up, but the .Net framework's implementation of generics and more importantly LINQ is still leaps and bounds over Java. And while Spring and other libraries have improved the ease and speed of data access over Hibernate, .Net's Entity Framework is super easy to work with (so long as there are good drivers for the DB you're hitting).

      Java's documentation is superior, no questions there. Microsoft's MSDN isn't bad, but if I run into something odd, it's almost always augmented by Stack Overflow.

      And historically speaking, I've had less issues upgrading the .Net framework on servers/desktops than changing Java version. Especially since .Net 3.0 (1->1.1->2.0 was rockier than I would have liked).

      Anyway, they are all 3 valid development platforms. I have my preference, others have their own.

      -Rick

      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    8. Re:Too soon to tell? by Gr8Apes · · Score: 1

      The .NET 3.5->4.0->4.5 upgrades were absolutely horrible if you were doing anything with escalating permissions or anything else that tied to system resources. If you had 100% self-contained code that only used basic resources exposed by core APIs, I guess you'd be safe. (That's also true of just about any other language/ecosystem)

      Java generics mostly are syntactic sugar. They allow for less boilerplate code, but if you don't understand what's happening under the covers, it makes no difference. Spring is the devils path to hell. Try debugging a Spring initiate's code sometime. The exorcist will have nothing on your head spinning. ORMs are pretty much all sucky bad. RDBMs just don't mesh with ORMs, as they're orthogonal. Any idea you have that they're not is mistaken or because you're at the LCD point.

      Regarding uptime, I code with Java, Xcode, and Android Studio currently, and my uptime is measure in months. I also use git. (who would use svn? It's irrevocably broken by design unless it's 1 user per source tree) What you're describing is a nightmare trifecta of bad tools, bad process, and bad developers. Any 1 of the three will be an unpleasant experience, but all three? You have my sympathies.

      --
      The cesspool just got a check and balance.
    9. Re:Too soon to tell? by bmarkovic · · Score: 1

      I can see few more plausible reasons for the decline:

      1) Servers are increasingly Linux, even in enterprise. Microsoft response by open-sourcing .Net might be too little, loo late.
      2) Client apps are increasingly mobile, Microsoft's market-share here is dismal.

      1) and 2) have given boost to Java, boost to Java is instantly C# decline since both languages rely on same approach to project management (the "nobody ever got fired for...." style) to thrive.

      3) Visual Studio my be the bees knees, but .Net is far, far behind the curve when it comes to web application development, which brings us to:
      4) Start-up economy is on fire, and there it's a run for least verbose, fastest to market type of development (release early, release often, pivot often, get tons of cash, then rewrite backend in something that can actually scale --- see: Twitter). Success in software-development related economy is not (and frankly, never was) about most solid technology choices from the get go, and more and more devterpreneurs are seeing this.

      Re 3) and 4) I can't think of any major web app (apart from StackExchange, granted) that is based on a Microsoft stack.

    10. Re:Too soon to tell? by shutdown+-p+now · · Score: 1

      Given that it's all open source, fork it?

    11. Re:Too soon to tell? by Gr8Apes · · Score: 1

      "The .NET 3.5->4.0->4.5 upgrades were absolutely horrible if you were doing anything with escalating permissions or anything else that tied to system resources. "

      I'm struggling to understand what you mean by this, it doesn't really make any kind of sense. Are we talking about upgrading code, or upgrading the CLR?

      You tell me... ;) .NET 3.5/4.0/4.5 directory implies the CLR.

      3.5 code is forwards compatible, the breaking changes are minimal and insanely rare edge cases).

      untrue.

      ...3.5 runs on the 2.0 runtime, and 4.0 had it's own new runtime. ...4.5 was an in place upgrade for 4.0, it changed some things under the hood but the breaking changes were again few and again very edge cases that 99% of .NET devs will never have encountered...

      Thanks for proving my points. That's exactly right, and exactly what was a horrible nightmare to deal with. Those few, edge case incompatibilities were what hit me each time. And, the 3.5->4.0 wasn't as minor as you make out. Even the 4.0->4.5 isn't 100% smooth, nor would it be, given the shenanigans MS did there.

      --
      The cesspool just got a check and balance.
  12. More stupid crap... by sudden.zero · · Score: 3, Insightful

    ...that no one cares about posted by some jackhole dice moderator. I wish some rich Slashdot reader would buy dice to acquire Slashdot, and then fire all Dice employees, and shut dice down. FU DICE! Stop ruining Slashdot!

  13. Is it actually on the decline? by vux984 · · Score: 2

    This seems more like an acknowledgement that ios and android are where the majority of new development jobs are right now than anything else.

    Does that mean C# or .NET is on "the decline"? I suppose, strictly speaking yes. But it doesn't remotely mean its on the way to becoming like COBOL where its only used by legacy products. Windows destkop and servers are still being deployed in the millions, and .NET is an excellent platform for new development if you are targeting that market.

    1. Re:Is it actually on the decline? by Gr8Apes · · Score: 1, Troll

      People still develop for windows? Why? (yeah, I better duck, my karma is taking a beating today:)

      Windows destkop and servers are still being deployed in the millions,

      Windows servers in the millions, there's a reason for that. Last time I had real numbers to compare 2 large scale equivalent systems: UNIX: <100 servers, Windows: about 2400 servers. Same basic workload, different codebases and languages (Java / COBOL for *nix, C/C++ MS SQL for Windows). Oh, and the windows system was much less capable.

      Seriously though, Windows servers are in decline, and have been for a while. They're a screaming security risk, perform poorly - *nix of any reasonably modern flavor smokes windows on the same hardware, unless, of course, you're attempting to run a windows program under an emulator or API framework under *nix.

      --
      The cesspool just got a check and balance.
    2. Re:Is it actually on the decline? by ilguido · · Score: 3, Interesting

      Justin Angel's post is quite insightful on the matter. He is simply reckoning that .net is probably past its prime: there are much less jobs for .net than for Java/Swift/HTML5+JS, open source developers are leaving .net, the ecosystem as whole is shrinking and fragmenting. He lists a number of reasons for this decline, but he doesn't say in a year there will be no more .net, just that it is going down.

    3. Re:Is it actually on the decline? by Dutch+Gun · · Score: 3, Insightful

      It's the same analysis that lead people to conclude that because mobile gaming was on the rise, console gaming was therefore going to disappear. And the same logic let pundits to conclude that we're now in a "post-PC" world. The ascendance of one market does cause a shift in proportions of other parts of the market, but doesn't necessarily lead to a complete collapse. Even if .NET is in overall decline, I think that speaks to the larger decline, proportionally speaking, of the desktop PC market. However, Windows still *completely* dominates that market, so .NET/C# will likely remain strong there.

      So, I'd say if we're talking about a "decline", that makes sense to me. If we're talking about a "collapse", that's absurd. Even if no one except Windows developers were using it, it would still not go away completely, because that's why the .NET platform and C# language were invented in the first place... to simplify Windows development.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    4. Re:Is it actually on the decline? by ADRA · · Score: 1

      Separating desktops and servers (which in this case is quite relevant):

      Servers can be Windows / Linux / etc. and it doesn't really matter. if I wanted windows, I'd spoool up a windows VM. If I wanted a Linux server, i'd spool up a Linux server instance in a VM. I ONLY WANT Windows/Linux because of the applications that run on them. Server dev environment choice in that respect don't really matter unless you're deeply entrenched in a given vendor's server API stack. I've personally never seen companies do anything OS-specific services outside of a few DCOM based components like 15 years ago. If you have customers that want your server offering, they'll spool up whatever OS/hardware necessary to run it.

      For desktops, this certainly matters a lot, since most consumers don't have multiple desktop OS's unless you're dancing with tablets/phone OS's as well. All that said, I see little interest for 'windows apps' or 'Linux Apps', 'Mac Apps', etc.. The web has really gutted the native platform applications market. Never eliminated obviously, but significantly maimed in the consumer space.

      Lastly, desktop applications for Enterprise are generally still thriving, and .Net/Java/C++/etc.. zealots in companies still fight tooth and nail for the next project.

      --
      Bye!
    5. Re:Is it actually on the decline? by vux984 · · Score: 1

      unless, of course, you're attempting to run a windows program

      I'm not arguing with you that *nix is a better server overall. But windows is a better server if your working with windows apps, serving windows apps, or managing windows desktops.

      With 90%+ of the desktop market; most people are running windows applications. They are using remote desktop into servers running windows applications. They are using local windows applications that talk to server windows applications. etc.And the whole thing is managed by another windows server running active directory, and their backups and antivirus and wsus ... all windows servers ... because why would you install *nix box in a role like that?

      Windows and Windows servers is not a niche market. And its not going to be a niche market any time soon. Even if its in "decline" relative to the ascension of mobile apps...

    6. Re:Is it actually on the decline? by vux984 · · Score: 1

      I don't disagree with you. But one role of Windows servers you sort of glossed over is simply: "managing windows desktops" (active directory, group policy, etc, etc). If you are running more than a handful of windows desktops you've probably got a windows server.

      And if you've already got a bunch of windows desktops plus a windows server, it doesn't really make sense to spin up one *nix box in that environment unless you really need something that only *nix can do. It generally makes more sense to either use the existing windows server, or drop in another one.

  14. Betteridge's law of headlines by cdrudge · · Score: 4, Insightful

    Any headline that ends in a question mark can be answered by the word no.

    EOM

    1. Re:Betteridge's law of headlines by Gr8Apes · · Score: 1

      Is cdrudge alive?

      --
      The cesspool just got a check and balance.
    2. Re:Betteridge's law of headlines by cdrudge · · Score: 1

      No

  15. Only "Declining" in scope by Anonymous Coward · · Score: 1

    I work in the enterprise app space.

    With the emergence of Single Page Application frameworks (I use AngularJS) a lot more of the logic of an app can be pushed to the client. The C# part of the application has morphed from being ASP.Net WebForms or (gag) MVC / Razor code into just being simple REST'ish Web API calls. It works really well.

    When working with this structure you wouldn't search for a "C#" person, you would search for Web API / javascript / SQL person.

    The ecosystem is alive and well. This guy is eating his sour grapes.

  16. YOU are the scratch monkey! by Thud457 · · Score: 5, Funny

    FUCK IT! I'll do it live and test it in production!

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    1. Re:YOU are the scratch monkey! by Penguinisto · · Score: 5, Funny

      They're using a new variation of Agile, called "Methagilephetamine".

      Still has a few kinks in it, though.

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    2. Re:YOU are the scratch monkey! by Lodlaiden · · Score: 1

      Oh for mod points today.

      --
      Suborbital [spaceflight] is the special olympics of spaceflight. - Rei
    3. Re:YOU are the scratch monkey! by Lunix+Nutcase · · Score: 1

      Yeah apparently. Must be one of the newest posts doesn't allow posting and says it's an "archived discussion" and the other doesn't show any of the comments its supposed to have. *golf clap* Good job, Dice.

    4. Re:YOU are the scratch monkey! by JMJimmy · · Score: 4, Insightful

      FUCK IT! I'll do it live and test it in production!

      I want my fucking comment link back. Share? Who wants to share Dice shill stories.

  17. not many tears if it is. by nimbius · · Score: 2, Insightful

    .net was microsofts misguided attempt to staunch bleeding from open source competitors and recover from the increasingly drunken shit show that was ActiveX. The idea being that while most of the technology existed under Apache 2.0 license, the core redistributed package was proprietary. In typical day-late-dollar-short microsoft fashion the whole thing was hinged on a JIT compiler (because Java in 2002 was a godsend of speed and stability) and came with C++ support in 2005 (more than 20 years after the language was written...nice) via visual studio. Redmond still had a problem though, and that was without a proprietary language, the framework was pointless because C and company were all well known and reasonably portable languages that didnt net any extra cash to Microsoft. So borne of a committee C# came to be, and for many moons C# was wedged into most code shops the same way any other microsoft technology gets there: License bundles. You see programmers were writing plenty of windows software on windows machines, and compiling in windows, but discounts to licenses for the desktop OS the greybeards use was hinged upon accepting free licenses for .NET and the new C# visual studio compiler. Management, ever needful to maximize value, prevented their bosses from yelling at them and in turn started most projects down the intractable cobblestone back alley we know today as .net.

    What made matters worse for everyone was now microsoft had an underhanded way to slash the tires of its competitors. If your software beat the pants off Microsoft they might buy it, but if you didnt sell and they knew you wrote C# they used the proprietary compiler against you and simply reimplemented your software with undocumented methods and subroutines that ran faster than yours. Theyd sit out your litigation until you folded, buy up your shop for cheap, and with a few modifications rebrand your application as a microsoft component.

    --
    Good people go to bed earlier.
    1. Re:not many tears if it is. by phantomfive · · Score: 1

      if you didnt sell and they knew you wrote C# they used the proprietary compiler against you and simply reimplemented your software with undocumented methods and subroutines that ran faster than yours. Theyd sit out your litigation until you folded, buy up your shop for cheap, and with a few modifications rebrand your application as a microsoft component.

      Has that ever happened?

      --
      "First they came for the slanderers and i said nothing."
    2. Re:not many tears if it is. by rcase5 · · Score: 1

      Another reason to steer well clear of anything Microsoft, especially when it comes to software development. It never made sense to me why people would willingly use Microsoft products to develop their own software projects when Microsoft could easily become your biggest competitor in a heartbeat. Back when I was working in Windows desktop software development, it would amaze me the convolutions and contortions we would go through to not reveal what we were doing if we needed to contact Microsoft support regarding one of their products we were using to develop or test our software; so they wouldn't steal our idea and kill us before we got off the ground. Going the Microsoft route is even more puzzling when developing for the web when you consider non-Microsoft platforms offer so many more and, arguably, better tools that are less prone to corporate sabotage.

      When will people learn?

    3. Re:not many tears if it is. by avandesande · · Score: 1

      Short and sweet, .NET was a response to Java.

      --
      love is just extroverted narcissism
  18. Re:Look at stackoverflow.com/tags by BenJeremy · · Score: 1

    So you are saying developers code in C# with fewer issues than those who program in Java and Javascript?

  19. Slashdot on the decline? by Mark19960 · · Score: 5, Insightful

    This social media S--T they keep pushing.
    These DICE links and plugs that we keep getting from Nerval's Lobster?

    C# isn't declining in popularity from where I sit - Slashdot is.
    Why do I come here?

    1. Re:Slashdot on the decline? by Megaweapon · · Score: 1

      C# isn't declining in popularity from where I sit - Slashdot is.

      You don't need to be a Kreskin.

      --
      I'm sure "SlashdotMedia" will improve on all the wonders that Dice Holdings blessed us all with
    2. Re:Slashdot on the decline? by irrational_design · · Score: 3, Funny

      We need an Ask Slashdot: "Now that Slashdot sucks, what site have you moved to?"

    3. Re:Slashdot on the decline? by Bite+The+Pillow · · Score: 1

      For the same reason I do - to yell at stupid people? Because there's not really much else to offer.

  20. What about programming in general? by CaroKann · · Score: 1

    I sometimes wonder if programming in general is in decline. Of course, there are hot spot areas, such as phone apps at the moment. Based on my own anecdotal observations, there seems to be more demand for System Architects than Programmers. It's a "Software as a service" world now, and companies want people who can choose the correct puzzle pieces to put together into a practical system. With the advent of "cloud" services, where services are not just shared within an organization, but across the entire world, I can see how actual customized coding may become less necessary for individual companies. Companies want systems that can be built quickly, without all of the bugs and issues that can come from completely customized systems. They still want some customization, but perhaps not to the extent of a system being built from the ground-up.

    1. Re:What about programming in general? by jbolden · · Score: 1

      Just as you need glue code to tie together libraries to make an application you need glue code to tie together SaaS services to make a unified service. The libraries now are just SaaS APIs.

    2. Re:What about programming in general? by LordWabbit2 · · Score: 1

      Sounds to me like you work for SAP?
      We are not programmers, we are System Architects and expect to be paid accordingly.
      Meanwhile you are writing code like every other programmer.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
  21. Maybe, but that doesn't imply the future is bleak by i_ate_god · · Score: 2

    Microsoft is pushing .net in directions no one thought it would five years ago in terms of being an open development platform. I think this will help boost c# popularity if anything. C# is a nice language to work with, and Visual Studio is a nice IDE to work with for the most part (it's virtual filesystem has got to go, and needs better RCS integration a la Eclipse).

    --
    I'm god, but it's a bit of a drag really...
  22. Unbiased source by TheSpinningBrain · · Score: 1

    I'd totally trust to get my information about the health of the Microsoft .NET ecosystem from an Apple fanboy.

  23. Re:Silverlight by Darinbob · · Score: 1

    You can tell he was a manager, because an actual developer would never think about "customer reach" when choosing a language.

  24. Of course not by phantomfive · · Score: 1
    --
    "First they came for the slanderers and i said nothing."
  25. Terrible Analysis by Zalbik · · Score: 4, Insightful

    Stick with program managing, Justin. Actually, given you were responsible for Silverlight, find some other career entirely.

    If you check Perl, Java, PHP or C++ on Indeed.com, you will see exactly the same trends.

    If you perform his same terrible analysis of the TIOBE index, PHP, C++, VB.NET, Objective-C are all going to collapse. Apparently Java has been "heading for collapse" since 2004.

    People who can't do statistics shouldn't report on them.

    The problem does not appear to be that C# is becoming less popular (than other languages), it's appears that custom application development as a whole is becoming less popular than it was a few years ago.

    This may be due to the economy, outsourcing, mobile platforms or whatever. You can't suddenly pull reasons out of your ass like this being due to "Microsoft’s ever revolving door of new technologies", despite how pissed off you are at them for shit-canning your pet project.

    When doing stats on whether something is less popular, it's helpful to ask "less popular than what". Sure, it may be less popular than it used to be, but so are the competing languages. This does not indicate that the C# ecosystem is going to collapse.

    1. Re: Terrible Analysis by Anonymous Coward · · Score: 1

      Hey, hey, take your insightful and rational comments elsewhere you hippie, we don't want that shit in here!

    2. Re:Terrible Analysis by trptrp · · Score: 1

      +1

      --
      The rounded corners on the front page are missing. Seems like change for the sake of change again. I don't even mind seeing this site worsening anymore. I look at it in a sarcastic and amused way. They still haven't figured out the obvious way to monetize, that is, we'd be all happy to pay a subscription fee to access the comments section.

    3. Re:Terrible Analysis by r0kk3rz · · Score: 1

      Seems to be a case of Lies, Damned Lies, and Statistics

      They are using the percentage of job postings as their main example of this decline, without stating whether the total number of jobs has increased/decreased/remained static. The actual number of C# jobs could be increasing if the entire field is also increasing, so the only conclusion they can come to is that the C# is losing market share.

  26. Nonsense by CustomSolvers2 · · Score: 1

    Windows is still (by very far) the most used OS on desktop computers. At the corporate level this superiority becomes almost insulting and Windows is and will continue being the number 1. Thus, just by focusing on desktop corporate clients, there will be lots of very interested buyers of Windows applications during the next quite a few years (some of them still struggling with Windows XP). To not mention that the web-based languages (= ASP.NET because Silverlight well) are so different to any alternative and so similar to the desktop-based ones that quite a few companies are moving to ASP.NET; actually, there will be many more doing that if this format wouldn’t have a so restricted applicability in web-servers (but, as explained below, they seem to be working on that). In any case, I want to highlight that I personally rely much more on PHP.

    Regarding the web and the mobile platforms, Windows & Microsoft seem to be losing the battle. On the other hand, they seem to be doing quite a few changes on this front lately (like increasing cross-compatibility or relying much more on open source); mainly because they cannot rely on their traditional monopoly-oriented attitude in any of these fronts. In fact, I do expect the .NET Framework to become increasingly more compatible with no-Windows systems within the short term.

    And on top of all what is written above, the .NET languages (C#, but even VB) have become so popular that even in the extremely unlikely scenario (better: impossible) of the claimed drastic reduction in their utilisation, some alternatives would surely appear. Additionally, a language like C# is extremely similar to quite a few other languages (like Java or even PHP) and thus learning this language will never be a bad decision.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  27. Indeed by __aaclcg7560 · · Score: 1

    You're more likely to find a job using Indeed, especially if you poll the website frequently and jump on a job post when it becomes available. If you respond within 15 minutes, you're likely to get an interview. I've gotten many interviews through Indeed. DICE, meh.

  28. Nonsense (2) by CustomSolvers2 · · Score: 1

    My previous post is not shown but I cannot re-post it because I get an error message saying "This exact comment has already been posted. Try to be more original..."?!

    I will try to paste it below these lines:

    Windows is still (by very far) the most used OS on desktop computers. At the corporate level this superiority becomes almost insulting and Windows is and will continue being the number 1. Thus, just by focusing on desktop corporate clients, there will be lots of very interested buyers of Windows applications during the next quite a few years (some of them still struggling with Windows XP). To not mention that the web-based languages (= ASP.NET because Silverlight well) are so different to any alternative and so similar to the desktop-based ones that quite a few companies are moving to ASP.NET; actually, there will be many more doing that if this format wouldn’t have a so restricted applicability in web-servers (but, as explained below, they seem to be working on that). In any case, I want to highlight that I personally rely much more on PHP.

    Regarding the web and the mobile platforms, Windows & Microsoft seem to be losing the battle. On the other hand, they seem to be doing quite a few changes on this front lately (like increasing cross-compatibility or relying much more on open source); mainly because they cannot rely on their traditional monopoly-oriented attitude in any of these fronts. In fact, I do expect the .NET Framework to become increasingly more compatible with no-Windows systems within the short term.

    And on top of all what is written above, the .NET languages (C#, but even VB) have become so popular that even in the extremely unlikely scenario (better: impossible) of the claimed drastic reduction in their utilisation, some alternatives would surely appear. Additionally, a language like C# is extremely similar to quite a few other languages (like Java or even PHP) and thus learning this language will never be a bad decision.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  29. Clickbait by OhPlz · · Score: 1

    Let me guess, fewer people are using /. so the bright idea is to post flaimbait stories to try and drive people back to the site?

    Fail.

  30. Help us with market research, please! by dave562 · · Score: 1

    According to Dice's data, the popularity of C# has risen over the past several years; it ranks No. 26 on Dice's ranking of most-searched terms. But Angel claims he pulled data from Indeed.com that shows job trends for C# on the decline.

    In other words,

    "We cannot figure out what is going on in the IT marketplace, but we are supposed to be a resource for the IT marketplace. Please, help us analyze these trends because we cannot reconcile the differences ourselves!"

  31. No by tolydude · · Score: 1

    No, it is not on the decline.

  32. Re:How Much C# Do You Need To Know For an Entry Le by invid · · Score: 1

    If you can explain what a delegate is and use one to create an event, you can probably get hired.

    --
    The Moore-Murphy Law: The number of things that will go wrong will double every 2 years.
  33. It's really obvious why by Ravaldy · · Score: 1

    Like any statistic, it must be compared to something. In this case C# is being compared with other languages that have been riding the mobile device market. With MS's mobile market share being what it is it's not surprising that C# is appearing to have weaker growth compared to say C++,Java...

    At the end of the day C# is just another way to write code. If you are good at reading/writing code it doesn't matter what language it's in. My strongest language is C# because it's what I've done for the last 8 years non stop. SQL is probably my second. C++, VB, assembly, JavaScript, HTML are also languages I'm very versed with and read/write almost just as easy as C#.

  34. Microsoft killed .Net. by TangoCharlie · · Score: 4, Interesting

    Microsoft sealed the fate of .Net by not choosing it as the basis for Windows 8.x and the metro UI. That indicated that Microsoft no longer sees .Net as the next gen framework for Windows, .Net has, of course, done its job. Which was to kill Java. Which, for desktop applications, it has.

    As a Windows developer, it leaves me with somewhat of a dilemma. Which framework is the way forward on the Windows platform? It's not MFC, nor Silverlight. Is it .Net? Is it Metro?

    --
    return 0; }
    1. Re:Microsoft killed .Net. by Twinbee · · Score: 1

      If you apply that logic generally, you could say Microsoft tried to kill Windows by trying to force Metro upon everyone. .Net is the good part; Metro however can dive off a cliff.

      --
      Why OpalCalc is the best Windows calc
    2. Re: Microsoft killed .Net. by art123 · · Score: 1

      That is fresh news to me. Can you post some references? Microsoft's recent Build conference had many sessions on XAML as used in Universal Apps (win 10, win 10 mobile, win 10 on xboxone). Xamarian supports cross platform (iOS, android, win) ui using XAML. I greatly prefer XAML over html for building universal apps.

    3. Re:Microsoft killed .Net. by art123 · · Score: 1

      .NET was designed before mobile became such a big deal. WinRT is supposed to be the energy efficient answer to iOS and Android. If MS allowed the use of full .NET framework, apps might do things in a very energy inefficient way. For example, everything in WinRT is async. If thread is waiting on i/o, the thread will give up its cpu. Of course you can still write a "while true { }" loop in WinRT and depend on the os to switch threads when the timeslice ends but in general, WinRT makes it a lot harder to make energy inefficient apps.

    4. Re:Microsoft killed .Net. by AqD · · Score: 1

      Self-evident by the very tiny numbers of Java desktop applications on Linux, where most desktop applications are meant to be cross-platform.

    5. Re:Microsoft killed .Net. by Qbertino · · Score: 1

      MS didn't kill Java - Oracle did. ...
      And on a sidenote:
      You might want to consider abandoning Windows as a plattform.

      If you're looking for something stable with a brand and a future, perhaps you should try the Google ecosystem. With either web or android. I see Windows on the downslope. It only takes a critical mass to see Exchange as a dated groupware model and moving to Google and to see a subscription to office software for the bizar contraption it is and moving that to Googles free version aswell. Once that happens, Google will have taken over the planet for the foreseeable future and MS will be lapping up its dribbles it leaves behind.

      --
      We suffer more in our imagination than in reality. - Seneca
  35. See Betteridge's Law of Headlines by Wain13001 · · Score: 1
  36. Re:Java, and C#/.NET longevity? by MightyMartian · · Score: 3, Interesting

    Java dwarfs .NET, no matter what the MS shills claim. Whether or not Java is superior to C# is rather besides the point, rather how it was fairly irrelevant how superior any number of languages were to C in the 70s through the 90s (or by some definitions even now). It's simply a matter that Java was for a long time the only major cross platform application ecosystem, so the big enterprise outfits used it, and it's become rather like COBOL.

    Microsoft flunkies love to get into these pissing matches with dominant technologies, and try to rejig the question so their products and technologies have the appearances of being on top (just look at how the shills try to act like Surface has any relevance at all).

    If I was looking at getting back into coding (which I'm not, I've happily left that world behind), I'd sharpen up my Java skills, as I'm more likely to find sustainable employment there than with whatever Microsoft is trying to fool me into using now.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  37. Too much "special sauce" in .NET by Chas · · Score: 1

    Just about every .NET implementation I see has all sorts of crap in there, completely black-box.
    And when it breaks, usually because the programmers assume some bog-standard "clean" environment, there's no actual "troubleshooting" recourse.

    --


    Chas - The one, the only.
    THANK GOD!!!
  38. They don't search for C# by Ravaldy · · Score: 1

    Most C# developer I've met over the years search without the C# tag like I do. I'll do something like this: ".NET copy filestream to memorystream".

  39. Re:Silverlight is on the decline - not .NET by neminem · · Score: 2

    Hard for silverlight to be "on the decline" - it was always crap. It was crap when it was first unveiled, it stayed crap, it's still crap. Nobody gives a crap about it, cause it's crap. When I see sites using silverlight, I know the site is gonna be crap, too, even more so than flash (which is also mostly crap).

    C# in general, though, is amazingly pretty. So is the winforms API, and so is asp.net MVC (not webforms, webforms was super crap). I'm absolutely happy to have a job that's built on C# programming (didn't plan it that way, just sort of happened), and I've started using C# for little scripts and stuff I need at home, too. I don't think it's on the decline at all.

  40. Outsourcing? Recession? by mschwanke97402 · · Score: 1

    So, if job .NET postings are down on some job listing site does could that mean that there are fewer ,NET jobs here or is a lot of the work being contracted to India? Perhaps there is an overall slowdown in the market? Seems a pretty weak data to support a pretty flimsy argument.

  41. As a Java/C/Python Multiplatform Programmer. by drolli · · Score: 1

    No. Its not an the decline. It's a rock solid language and in a few cases i had to bind complex functionality on windows systems in a controlled way, and used C# and it was a very good experience. I donâ(TM)t see any reason that the language will decline soon. maybe it wont have explosive growth, but Java did neither grow from one day to the next.

  42. Iteration, Openness by labradore · · Score: 1

    There's three basic things that Microsoft is doing right these days and it applies to .NET as well as many of their other technologies / products.

    1. They steadily iterate. .NET had the advantage of avoiding a lot of the bad old parts of Java because it came afterward and the designers had a good handle on what wasn't working. When something is missing or isn't working well, they address it in the next release. Microsoft has had a fairly consistent 7 major releases in 12 years. The longest gap was 2.5 years from 1.1 to 2.0 and 3.5 to 4.0. Those were also where the biggest upgrades came from. Java went 4.5 years from v6 to v7 and then almost 3 more years to v8. There's been about 9 major releases in 20 years. The pace is slower, the gaps are longer. By itself this isn't a big deal, but when it comes to evolving to meet the needs of developers, MS has the advantage.

    2. Microsoft has figured out how to play in the open. .NET is well on its way to being a completely open, standardized technology. It's becoming viable to run it for real on Linux servers. The web stack is becoming very flexible and powerful. The advantages of openness that used to accrue to Apache and PHP and MySQL are now becoming strengths in .NET as well.

    3. .NET has Microsoft's superior documentation and support.

    I really used to dislike M$. I wrote a fair amount of Java on Linux. The MS products and operating systems are not cheap. The have been ruthless competitors and sometimes illegally so. But it's really pretty amazing to consider how well they support their stuff and how well they document it relative to the messes I've dealt with in the Java world. Oracle just doesn't appear to have as strong a team at work behind their stuff.

    I still love languages like Scala and Python and I still want Linux for most of my web servers, but the gaps are closing and the game is getting really interesting. If you are ignoring Microsoft, you may get caught by surprise.

    1. Re:Iteration, Openness by MightyMartian · · Score: 1

      How much did that low UID cost Microsoft?

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    2. Re:Iteration, Openness by WuphonsReach · · Score: 1

      #3 is pure shill. MSDN documentation is crap for 90% of what you search for compared to how it was back in 2000.

      The big problem with MSDN is that they change URL schemes every 2-3 years, breaking every reference URL that you might have saved. Then there's the almost, but not quite, completely useless form of the documentation which tells you everything you already know without making the water less murky.

      --
      Wolde you bothe eate your cake, and have your cake?
    3. Re:Iteration, Openness by shutdown+-p+now · · Score: 1

      I still love languages like Scala and Python and I still want Linux for most of my web servers, but the gaps are closing and the game is getting really interesting. If you are ignoring Microsoft, you may get caught by surprise.

      The funny part is, MS is no longer trying to pretend that the world ends at its bubble - .NET is nice, but not all people like it, and it's not perfect for everything; and that's okay. So, for example, you can do Python using Microsoft tools and on Microsoft platforms (and yes, it is all open source under sane licenses like AL 2.0). At the same time, a Microsoft employee is one of the core CPython maintainers, and is basically responsible for the official Win32 releases. Expect more of that kind of thing in the future.

      (full disclosure: I am a developer on the PTVS team)

  43. Re:New low for Slashdot by MightyMartian · · Score: 1

    You're post has just generated $1.37! Thank you for making Dice money. Please post again, but this time with more swearing. We've determined that using the word "fuck" at least once in every sentence adds an additional 13.8% to your post, and the word "cunt" an additional 15.7%. Be sure to mention Rand Paul, either in the negative or the positive, as either way generates a whopping 27.4%.

    For instance, if you had written your post thusly, we calculate your post would have earned Dice over $5.00!

    "Linking to some *fucking* guy's ramblings in a "word document" in OneDrive, *just like Rand Paul*: a new low for Slashdot, that *cunt-like* *Rand Paulian* news source. Is any website immune from *fucking* corporate "monetizing" (just like *fucking* *Rand Paul* *cunt* any more? Could slashdotters pitch in to fund a fork?: https://www.google.com/contrib... [google.com]?"

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  44. Nah by allquixotic · · Score: 1

    When PHBs think of development, they think of one of two things: either an MS Access database with code-behind in VBA, or they think of Visual Studio. Naturally, nearly all of the most useful features of Visual Studio hook into at least some kind of .NET language or runtime.

    As long as PHBs continue to consider Microsoft stuff as the "name brand" for software development, like Kleenex for tissues, we won't see .NET going anywhere. After all, if they're willing to bankroll $1M in license fees for a couple hundred devs to buy VS Ultimate...

  45. Re:Java, and C#/.NET longevity? by WuphonsReach · · Score: 1

    Having played both sides of the fence, Java vs C# for server-side stuff is about equal. Especially if you use a good framework, inversion of control, and unit/integration testing. At this point, you can succeed with either.

    The main downside right now with C# is your limitation to running on top of Microsoft Windows/Azure servers stack. Support for running against non-Microsoft technologies (such as PostgreSQL, or under a different O/S) is still a rough edge.

    --
    Wolde you bothe eate your cake, and have your cake?
  46. Re:Look at stackoverflow.com/tags by Anonymous Coward · · Score: 1

    Don't pull shit out of your ass

    Please choose your images more carefully, some things cannot be easily unthought.

  47. Re:WTF? by Ronin+Developer · · Score: 1

    C# and .NET were Microsoft's answer to Borland's Delphi (which was their answer to VB) and Java. They poached Anders from Borland after he created Delphi and they didn't want another ass kicking. I have always wondered if he had the idea for .NET before going to the dark side and that Borland, when they went off their their idiotic Java vision quest and became Inprise, blew him off and Microsoft realized the potential of his vision. He has had free reign pretty much ever since.

    I don't dislike the .NET platform. Still, I find it ironic that Microsoft Skype is abandoning the Modern interface and rolling back to the older Win32 version (ironically, written in Delphi).

    And, I find it interesting that Delphi has been rising on the Triobe index (currently, at #10...just behind JavaScript) after everyone predicted its certain demise. C# is in the 4th place and rising.

  48. Re:Silverlight is on the decline - not .NET by art123 · · Score: 1

    I would hardly call Silverlight crap (on the technology front anyway), especially when compared to Flash. If the goal was to give Microsoft desktop developers (.NET/C#/WPF XAML) a way to make very rich browser based apps, then it succeeded. Don't forget that many more vertical market apps are built and used within a company, rather than the public facing internet. I don't think I've ever seen a public facing use of Silverlight besides Netflix (and they have now moved away from it only very recently because finally HTML5 has caught up on the media side). I'm sure Microsoft was hoping Silverlight would be adopted as widely as Flash but right when Silverlight finally became decent (v3+) was when iOS took off and all plugin based web add-ons started to tank.

  49. Re:Silverlight is on the decline - not .NET by AqD · · Score: 1

    Huh? Winform has been deprecated by WPF and XAML-based UI for 10 years. Winform is essentially the same old crap that comes out from OS/2 before made into Windows API, just an object-oriented wrapper of stone-aged tech. You have no idea what you missed.

    It is even worse than Motif and TK, which at least have proper automatic layout system.

  50. .Net the Longest Part of a Windows 7 Reinstall by BrendaEM · · Score: 1

    It takes longer to run the .net updates than it takes for the whole rest of a reinstall.
    What crap!

    --
    https://www.youtube.com/c/BrendaEM
  51. don't think so... by SuperDre · · Score: 1

    With MS now opensourcing their .NET framework, and more and more crossplatform development enviroments using it, I don't see it happening that it will really go into decline.. Let's not forget C# is a language which is not specifically coupled with .NET..

    But what would be the next 'hip' language to do your work in?

  52. .Net will never die by Demonoid-Penguin · · Score: 1

    Because the world can never have enough calculator utilities. But mostly because .Net is the perfect zombie code.

  53. It never was on the rise. by Qbertino · · Score: 1

    .Net, from day one, was a vehicle for clueless middle-managers to justify sitting around blabbering web-economy bullshit and spending ginormous amounts of money for their consulting buddys to scoop up because they have a few devs at hand that are willing to play along and develop under-performing, non-future-safe, overpriced superfluos crappy MS-lockin middleware and shoddy MS SharePain intranets.

    I said it when .Net came out, and it holds true to this very day: With Java and other toolsets being FOSS, there was no point whatsoever for .Net - a Type A MS plattform login, no matter how MS marketing bullshit tries to spin it.

    *Everyone* with more than 2 braincells saw this and still sees this. If they'd've FOSSed .Net 10 years ago, like I and many others, even right here on slashdot said they should do, they might have had a chance. This way .Net, like all proprietary closed source software, is a dead end, and everyone with a brain stears clear or just does it for the quick cash and doesn't expect it to be around in the long run.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:It never was on the rise. by CustomSolvers2 · · Score: 1

      You are talking about managers and your speech sounds too manager-like (or HHRR-like?). To not mention that you are focusing on web when the true big deal of .NET is precisely desktop. Together with nonsensical claims like "never on the rise" or talking about stupid people using the .NET Framework?! (most of the programmers creating applications for the most widely used OS are stupid?!)

      Usually programmers talk about programming environments being better, supported by a wider number of users, more programmer friendly, etc. But you are basing your claims on a set of abstract ideas talking about the general attitudes of the companies making the programming languages.

      As a programmer, I might not like certain companies, because of their general attitude; but if they happen to create something objectively better, I would accept it and start using it. Other programmers might think differently than me, but will certainly not mix technical stuff with disliking the company up (and, in any case, will never bring “manager decisions“ into a programming language discussion, as far as they are completely irrelevant; and what about "marketing"?! how can you mention such a thing in a discussion about what programming language to use??!)

      From the programming point of view, the .NET Framework (and its IDE, Visual Studio) is a step beyond on desktop (and on web it is unclear, as far as their approach is completely different to the remaining approaches and thus not easily to be compared) and don't think that any (even half knowledgeable) programmer will ever discuss about the quality of the .NET framework languages. Other issues (like limited capabilities outside Windows or preferring to continue using the programming language you have been using for a while) are perfectly valid reasons to not use .NET at all. But saying that "was a vehicle for clueless middle-managers to justify sitting around blabbering... " etc. is completely against the reality.

      The .NET development team has done an impressive work (unlikely many other development teams at Microsoft) during the last years and, as a result, we have a really good programming framework. You might not want to use it; or not like it; but you shouldn't dare to critise something so unmotivatedly (i.e., at the technical level/quality of the framework, when this is very far away from being a true issue), much less when not having the required knowledge (what, correct me if I am wrong, seems pretty clear from your post).

      --
      Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  54. Better solution required by gladius17 · · Score: 1

    I wish some rich Slashdot reader would buy dice to acquire Slashdot

    And financially reward Dice for their crimes....? Hell no. Unacceptable. I will not be satisfied until all Dice executives and employees, down to the janitor and secretary, are living under a bridge and dumpster diving for their next meal.

    Someone just needs to make a new website, and let this turd circle the drain.

    How hard could it really be to duplicate and/or improve upon the site design, let alone the self-described editorial staff? Use the classic low bandwidth style, HTML/CSS only with only a tiny smattering of Javascript as UI sugar, and get rid of all the Web 2.0 garbage. Maybe even put in some God damned Unicode support, and rethink the karma system so good comments don't get buried under bad moderation. Design the site right and seed it with interesting (and timely) stories, and it will take off, while this place turns into a graveyard in short order.

    Fuck Dice with a sword for ruining what was once a great web site.

    Why--just fucking why--does the entire Western world have to be overrun by such imbeciles?

    God help us all.

    the user formerly known as shiftless (410350)

    1. Re:Better solution required by gladius17 · · Score: 1

      Neither one has got the formula exactly right. What do either one of those web sites have to offer, that can't be more easily found somewhere else?

    2. Re:Better solution required by gladius17 · · Score: 1

      Perhaps I should have been more clear. Simply copying this site verbatim is a waste of time. The new site obviously has to be significantly better in some way in order to actually attract an audience. The question remains: how hard can that really be? Judging by those two sites, the answer is obviously, "harder than one would think, if one assumes that everyone else is as competent as he is."

  55. Not so fast... by joerdie · · Score: 1

    Every large company in my city (Cincinnati) uises .NET heavily. Some of them are using VB, but they are almost exclusively using .NET. The amount of money and inertia to change that is so high that I don't see how OP's assertion could be correct. Big companies like Microsoft. And that's okay.

  56. Re:WTF? by rcase5 · · Score: 1

    Hmmm...very interesting, both on the rise of Delphi and that Skype is going back to their Win32 interface (written in Delphi).

    I have to say that, when Skype went to whatever the hell they're using now, it became like almost everything else Microsoft makes; bloated and sluggish. It takes my Skype client 2 minutes to start up. I'm guessing they got complaints and saw a decline in usage. I'm glad they're going back to a client base that seemed to work reasonably well.

    An interesting note (perhaps?), Skype originated in Australia. I worked for a company that also had origins in Australia, and an internal tool they wrote was written in Delphi. I wonder if this is a general trend in Australia. Because in all other Windows desktop app developers I've worked for (Silicon Valley) had always used Microsoft Visual C++/Visual Studio/MFC (I might be dating myself here). One company had a Java applet, but it was to be used in conjunction with a back-end that was written in Visual C++.

  57. Interesting by Giant+Electronic+Bra · · Score: 2

    I think the problem is that you can make a higher quality product using Qt, but it IS more expensive. Writing C# code, or Java line-of-business stuff is just more cost-effective when the use cases are very specific. I mean I wouldn't write some one-off program to manage some tiddly business process somewhere in C++/Qt because nobody cares if it has to run on a Windows box, and nobody cares if it is fast, small, or even all that reliable. So a vast array of stuff exists in these environments.

    Then there's super high-reliability stuff, like most of the code I write. It has to handle 400 million transactions in a week and never crash, never miss one, etc. It certainly COULD be written in C++, but the hunt for stupid programming errors you can't make in Java just makes it more costly. Its also easier to train a Java/C# guy to a level where he can do decent work.

    --
    "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson