Are you may be comparing the pro model to the non pro model with thinking? Granted it’s a bit confusing but the pro model is 10 times more expensive and probably much larger as well.
You can activate the uv venv from anywhere just fine, just do source path_to_sandbox/.venv/bin/activate. Probably makes sense to define a shortcut for that like activate sandbox. Your conda env is also linked to a directory, it’s just a hidden one, you can also create the uv obe somewhere hidden. But I get it to some extent conda has this large prefilled envs with a lot of stuff in it already that work together. Still if you then end up needing anything else you wait ages for the install. I find conda so unbearable by now that I voluntarily switch every conda thing I have left over to uv the second I need to touch the conda env.
Because the gp comment is not about grapheneos, but its creator and could be taken as insulting (considering none of them is likely to be actually schizophrene).
That might take a few days or weeks, it seems like they put in some decent effort into it this time. From skimming the supplement I wouldn’t be suprised if the speedup is only 100x though. That’s still significant, but clearly less than they claim. For example I am not entirely convinced that 20% flops efficiency is really the upper limit or that the slicing overhead of 5x is really needed here.
But if you happen to have n=2^c, then an algorithm with logarithmic complexity only needs c time. Thats why this is usually referred to as exponential speedup in complexity theory, just like from O(2^n) to O(n). More concretely if the first algorithm needs 1024 seconds, the second one will need only 10 seconds in both cases, so I think it makes sense.
The knowledge is stored in the model, the one mentioned here is rather large, the full version needs over 700GB of disk space. Most people use compressed versions, but even those will often be 10-30GB in size.
I think you probably don’t want the application user to inherit from the superuser you may use for migrations since some migrations require a superuser.
It won’t answer questions that are not somehow related to code or computing, I usually don’t need anything else so I didn’t really test the limits of that so far.
For me it really is extremely close to 100% for timers, I barely remember it being wrong and I use it several times per day. Finding my phone via the HomePod also works pretty much every time, may be 90% for me but it doesn’t recognize my wife so for her it basically never works. The others I don’t use enough. But timers and reminders work really well for me and it’s also what I need to most from an assistant.
It’s extremely hard to root, I think that’s why it got removed from the supported robot page. As for ios, just saving the page on the Home Screen really works fine, no need for a native app here imho.
Same here, I also don’t understand why the home app is rather lacking. The light switches in the control center are okay, but that quickly becomes too full. I mostly use voice commands to manage my lights and third party apps like the one from Eve for other accessories.
I agree, probably the biggest point Digitalocean is lacking. I think the only workaround is creating several projects? But that probably becomes annoying and hard to manage quite easily if you want a lot of separation.
Many of my friends in Germany have Telegram as well and I think that it’s mainly because it has by far the best multi device (esp. Desktop / Notebook) UX. Switching devices with Telegram and using it on several devices concurrently has always been super easy.
Hetzner (German data center provider) claims to achieve a PUE of 1.1 (https://www.golem.de/news/besuch-im-rechenzentrum-so-betreib...), admittedly their cloud offerings are quite limited but I think they are expanding on that front. So it doesn’t seem like only hyper scalers would fall into that limit.
The short answer is very likely no, at least not without any other major breakthroughs. The reason why Viterbi is fast is because the underlying probabilistic model is rather simple, which does not hold for quantum situations in general.
While that might not fit your needs I map unions to Postgres with an enum encoding the type and then adding constraints on which additional columns must be set (and also must not be set) depending on the type. For your example the enum might be leaf or tree and then if it’s of type tree you have non nullable left_child and right_child columns and if it’s a leaf those must be null, and then you might have a value column that is non null in both cases or only for leaves.