71–80 of 84 posts
"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality." Wait - net6.0- is actually net5.0?
the future of .net? the cemetery lol they still playing catchup with java when the real threat was GO, now they are behind, and far far behind
Catch up with java? C# .net was always ahead. The advantage java had was the ecosystem.
The truly great thing about java is sun somehow created an ecosystem, a community. Probably by leading with specs, always, and not implementing anything but the core. So, you wind up with a real marketplace and a collaborative development effort. The variety of widely-accepted non-Sun solutions is an indicator.
Meanwhile, in microsoft-land... no spec, no standard. It's just "whatever MS does, that's the Thing." Nothing 3rd party is implemented because (a) no spec, and (b) MS has a nasty habit of cutting 3rd parties off at the knees. (Maybe because they're not happy with what 3rd parties develop, because... no spec.)
The result? Microsoft blinders. "If MS didn't invent it or publicize it at Build, it's no good."
So, you get the absolute ferment of java (and python, same factors, really) or... solutions by MS or MS vendors, which is more limited because a profitability case has to be made to lenders.
MS really did play catch-up with Java, which they were able to do because of the MS tax. Don't make any arguments based on technological superiority, 'cause there ain't none. Java (and the entire web, really) caught MS flat-footed. Bottomless pockets saved them.
Earlier quoted context omitted.
What 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…
We 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.
Earlier articles in this ongoing series of “how to name things”: - September 2016: Introducing .NET Standard ( https://devblogs.microsoft.com/dotnet/introducing-net-standa... ) - May 2019: .NET Core is the Future of .NET ( https://devblogs.microsoft.com/dotnet/net-core-is-the-future... ) - May 2019: Introducing .NET 5 ( https://devblogs.microsoft.com/dotnet/introducing-net-5/ ) (Yes, the last two are from the same mo…
Omfg, the hours I've wasted searching for netframework answers, and all the search results are netcore. Because search engines prefer newer, and nobody adds "framework" to their questions.
This is good news for experienced .NET developers and newcomers alike. It marks the end of the journey from legacy .NET Framework to fully open source cross-platform .NET. .NET Standard was confusing, and the ubiquitous TFMs in the early days were even more so. But all of those struggles where made to achieve a cross-runtime compatibility layer to make it easier to support both ecosystems. It was a Herculean effort b…
I fear it marks the beginning of a very long dark journey, where .net developers are forced to work on more and more obsolete software while looking with envy towards other platforms which are actually maintained. The "core" migration is not a problem for short-lived startups, but .net is used a lot in business and enterprises. They don't rewrite their whole stack every two years but prefer an incremental approach. S…
Earlier quoted context omitted.
What 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…
We 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.
Earlier quoted context omitted.
We 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.
At 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.
Was a waste of money and time.
Earlier quoted context omitted.
golang isn't really a threat. It's a weak language with a very messy ecosystem. They don't even have proper versioning figured out, not to mention a proper package manager.
It capturing the minds of youth way faster than .NET did. Package management is an absolute mess on NET too. I was working on a project that had to work with old Mono versions, so it still used packages.config. Behold this mess: https://docs.microsoft.com/en-us/nuget/reference/packages-co...
Earlier quoted context omitted.
At 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.
I’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.
Resume Driven Development.
Earlier quoted context omitted.
I’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.
For the company yes, but not for your resume right? Resume Driven Development.