nerverwin

web slop won the desktop war and we let it happen, and now the terms "speed" and "privacy" are basically dead. claude spent 20k on an ai agent swarm to write a c compiler in rust. but their desktop app is still electron wrapper. ironically, openai's codex desktop app is built on electron too isnt it crazy that we have ai models that can write highly optimized c and rust, yet companies like openai and anthropic still wrap their desktop agents in headless browsers a blank electron app starts at around 130mb of disk space and 50mb of ram. an equivalent win32 c++ app is under 1mb. we traded storage density for so-called developer convenience electron xss opens a reverse shell. if a lazy developer leaves nodeintegration enabled, a standard xss payload can require the child_process module and execute native os commands. web devs should not write desktop security boundaries electron's security model is so fragile that cve-2025-55305 revealed an asar integrity bypass and could modify the application resources to completely bypass integrity validation before the app even loads the v8 engine has to read your electron js code to run it, which means anyone with a debugger can dump your unencrypted application state. you cannot hide api keys in client side javascript rust developers are not wrong when they lecture you about memory safety and security flaws when you tweet a vs code screenshot there is a total collapse of engineering standards. we just accept 500ms button delays because nobody remembers what 16ms delay feels like anymore native developers use metal and directx to animate millions of polygons at 500+fps. frontend developers use electron to animate a hamburger menu at 60fps and it costs 500mb of ram we killed memory safety because a design agency wanted a custom cubic bezier transition on a modal window if you're blaming ai for expensive ram, you've got to see electron, we could've easily used it on fast native user interfaces taking negligible amount of ram (idk about swift, but win32, gtk yes) compared to what webslop takes from us sources: 1. blogs: dbreunig.com/2026/02/21/why… 2. electron's security and vulnerabilities: blog.doyensec.com/2017/08/03/ele… nvd.nist.gov/vuln/detail/CV… nvd.nist.gov/vuln/detail/CV…

#UnrealEngine This line of reasoning is fundamentally flawed. The issue is not project side #gamedevs, it is the engine UE5, at its core, that carries an unfeasible performance target for games. It's whole #rendering pipeline is made for film in mind. Where high end PCs are commonly used and performance is not really concern. Here a demonstration of the exact same project running 2.35x faster than the UE5 version. The only difference one is using #DDGI and UE5 #Lumen, while both being #Raytraced GI systems. Strong reasons of #UE5 titles running poorly is simply because of the engine tech behind it. [Image 1] Vite DDGI (Hardware RT) 107.10 fps 233.2% [Image 2] UE 5.7.3 Lumen Hardware 45.92 fps 100% [Image 3] UE 5.7.3 Lumen Software 54.01 fps 117.6% [Image 4] UE 5.7.3 No Lumen 77.82 fps 169.5% *Lumen no reflections, no vsm, no nanite is on, exact same settings. These tests were made on a RX 6700 which represents closely #PS5 GPU This is only using Lumen, whenever you add VSM, Nanite, TSR you simply need to force down actual res to figures as low as 720p-900p on console. There is sadly no fix to this, as fixing the engine performance would imply removing entire systems such as Lumen, #Nanite, #Chaos, etc (essentially the entire UE5 stack). And yes, this would be needed even for projects that do not use these features at all given that they all carry a severe overhead from the engine source. That's why the ue 5.7 non lumen scene is so far behind in performance compared to the Raytraced one in Vite. The results from this post are only about GPU, as for CPU check: x.com/theredpix/stat… Which showcases how ue5 is 4x times slower on #CPU side. The industry needs to move away from #UE5 as it puts titles at a severe tech disadvantage, whether that means adopting #UE4 or investing in proprietary engines. Join : discord.gg/n9zQrYFhMb Support Vite: ko-fi.com/vitestudio #screenshotsaturday