eeegnu

I've been trying with little avail to get a Windows 10 VM running on Windows 10 which isn't graphically jittery. I plan to use this VM to download random games without having to worry about potential malware. I've tried VBox, and native Hyper-V Manager, with the latter being slightly better, but still far from native performance. I expect some performance degradation, but I don't have a good grasp on what should be attainable. I have a Ryzen 5800X3D, and a decently powerful GPU, but it runs like the hardware is 15 years old. Looking for advice on what I can do here; I've tried following pretty much every guide on the first page of Google, which all recommend the same things: enable virtualization, increase #virtual cpus, decrease #virtual cpus, increase memory, change memory to fixed instead of dynamic, get rid of bloatware, defragment, etc.

I'm struggling to find a great post I saw here a few months (years) back on what I think was a very technical dive into the exact details of attaining the ability to compile complex things by writing code that incrementally compiles the previous code. If anyone knows what this was, a link would be appreciated.

Just now I was trying to spell "manipulable" and I typed in "manipuble". It gave three options to fix this: "manipulee", "maniple", and "manipulees". But if you just try to google "manipuble", it will inform you that it's instead searching for "manipulable". I can't think of a single time when searching for a misspelled word didn't yield the correct spelling as the first suggested result, but it's almost a daily occurrence for chromes typo suggestions to avoid suggesting the correct, seemingly nearby, word. This feels like a newish occurrence too, I don't remember ever having this much issue with it years ago.

I was browsing through vercels docs when I noticed that password protecting [1] a project (so that anyone previewing a deployment needs a password) is an optional add on feature for (an insane?) $150 per month. A pro plan is $20 per month per member [2] and it just makes me curious who this works out as desirable for? For small teams paying an extra $1800 per year for a feature that's maybe a few hours of dev time to implement doesn't seem worth it. Even for large teams where a feature leak might be disastrous, they might be concerned enough to want their own implementation. Is there something technical I'm missing here that would be difficult (or impossible) to reproduce? I'm mostly curious because I'd think the economics of it would lean toward a smaller price tag; as for most teams this probably means ~doubling their costs if they wanted to use it.

[1]: https://vercel.com/docs/concepts/projects/overview#password-protection

[2]: https://vercel.com/pricing

I'm working on a project and i'm at a step where there are several options for accomplishing the task, any of them working will do. And because I really don't care which of them I use, I try to find which of them will take the least effort/time to get working. But i've found myself trapped in a cycle: Every time I dig a little deeper into one solution, I find something that looks like it'd be unpleasant to deal with and I switch over to inspecting a different solution (e.g. browsing through a different library.) I've looped a few times now between three reasonable routes, getting a little deeper in each one each time. Does anyone else ever get caught in this kind of cycle?

I was creating a bucket on GCP and noticed what I thought was an odd restriction[0]:

> Bucket names cannot begin with the "goog" prefix.

> Bucket names cannot contain "google" or close misspellings, such as "g00gle".

I'm mostly just curious about the motivation behind these restrictions. My guess is that it's to avoid buckets that make it seem like they're owned by google, but there doesn't seem to be equivalent restrictions on azure[1] or aws[2] (they do disallow the prefix "xn--" and the suffix "-s3alias", but these seem functional.) Is there some other reasoning?

[0] https://cloud.google.com/storage/docs/naming-buckets

[1] https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

[2] https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html