brandon

I once got called the f-slur for having the audacity to read a book in public, outdoors in front of the library.

This is the first beard I’ve ever seen make someone’s chin look weaker.

Edit: is it accessible without knowing much Japanese?

It is, if you look a few things up, but there’s also a readily available translated “backup copy” floating around.

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

Slaves don’t have private ownership of their capital (that is, their own labor)… because someone else does.

Most “free” workers, in terms of capital, own only their own labor.

Capitalists own the majority of the capital–land, equipment, intellectual property, etc.

A system where the workers own the capital (aka the means of production) is socialism.

.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, and their service offerings are quite complicated.

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.

You will have to configure the web server & .net yourself.

I am assuming from your post that you don’t have a lot of experience with Linux. You can try setting it all up from home too if you have an old PC or laptop lying around (either for practice, or to self-host long term). Download a linux distribution and give setting up a server a shot.

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.