brandon

And iirc the next fedora release will finally unify everything under /usr/bin.

On my current Fedora 40 install /bin is already a symlink to /usr/bin

Well, butter my butt and call me a biscuit

With the exception of some stuff used for windows desktop development, .NET (“dotnet core” is just .NET now) is released under the MIT license. I’m not following how using .NET would be contributing to the “agenda of proprietary software”.

The dotnet cli tools that come with the SDK run just fine cross platforms without Visual Studio. Your Linux distribution probably packages the SDK already, just install and use it.

If you want, you can use C# without .NET by using Unity, mono, or maybe Godot now I think?

why American government has not gone after Proton like they did with Lavabit

Lavabit was based in the United States. Proton AG operates entirely in Switzerland. Ostensibly the US government would have to go through the Swiss court system to get anything out of Proton.

.NET core is supported on Linux. There is some stuff that won’t work on Linux, like WPF, but it doesn’t sound like you’re using that.

If you are searching specifically for “.NET hosting” you are bound to come across a bunch of Windows results, so I wouldn’t recommend that.

Any Linux virtual server provider will work just fine, provided they support a Linux distribution that runs the .NET core runtime, (which includes all the major ones). I’d avoid AWS or Azure. Those are a good way to run up a big bill pretty quick.

A $5 vm from the likes of Linode, Digital Ocean, Vultr, etc, will get you started just fine. Typically the costs won’t be able to “spiral out of control”–you’ll be allocated a set amount of CPU, memory, disk, and network usage.

It depends, and there’s a lot of variation obviously, but,

A frontend developer writes the stuff that runs on the client,

A backend developer writes the stuff that runs on the server (it can be repetitive–any programming can be, but it certainly needn’t be. It’s not always as flashy as frontend but there are still some exciting challenges),

And finally, a full stack developer does whatever the company wants, and damn it, they had better enjoy it too.