31–40 of 256 posts
There might also be significant performance improvements to gain by chnging to Linux, especially on startup time (this is true for Java and Node as well and in my limited tests it was absolutely true for dot net core a couple of years ago.)
Making JIT 4% (or whatever) faster is cool but it would probably have higher ROI for the .NET ecosystem if Microsoft assigned some of these high caliber people to instead work on improving or simply rewriting some of the atrocious open source libraries that are available. Would you rather have an A language/runtime with a D open source ecosystem or a B for both?
A lot of the library ecosystem still feels dominated by companies who make their money selling library code. If more successful, open-source friendly companies adopt .Net to create higher-level products and services one would hope that would help contribute to a more well maintained and more friendly licensed ecosystem. My sense is that things are improving though.
My favorite part of dotnet 6 is the focus on hot reloading not mentioned here. Being able to work on a webapp that rapidly reloads in under a second is huge. It allows me to maintain the state of flow as I'm bringing something to life. I had a unique use case wherein I had a separate worker thread that also needed reloading with the hotreload. I was able to hook into the hot reloading via "[assembly: System.Reflectio…
> My favorite part of dotnet 6 is the focus on hot reloading not mentioned here Does this work, for example, to reload method changes and so on? I miss this coming from JVM.
Method signature changes, class hierarchy, all of it.
He wasn’t a sun employee at the time and the sun folks kept telling him what he was doing was impossible. We ended up using his stuff, the dcevm, internally for a long time.
He was eventually hired by sun/oracle to work on other stuff and Java still doesn’t have proper hotswap.
That’s the tech world for you.
For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity. I have always loved .NET and it keeps getting better and better. They have shown remarkable flexibility to throw away ideas that don't work and have modernized. A large part of that is due to active involvement of the community. This could be a new model moving forwards, a software worlds equ…
I’m thorn on that. As someone who has had intermittent periods of .NET, it’s a complete mess every time I’ve come back after a couple of years off and figuring out what new APIs are the new thing to use, which have been deprecated and when looking for a solution of something involving e.g. configuring stuff in the web server request handing stack it’s a real confusing mess. Docs of course aren’t all up to date and ar…
Where should someone start if they wanted to get familiar and proficient with .NET?
Check out F#, the bastardized yet legitimate child of MSFT. If you like functional languages or would like to try it, give it a whirl! https://dotnet.microsoft.com/learn/languages/fsharp-hello-wo... If you use vscode, highly suggest to use Ionide extension. You’ll be quickly amazed at how smooth it all works.
For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity. I have always loved .NET and it keeps getting better and better. They have shown remarkable flexibility to throw away ideas that don't work and have modernized. A large part of that is due to active involvement of the community. This could be a new model moving forwards, a software worlds equ…
I’m thorn on that. As someone who has had intermittent periods of .NET, it’s a complete mess every time I’ve come back after a couple of years off and figuring out what new APIs are the new thing to use, which have been deprecated and when looking for a solution of something involving e.g. configuring stuff in the web server request handing stack it’s a real confusing mess. Docs of course aren’t all up to date and ar…
I understand your pain but I think most of the recent changes are necessary for the long-term health of the ecosystem, and I would not expect the breakneck pace of the last 5 years to continue forever.
For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity. I have always loved .NET and it keeps getting better and better. They have shown remarkable flexibility to throw away ideas that don't work and have modernized. A large part of that is due to active involvement of the community. This could be a new model moving forwards, a software worlds equ…
I’m thorn on that. As someone who has had intermittent periods of .NET, it’s a complete mess every time I’ve come back after a couple of years off and figuring out what new APIs are the new thing to use, which have been deprecated and when looking for a solution of something involving e.g. configuring stuff in the web server request handing stack it’s a real confusing mess. Docs of course aren’t all up to date and ar…
Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don't understand why they are pushing more and more features when they cannot complete the ones they started years ago. Not to mention that porting WinForms from .NET Framework to .NET 6 requires a rewrite for anything more complex than a Hello World.
These days, you can run .NET entirely on Linux, without ever touching Windows or Visual Studio.
(Founder here) At Amezmo [0], we've supported .NET for sometime now, and recently added .NET 6 as an option for our managed app hosting platform.