341–350 of 351 posts
I'll take the opportunity to jump on this thread to fish for recommendations on courses/guides to learning C# to be used with .NET - for programmers. I mainly see those that are way too simple or way too Windows specific.
Earlier quoted context omitted.
There is no immediate problem with building from source, there simply isn't much of a benefit to doing so. An assembly compiled with different optimizing C# compilers will be virtually identical assuming the source files are identical. I can think of a reason not to compile from source: it's essentially statically linking code into your assembly which can be huge problem for middleware packages that want to override…
Hm. Thanks for this and previous answers. > I can think of a reason not to compile from source: it's essentially statically linking code into your assembly which can be huge problem for middleware packages that want to override the specific version you depend on. This is very common with the JSON serialization library, which is highly backwards compatible. I think if .NET were integrated into Linux package management…
Earlier quoted context omitted.
I think you may have missed the train of thought.
Azure, "the Microsoft platform" is said to be around 60% Linux. Source, elsewhere in these comments: https://news.ycombinator.com/item?id=32483239
Earlier quoted context omitted.
> with Rails I have to introduce React Do you know about Hotwire? It's Rail's html over the wire solution and seems comparable to Blazor.
Hotwire I believe wasn't introduced yet but was close to release when I left the Rails dev community.
Earlier quoted context omitted.
> Microsoft might acquire Ubuntu That would make a lot of sense, despite the backlash it would generate. Remember when they acquired GitHub, developers were vouching to move over to GitLab. Yet very few did. The same would probably happen if they acquire Ubuntu. Developers would vouch to move to another distribution, yet few will, because Ubuntu is so much nicer to use than the competition.
I'll be one of the few. Maybe I'll give a try to Debian but probably I'll end up using one of the Ubuntu replacement distroes that will popup. Or Pop!_OS outright. I'll never trust Microsoft again after all they did in the 2000s. Transitively, I'll never trust any comparably sized company.
Earlier quoted context omitted.
Repro steps: sudo apt install dotnet6 - Observe the “telemetry enabled” message.
Hi! Could you be so kind and open a bug for this at https://bugs.launchpad.net/ubuntu/+source/dotnet6 ? Thanks in advance.
Earlier quoted context omitted.
Yup, Australia has a real hard on for C#. As a dev in Australia, I can support the list you gave, but I'd be cautious to extend that globally.
I'm from Europe and there's a lot of .NET jobs here too. In my experience, the US is the outlier with a very small .NET presence.
It's the other language stacks that are smaller, but just get more attention on startup-related discussion boards.
Earlier quoted context omitted.
The debugger is part of Visual Studio, which is a paid product. I don’t think it’s unreasonable to not publish the source for it.
Yeah, but the general standard is for open languages to either have an open debugger (e.g.: V8 JS) or else otherwise have support for an open debugger interface (e.g.: Rust via GDB). It's not strictly unreasonable for MS to offer a proprietary debugger, but it is bass-ackwards for the core .NET team to not offer an open source debugger or open standards compliant debugger interface to go with their open source langua…
Earlier quoted context omitted.
> Looking for a really good reason to make the jump Not having to pay for Windows Server licences? Better start-up performance, likely better overall performance, less resource usage. Assuming these are specific Windows calls, moving to something more cross-platform you could open development to colleagues with Mac or Linux machines (via VS Mac, JetBrains Rider or VS Code) if there are any. Options to use Kubernetes…
> Not having to pay for Windows Server licences? Chances are that those licenses are paid for already so this is a sunk cost. > Options to use Kubernetes or deploy to container services that run on Linux I think this would be a hard sell - "hey, let us migrate platforms so we can rewrite our entire production infrastructure "
Also "Oh and we need to hire two full time devops engineers to take care of the thing" :)