UMAs aren't made for speed, but for power savings. You are ignoring the fact that a discrete GPU accesses VRAM and caches at much higher bandwidths (and power) than an iGPU does RAM. Shared mem also comes at the cost of keeping it coherent between CPU/GPU. So you can't just look at one part of the system and then claim that UMAs must be faster because there are no data transfers.
And by the way, even on UMAs, the iGPU can still have a dedicated segment of memory not readable by the CPU. Therefore UMA does not imply there won't be data transfers.
This is really not the right comparison to make. An OS will use memory liberally. Give it more and it'll use more. Give it less and it'll swap to disk. So the real question is how long a given workload takes to complete, or whether you can multi-task without shitting out to/from disk every time you switch windows. "My OS uses X amount of RAM" is an entirely meaningless and irrelevant statement.
> the real question is how long a given workload takes to complete
The memory eaters most people are complaining about are not workloads, but shitty communication apps that keep all those cat pictures from the last 4 months uncompressed in ram...
This is exactly it. The people who release stuff under the GPL do so precisely because they want the software and derivatives to stay free. The software has strings attached; the AI removes them. What's so hard to understand here?
Carmack's argument makes no sense, but I guess it has "Carmack" in it so obviously it must be on the front page of HN.
Is Eglot on par with emacs-lsp for C++? Specifically thinking about pointing it to a compile_commands.json and all of the usual C++ nonsense required for code navigation and autocomplete.
Pretty much yes. I switched to eglot from emacs-lsp because of some frequent random errors ("document not added") that required me to frequently kill clangd; might be a PEBCAK problem, but went away with eglot.
The UX will be different and is a matter of preference. The performance depends solely on your LSP. So long as your LSP is the same and configured the same, it will give you the same results for navigation/completion.
I use it that way. It requires less setup than lsp-mode. Just try it – add `:disabled t` to your use-package lsp-mode, restart emacs and type `M-x eglot` in a C++ buffer.
> Note that you'll need to have an AI generate assets or something since you can't just reuse textures and models.
As far as I know, you can as long as you own a copy of the original. In other words, you can't redistribute the assets, but you can distribute the code that works with them. This is literally how every free/libre game remake works. The copyright of your new, from-scratch code, is in no way linked to that of the assets.
And by the way, even on UMAs, the iGPU can still have a dedicated segment of memory not readable by the CPU. Therefore UMA does not imply there won't be data transfers.
reply