Out of curiosity I asked chatgpt what the malware does, but erased some parts of the base64 encoded string. It still gave the same answer as the blog. I take that as a strong indication that this script is in its training set.
The popular Bumpalo only returns references with the lifetime of the allocator. Not sure what you mean by manage your own garbage, an arena allocator deallocates everything when it goes out of scope. You definitely can't reference uninitialized parts of an arena.
Entirely untrue. Download git, run make and you'll get a 19MB `git` binary along with a whole lot of other 19MB binaries. Running `cargo build` produces a 3.8MB binary.
And that's still comparing apples to oranges, because git is compiled with full optimizations. Running `cargo build --release` produces a 462KB binary.
Even if I'm comparing to my system's git installation, that's still 3.9MB, and that's with all the debug info stripped.
Yes rust (like C++) tends to produce larger binaries than C, but lets be real here: The reason Zed has a bloated binary is the ~2000 rust packages that comprise it.
You know what does have theming? Win32, GTK and QT. GTK even uses CSS for it.
And unlike electron apps, when you change how a button looks in your GTK theme it affects all GTK apps rather than just the single electron app.
> Nonsense. Obsidian is sitting at 115 MB right now, zero CPU.
I just downloaded obsidian for the first time and launching it spawns 8(!) processes using a total of 827.3 MB of RAM. That's at the launch screen, before it's doing anything.
Of course it's using no CPU when idle. That's basically the bare minimum bar for any application. It's well known that javascript is at least an order of magnitude slower than C. That's where it's wasting CPU, not when it's idle.
> Define slow.
Well to start off with, I can count the seconds obsidian takes to start up. Most native apps I have installed (other than browsers) start faster than I can reasonably react.
> It's well known that javascript is at least an order of magnitude slower than C
If your base is base-2, yes. (It is well-understood that when you don't have your thumb on the scale—e.g. selecting, whether deliberately or carelessly, poor/pathological code to benchmark—that the expected slowdown factor of executing on a mainstream JS engine instead of AOT is in the neighborhood of 2x to 4x. Of course browsers JIT instead of AOT out of necessity—a constraint that doesn't apply to programs loaded from disk.)
I get where you're coming from, and I do think game devs should put more effort into supporting lower-end hardware.
That said, bg3 does run on 10-year old hardware. The minimum requirements lists a gtx 970, released 2014. Which, despite its age, is still 6x faster than your integrated graphics.
When was the last time you played? They've been making continuous performance improvements and act 3 hasn't chugged on my PC for a long time. Even steam deck seems to get a steady 30fps.
