3 ms·

It's really not. It's a hellscape of insanely rapid platform churn, abandonware, payware and half-assed bug-ridden copy implementations of libraries from other

by hughrr 5y ago

It's really not. It's a hellscape of insanely rapid platform churn, abandonware, payware and half-assed bug-ridden copy implementations of libraries from other ecosystems all stuck together with marketing crowed from a bunch of people with Stockholm syndrome. I have literally used it along side several other ecosystems for the full lifespan of it from beta, and it has in large been a very very expensive mistake in the long run compared to the other platforms.

smackeyacky 5y ago
I always used it without the desktop gui frameworks and didn't have this experience, aside from a couple of abandoned 3rd party tools. One web thing I did has been chugging, unchanged for 15 years. Overall it has been great for me. But getting sucked into silverlight would likely have soured me on it.
- hughrr 5y ago
  Agree on the desktop. The peak of development was when Windows, Visual Studio and .Net framework releases were synchronised and we were targeting Windows Forms. That was almost bliss. I got so much work done. That started in 2002 and ended in about 2010. I built some stuff in C# on Windows CE as well which was interesting too.
  - smackeyacky 5y ago
    CE development must have been interesting. Not sure I ever saw a CE device that had enough room left over for another program. Back when I switched to .NET the future looked like web apps. Can't say I am particularly prescient but of all the tech in .NET, the web stuff thankfully had the longest legs so I'm kinda glad I avoided the slow death spiral of MS's ever changing desktop moods.
    - hughrr 5y ago
      It was roughly on par with iOS development now strangely enough. But with a light weight windows forms abstraction. We did unholy things on CE which were quite impressive.
mdb31 5y ago
Your response is not only hyperbole, but also not very consistent with, like, reality. If you've really used .NET "from beta", you'll know that the platform became a snoozefest around 4.5, only to be revived around Core 3.0. "Insanely rapid platform churn" it is not. And abandonware? Silverlight, sure, not much future in that (although it still runs fine on its own) but how is Adobe Flash doing these days, talking about "other platforms". Or Java Servlets? In-browser applets?
- pritambarhate 5y ago
  Java Servlets - these are backend services. Those run fine even today and are 100% supported by at least 2 (there must be more, but I have not checked) app servers that I regularly use.
  - mdb31 5y ago
    Really? You never had to change a single line of code in a servlet due to JRE/host environment changes? I've had to migrate my server-side Java code at least twice in the last decade. But possibly I'm just not understanding the needful?
- hughrr 5y ago
  I don’t think you know what you’re talking about nor have dealt with significantly sized enterprise platforms. In fact there was a hell of a lot of churn while Microsoft pissed around with the MVC middleware stack implementation and throwing async in which has been buggy as hell on classic. And of course there was the entire “we decided to gut WCF and WWF and AppFabric” thing. I lost count of the hours I spent digging through deadlocks and spinwaits. On .net core there have been many many breaking API changes over just the last three years which have broken everything from libraries to the stack. There has also been absolutely zero to no guidance on what best practices are in the current hour. All the documentation and articles out there are obsolete within a gnat’s fart of time after they are written. There was a lot of change and not a lot of thinking that went into the platform over the years. This costs big money for clients.
  - 5y ago

by hughrr 5y ago

smackeyacky 5y ago

I always used it without the desktop gui frameworks and didn't have this experience, aside from a couple of abandoned 3rd party tools. One web thing I did has been chugging, unchanged for 15 years. Overall it has been great for me. But getting sucked into silverlight would likely have soured me on it.

hughrr 5y ago
Agree on the desktop. The peak of development was when Windows, Visual Studio and .Net framework releases were synchronised and we were targeting Windows Forms. That was almost bliss. I got so much work done. That started in 2002 and ended in about 2010. I built some stuff in C# on Windows CE as well which was interesting too.
- smackeyacky 5y ago
  CE development must have been interesting. Not sure I ever saw a CE device that had enough room left over for another program. Back when I switched to .NET the future looked like web apps. Can't say I am particularly prescient but of all the tech in .NET, the web stuff thankfully had the longest legs so I'm kinda glad I avoided the slow death spiral of MS's ever changing desktop moods.
  - hughrr 5y ago
    It was roughly on par with iOS development now strangely enough. But with a light weight windows forms abstraction. We did unholy things on CE which were quite impressive.

mdb31 5y ago

Your response is not only hyperbole, but also not very consistent with, like, reality. If you've really used .NET "from beta", you'll know that the platform became a snoozefest around 4.5, only to be revived around Core 3.0. "Insanely rapid platform churn" it is not. And abandonware? Silverlight, sure, not much future in that (although it still runs fine on its own) but how is Adobe Flash doing these days, talking about "other platforms". Or Java Servlets? In-browser applets?

pritambarhate 5y ago
Java Servlets - these are backend services. Those run fine even today and are 100% supported by at least 2 (there must be more, but I have not checked) app servers that I regularly use.
- mdb31 5y ago
  Really? You never had to change a single line of code in a servlet due to JRE/host environment changes? I've had to migrate my server-side Java code at least twice in the last decade. But possibly I'm just not understanding the needful?
hughrr 5y ago
I don’t think you know what you’re talking about nor have dealt with significantly sized enterprise platforms. In fact there was a hell of a lot of churn while Microsoft pissed around with the MVC middleware stack implementation and throwing async in which has been buggy as hell on classic. And of course there was the entire “we decided to gut WCF and WWF and AppFabric” thing. I lost count of the hours I spent digging through deadlocks and spinwaits. On .net core there have been many many breaking API changes over just the last three years which have broken everything from libraries to the stack. There has also been absolutely zero to no guidance on what best practices are in the current hour. All the documentation and articles out there are obsolete within a gnat’s fart of time after they are written. There was a lot of change and not a lot of thinking that went into the platform over the years. This costs big money for clients.
- 5y ago