Uvix

You can usually get gas and get back home in under ten minutes, versus hours to get to an EV place and charge.

I can't imagine anybody switching to ADO from GitHub. Microsoft has made clear that ADO is on life support, and are slowly stripping features out like public repos.

I look forward to when GitHub Actions has feature parity with Azure Pipelines.

We have the expertise. We don’t have the interest in fighting our internal “security” teams to keep running VMs.

With hard disks, I could see reading the compressed version from disk and decompressing giving you the bytes faster than reading the uncompressed version. With SSDs that advantage likely went away.

The FAQ reads as "not yet", not "won't". This is second-hand but my impression is that publishing patches through GOG is not as easy as through other platforms (possibly because of their need to build new installers?).

You can but having to hook it up to a mouse and keyboard and monitor every time I want to install new games from not-Steam would be a pain.

We can do that on our developers' machines no problem, but there still needs to be a place for QA to do their testing.

Target as well. It was one thing when it was just Amazon acting as a sketchy third party storefront, but now everybody’s doing it.

I haven't found digital signage displays with the same brightness for HDR content, or variable refresh rate support.

Interdiction at the ports is the buyer's problem, not the seller's. Kidnapping people because of their employer sounds like a great way to lose tourism permanently.

It’s sustainable at $1/month at current costs, but those costs will go up over time. The subscription price could be raised accordingly but they can’t go back and ask for an inflation adjustment from people who bought it.

Per your link, Sony will soon be disallowing new purchases, but has not set a date for disallowing downloads of existing purchases.

Amazon may not be going away tomorrow, but they have form for disallowing redownloads of old ebook purchases. If you dared to buy ebooks from them pre-Kindle, you can't access them anymore. If you hold onto your Kindle devices for too long instead of replacing them with a newer model, you can't access your old books that aren't already downloaded until you buy a new device.

For now, Sony has no issues with people redownloading PS3 games. Or PSP games onto a Vita - not sure if you can still download onto an original PSP. They'll probably jump on the Amazon revoke-download train eventually, though.

Only additional third-party DRM is listed there, not Steam's own DRM.

Until Steam starts telling me before I buy which games have their DRM and which doesn't, they belong in the same category as Sony and Microsoft.

Just as you can download old games on Steam for now. Either will pull the plug whenever they want.

Sony wouldn’t see any benefit from switching to game key discs. Nintendo introduced them to save on manufacturing costs, but game key discs wouldn’t give Sony any additional market or reduce costs any; they’d only shrink the physical market further.

You can still download games for PS3 and Vita after they stop selling them. It’s no different from how Steam no longer sells some titles it used to.

Or they’ll just stop “selling” copies in those territories and only allow short-term rentals or monthly subscription services.

Don’t jurisdictions generally offer ID cards for non-drivers that are functionally equivalent for ID purposes, you just can’t drive?

Some people don’t want to carry two devices and prefer BYOD, even if the company offers a work phone.

Wait, I thought one project = one assembly, so you would never have "types in assemblies in the same project which the current assembly depends on".

Should that be same solution instead of same project?

It seems trivially simple until you have two dependencies with conflicting exact version requirements... So I don't think you can get rid of floating versions entirely. They did add NPM-style lockfiles for PackageReference, but currently not mandatory.

The version numbers for BindingRedirects are orthogonal to the package versions. You can have multiple package versions use the same AssemblyVersion so that applications don't need to create BindingRedirects. (e.g. Newtonsoft.Json - 13.0.0, and 13.0.1 in NuGet are both 13.0.0.0 for binding redirect purposes) And .NET Core/5+ don't need BindingRedirects at all!

But just the dependency list isn't sufficient to pick a specific version, thanks to dependency ranges. If Package A depends on Package B >= 1.0, and Package B has v1.0 and v1.1 available, it will use v1.0. But if Package B suddenly unlists v1.0, then future restores will change to v1.1.

NuGet is lock-by-default for the parent package, but with the move from packages.config to <PackageReference> it's no longer lock-by-default for dependencies.

Could be worse. It’s finally gone now but I believe that my employer used VS6 as late as 2025.

It’s the opposite - if a 12-year-old thinks it’s cool it probably needs a rethink.

Amazon.jp does ship everywhere, but their international items use a separate warehouse, and sometimes items are only stocked in the domestic one(s) and are unavailable for international shipping.

“It sounded good.” https://devblogs.microsoft.com/oldnewthing/20211214-00/?p=10...

That makes sense. Thanks for explaining!