Lucky

The project I’m on right now originally had the nuget.exe saved in source because they had to manually run it through build scripts, it wasn’t built in to VS until VS2012

I’m guessing they only used it 10 years ago when it was very rough around the edges. It didn’t integrate well with the old .NET Framework because it conflicted with how web.config managed dependencies and poor integration with VS. It was quite bad back then… but so was .NET Framework in general. Then they rebuilt from the ground up with dotnet core and it’s been rock solid since

Or they just hate Microsoft, which is a common motif to shit on anything Microsoft does regardless of the actual product.

I’ve never had an issue with nuget, at least since dotnet core. My experience has it far ahead of npm and pip

There are a number of alloys that are used when working with desalinization plants, but the effective ones are cost prohibitive.

Even if they had a way of pumping it out cheaper, it still comes with issues that are costly. There are chemicals used during the process which pollute the brine and cost money to remove. It also comes out much warmer than surrounding water which disrupts the ecosystem. The brine eats up oxygen levels and suffocates animal life in the area.

They are trying to dilute the brine before releasing it back to the ocean but this is either not effective enough since you’re using salt water from the same source you’re pumping into, especially if the area doesn’t have strong currents to carry it away. Or you’re using water which doesn’t have high salt levels and can dilute it to healthy levels, which you might as well just treat and use in the first place instead of using saltwater.

It’s not an easy problem to solve at the moment

I’d be concerned about it leaching into the water table with that approach. Plus transport to those mines could be very expensive and complicated

Salt is highly corrosive, especially when concentrated into a slurry. If you dump it directly from shore you kill any local wildlife and destroy the local area before it dilutes. If you pipe it further out into the ocean the pipe will continually need maintenance due to corrosion and makes it more expensive

If you dump it on land you also need to ensure it isn’t exposed to wind which will kick it up and cause health hazards to local populations. So you can bury it, but that doesn’t scale and adds to the costs

Don’t let lack of knowledge ever be the reason to stop trying something in homelabs! Honestly for a beginner resource ChatGPT is where I’d go for these kinds of questions. It does a great job explaining what all the terms mean and you can drill down into topics as needed such as permissions and different terminal commands you’ll need

Anyways, this link has a decent description of samba:

https://ubuntu.com/tutorials/install-and-configure-samba#1-overview

A Samba file server enables file sharing across different operating systems over a network. It lets you access your desktop files from a laptop and share files with Windows and macOS users.

So as long as a computer is on the network it could access files stored on this hard drive. It is super useful as a first homelab project

How does that philosophy come from Windows? Windows was all about tying your application directly to the host OS via the old .net framework and COM. You had to wait for the OS to update before your app could, or the OS could randomly update and break your app

Containers as a technology are almost entirely a Linux thing as well, Windows ships with a full Linux kernel to support it now.

Minnesota is home to the juicy lucy, a cheeseburger with the cheese being cooked inside the patty. Serve that with a tater tot hot dish

Microsoft develops vscode as open source, but compiles it with proprietary telemetry tooling.

VSCodium compiles from the same source code but without the telemetry

Rider works great on Linux, assuming you’re on dotnet core (or .net 5+)