@Efi @Fuego @staticsafe why is it so difficult to write a web browser that doesn't eat half a computer's fucking ram tbh

@literallyfenic @Efi @staticsafe@mastodon.zombocloud.com because when you do that you get a browser that is comically easy to exploit

@Fuego @Efi @staticsafe gah there's gotta be SOME way to balance that

@staticsafe @Efi @Fuego like, if you could do some combination of limiting unnecessary capabilities + shaving off some less important security concerns and running stuff exclusively from certain trusted soruces, it might make a faster electron-like app at least?? idk i'm not good at this stuff

@literallyfenic @staticsafe@mastodon.zombocloud.com @Efi capabilities has nothing to do iwth it - I'll take the capabilities I need once I have arbitrary read / write.

And the way they CAN limit it in useful ways involves sandboxing which is very expensive ram wise.

@Fuego @staticsafe @Efi ...okay well, here's a question then, why is sandboxing so ram-heavy

@literallyfenic @staticsafe@mastodon.zombocloud.com @Efi you're literally creating a process per tab that runs at a limited execution level, that communicates over IPC to a manager that is keeping state of all the tabs and performing all the syscalls then passing the info back to the lower priv processes.... its expensive.

Like this is pretty well known... you're either expensive or you're owned. Choose one.