Why users cannot create Issues directly

Re:Why users cannot create Issues directly by abenga on Friday January 02, 2026 @04:46AM (#46463164)

Is there a straightforward way to have one-process-per tab in browsers without using significant amounts (O(n_tabs)) of memory?

[ Parent | on HN ]

Re:Why users cannot create Issues directly by samus on Friday January 02, 2026 @05:25AM (#46463409)

There is no justification for that IMHO. The program text only needs to be in memory once. However, each process probably has its own instance of the JS engine, together with the website's heap data and the JIT-compiled code objects. That adds up.

[ Parent | on HN ]

Re:Why users cannot create Issues directly by abenga on Friday January 02, 2026 @06:07AM (#46463645)

I'd very much like a crash in one tab not to kill other tabs. And having per tab sandboxing would be more secure, no?

[ Parent | on HN ]

Re:Why users cannot create Issues directly by samus on Friday January 02, 2026 @11:36AM (#46466496)

What do you mean? All these features are provided by process per tab.

[ Parent | on HN ]