5 ms·

No thanks. I've been writing .Net since before day one and quite frankly I've been buggered around enough now to run as far away from this as possible.

• apalmer 6y ago
  Interesting, I always felt C# was a step ahead of Java, while the JVM was some steps ahead of the CLR.
  • qz2 6y ago
    The language is absolutely brilliant and I love it. It's the vendor's schizophrenia that's the problem. I've run out of fingers to count things that have been deprecated painfully on after being promoted as the next greatest thing and sold hard. This has cost me, my clients and my employers ridiculous amounts of money to unfuck.
    • cpitman 6y ago
      Totally fair, anyone in the Microsoft development ecosystem has to learn to be incredibly skeptical of anything new. Anytime I spent on adopting Silverlight was essentially wasted. I had one client that had adopted a random WYSIWYG released by Microsoft to design WCF services, when anyone experienced in the ecosystem knew it had abandonware written all over it. Of course, other ecosystems have their own versions of this. But Microsoft might be the only one that essentially controls an entire ecosystem and still manages to give devs whiplash.
      • qz2 6y ago
        Exactly. Yes I interviewed at a company where Silverlight and WCF was the future and they'd just rewritten everything in it. I didn't see it with the way everything was going. I dread to think of what happened to their business when the rug was pulled out overnight. "Microsoft says you need to start funding your entire product to be rewritten from scratch"
        • teh_klev 6y ago
          I don't know how long ago you're speaking about, but Silverlight and Flash were at their end of days even back in ~2006. Apple just nailed the coffin shut. That's not Microsoft's fault, there was a sea change in the industry away from browser plugins and these types of platforms. Apropos WCF, well we got JSON and no-one outside of "enterprises" were doing SOAP/WSDL et al any more and it was pretty much done. That's not really a fault of the vendor, the world moved on. At the end of the day, as a software development house you have to make strategic choices, regardless of vendor. And you can still build WCF apps today, sure maybe not in .NET Core, but they'll still be supported for donkeys years by MS, but who'd want to?
          • bruckie 6y ago
            Silverlight wasn't even born until 2007, so it's hard to see how it was dead in 2006. :) Or maybe you're saying it was DOA?
            • teh_klev 6y ago
              > Or maybe you're saying it was DOA? Pretty much. The only time I've ever seen Silverlight apps in the wild were for streaming use (Sky/Now TV for example).
      • spaetzleesser 6y ago
        Very true. I don’t trust anything new MS is putting out. The risk of being abandoned soon is just too high.
  • at-fates-hands 6y ago
    Not that my opinion means much, but I'm a UI/UX guy and I've always had a much better experience learning and using C# as opposed to Java.
• criddell 6y ago
  What would you choose for server code?
  • qz2 6y ago
    Probably Go at this point in time. They care about API stability, keeping scope focused and about technical improvement instead of marketing. And the language is nice to use! There are warts but they take a measured structural approach to resolving them and caring about the change.
    • dustinmoris 6y ago
      I was going to say the same, but you said it much nicer than I would have done.
    • forest_dweller 6y ago
      Are you saying that .NET API isn't stable? I have code that works from .NET 1.1 back in 2004. I wouldn't use any of their flavor of the month tech they release from the conferences. But the .NET framework has been pretty stable over the last 15 years.
      • qz2 6y ago
        No it doesn’t. Try it on .Net 5.0.
        • forest_dweller 6y ago
          It works with .NET Standard, .NET Core and .NET 4+ and I am pretty sure when I do the upgrade it will just work.
    • int_19h 6y ago
      Go might care about their own API stability, but it took them years to stop doing direct syscalls on macOS (where it is not a stable ABI); and last I checked, they were still doing that on BSDs. As for technical improvements, well... it's a language that took, what, almost a decade to add generics? And that's because the designers were claiming that everybody else is doing them wrong, and they want to figure out how to do it right. Now that they're finally adding them, turns out that they look exactly the same as everybody else's.
• gameswithgo 6y ago
  Wherever you run to, you will get buggered around a bunch and then run somewhere else.