but, if it's trying to respond in a natural way, with interruptions in both directions, it may still be a good idea. if there's a delay between you stopping and it starting talking, it feels weird
(you might be able to fake some of that on the client, but then you need a thicker client)
i think it's a mix of conservative/religious lobbying (getting them ire from the government), and chargebacks by embarrassed customers with post-nut clarity being common
i think the thing that got me was that people wrote articles comparing this thing to a laptop GPU, and i didn't read far enough to notice. normally, people compare desktop stuff to desktop stuff, and laptop stuff to laptop stuff
i haven't bought a laptop gpu since ~2008. from what i remember, they used to at least put "mobility" in the name, or throw and 'm' after the number, or something
a quick search told me that this thing's GPU (8060s) is comparable to a 4070
from what i can tell, a 4070 alone is ~$750. this thing is apparently $799 for the CPU+GPU+RAM+motherboard all soldered together ($300 more for case+PSU+SSD)
if the CPU+RAM+motherboard are costing me $50, i don't really care if i have to throw them out along with the GPU
would have been cool to know about this a month ago
i just built a mini ITX gaming PC for a friend, and this one looks pretty good for quality/$. good enough that i wouldn't be surprised if these get snapped up and re-sold for more than the sticker price
i think it makes more sense to think of it as a high-end console, given that basically everything is soldered, though
you can avoid resizing and moving the pools if you allocate massive pools up front. most OSs let you overcommit memory, and most programs using memory pools only have a handful of them
(on windows, you'd need to handle this with VirtualAlloc. osx and linux let you overcommit with malloc, and handle it with a copy-on-write page fault handler)
vulkan doesn't have global state, and the error handling is better
but it's not batteries-included, and that's often to be a deciding factor at small scales
i think if you're going to dabble in engine dev, you pick which one you want depending on which part of the engine you find interesting. if you want to make a game, you pick up unity or godot or something
but, if it's trying to respond in a natural way, with interruptions in both directions, it may still be a good idea. if there's a delay between you stopping and it starting talking, it feels weird
(you might be able to fake some of that on the client, but then you need a thicker client)