8 ms·
This is the most schizophrenic platform I've ever worked on. I've just spent an hour trying to make something work across the five different variants and web pi
by qz2 6y ago
This is the most schizophrenic platform I've ever worked on. I've just spent an hour trying to make something work across the five different variants and web pipelines doing things underneath.
Edit: to be clear we have completely hung legacy stuff which is waiting resources (lots of $$$$ wasted) to port it to later versions of the frameworks because huge chunks of the ecosystem got abandoned by MS and the OSS developers who were supporting it.
On the positive side I'm getting paid danger money now.
- goto11 6y agoWeb forms?
- qz2 6y agoNope. An ASP.Net MVC project dragged through since CTP versions.
- golergka 6y ago> most schizophrenic platform > danger money In my experience, these often go hand-in-hand. Also, never heard 'danger money' and absolutely love it, thanks.
- bookshelf976 6y agoWhat do you mean by five different variants? Also, what are the chunks of the ecosystem that were abandoned? Web Forms? Silverlight? UWP? Microsoft has shown an amazing ability to modernize and improve the platform without dragging baggage around from one version to the next. We just took an ASP.NET MVC web app developed in 2005 for Windows/IIS and shipped it on linux using .NET core— the conversion took 1 developer just 2 days.
- qz2 6y agoTrivial projects yeah. This is not a trivial project. As for different variants. Two different http pipelines (classic, integrated), OWIN, one obsolete variant of OWIN, whatever is lurking inside .Net core now. WebAPI, MVC, bits of the remains of WCF floating around. Abandoned bits: WCF, WWF, older OWIN pipelines, SignalR and a huge chunk of open source projects and commercial CLR packages. It's a shit show it really is.
- WorldMaker 6y agoSignalR is still supported. Though yes, modern "Core SignalR" is something of a rewrite compared to older versions of SignalR, though the biggest backwards incompatible changes are JS client side, not server side .NET side (most of that remains the same once you swap nuget packages), as they dropped the magic JS autogenerated client for a sometimes more sensible "Event Emitter" style client.
- yread 6y agoWWF has nothing in common with the other stuff?! It was also one of the shittier MS technologies. Shipping software over decades is tricky: look at the alternatives: what web app from 2005 could you just run today? How has the platform developed over time? PHP, Perl, Python, Java, Ruby... No really clear winner there, IMO
- qz2 6y agoWhat about AppFabric which tied it and all their ESB stuff together. That was flushed faster than a bag of crack in a police toilet.
- nullsense 6y agoWe have a million line SaaS on .NET 4.7.2 running EF 5 that we can't upgrade to .NET Core. We can't do it all in one big bang as it's too much effort and too risky. It will like just continue to rot. We're trying to break it up somewhat and write new parts in .NET Core, but it's an ugly reality staring us in the face.
- andrewf 6y agoAt work, we sidestepped having to explicitly do a Python 2 -> 3 transition, because we were already rewriting the monolith as a bunch of microservices. Took 7 years.
- qz2 6y agoI’ve watched my current gig push microservices hard. Realistically after 5 years and a lot of investment only 10% of traffic lands on them. Was a waste of money and time.
- qz2 6y agoI feel for you