There's a difference between carrying ten pounds small distances for short durations, and carrying an extra two pounds over twenty hours of travel, across multiple connecting international flights in a single day. It's also not just an extra two pounds, it's an additional proprietary power cord, bulk, more mass moving in and out under an airliner seat, it all adds up. Especially when you're sleep deprived and physically exhausted.
Any amount of weight is annoying after that long, but if the extra laptop weight is reduced to 10% of your 25 pound bag then it's even less able to be the deciding factor between "portable" and "barely portable".
Is the CUDA compat layer AMD has that transparently compiled existing CUDA just fine insufficient somehow or buggy somehow? Or are you just stuck in the mindshare game and haven’t reevaluate whether the AMD situation has changed this year?
I haven't checkout out AMD's transparency layer and know nothing about it. I tried to get vkFFT working in addition to cuFFT for a specific computation, but can't get it working right; crickets on the GH issue I posted.
I use Vulkan for graphics, but Vulkan compute is a mess.
I'm not in a mindshare, and this isn't a political thing. I am just trying to get the job done, and have observed that no alternative has stepped up to nvidia's CUDA from a usability perspective.
> have observed that no alternative has stepped up to nvidia's CUDA from a usability perspective.
I’m saying this is a mindshare thing if you haven’t evaluated ROCm / HIP. HIPify can convert CUDA source to HIP automatically and HIP is very similar syntax to CUDA.
> Unless you have an Intel Arc iGPU, Intel Arc B50/B60, or fancy server GPU, you won't have SR-IOV on your system, and that means you have to pass the entire GPU into the VM.
This is changing, specifically on QEMU with virtio-gpu, virgl, and Venus.
Virgl exposes a virtualized GPU in the guest that serializes OpenGL commands and sends them to the host for rendering. Venus is similar, but exposes Vulkan in the guest. Both of these work without dedicating the host GPU to the guest, it gives mediated access to the GPU without any specific hardware.
There's also another path known as vDRM/host native context that proxies the direct rendering manager (DRM) uAPI from the guest to the host over virtio-gpu, which allows the guest to use the native mesa driver for lower overhead compared to virgl/Venus. This does, however, require a small amount of code to support per driver in virglrenderer. There are patches that have been on the QEMU mailing list to add this since earlier this year, while crosvm already supports it.
To add to this, while I haven’t used it yet myself (busy with too many other projects), this gist has the clearest and most up to date instructions on setting up QEMU with virglrenderer that I’ve found so far, with discussion on current issues: https://gist.github.com/peppergrayxyz/fdc9042760273d137dddd3...
Why do you have to install Windows? You could put bazzite or any other distro of your choosing on this machine and have a similar experience to the official Steam Machine.
> Oddly, tameness has also long been associated with traits such as a shorter face, a smaller head, floppy ears and white patches on fur—a pattern that Charles Darwin noted in the 1800s.
Hmm, so evolutionary pressure of existing around humans makes animals cuter.
I believe the main biological lever is retaining juvenile features as adults, physically as well as mentally (like with dogs). What we see as cute is an honest signal that they are more child-like: less aggressive, more trusting and pro-social.
I also think that this is the central cause of a wide variety of domestic/cute adaptations. There are too many separate features to believe that raccoons and dogs and cats and a dozen other species all select for these same elements independently.
I no longer have the book on hand, but read a few months ago that this correlation between juvenile traits and domestication was one of the main theses of Barrett's "Supernormal Stimuli" in Chapter 4. She cited a few studies of fox domestication [1], [2] and other works to support these theories.
My guess: possibly co-evolution. The article subsequently describes the genetics behind things becoming cute - which would have been completely benign to our ancestors (the core of your question). However, those of our ancestors who completed domestication of these animals (by random chance) would have enjoyed more protection from predators, rodents, etc. Those of our ancestors who attempted to domesticate things without the mutations might have had bad companions at best, and would have been predated at worst. This would have provided evolutionary pressure to adopt animals that were showing early signs of domestication. What we call "cute" is merely "likely to cooperate with us."
Since humans associate cuteness with large eyes and small body size, nocturnal / twilight animals, like raccoons, sugar gliders, cats, squirrels, etc have a larger chance to be domesticated as pets.
Daytime, larger animals (e.g. sheep, goats, or even rabbits) have a larger chance to be domesticated as food.
Experiment in taming foxes that relied on a single principle of selecting animals that react to humans with least fear and aggression resulted also in those morphological changes. I think it's more about selecting animals that retain youthful curiosity and other traits into their adult life. Youthful morphological features just tag along.
Perhaps a combination of adaptableness, small size, prodigious reproduction, and cuteness saved some species from being wiped out whereas other species didn't fare so well once humans arrived and transformed their territory. Adapt to urban encroachment or face extinction.
It would make sense, but Apple has large amounts of disdain for people having fun with their products. This evidenced by the large amounts of engineering they've put into very large, capable, and efficient GPUs, only to squander them on rendering web pages and liquid glass.
They released Apple Vision Pro with no ability to play popular PC games on it.
As far as I understand, there's actually an intermediate driver on macOS that implements Vulkan on top of Metal, similar to how Proton implements Direct3D on top of Vulkan.
The available low-level API is Metal, and the existing software stack is written for Vulkan, so it makes more sense to implement Vulkan than to write a new Metal backend.
It's not at all about looks, it's about a different kind of handling, for off road, that's mutually exclusive with on road handling.
Yes, some people choose to emulate off road appearances, such as with fake bead locks and then only ever drive their vehicle on road. That doesn't discount the fact that there are a great many explicit choices you can make in designing and building a vehicle that sacrifice on road performance for off road performance.
What current mass production EVs use hub motors? It seems a lot more sensible to have the motors inboard, mounted to the chassis, and drive the wheel(s) with axle shafts. It seems in my searching this is how nearly all EVs are currently designed and produced.
reply