4 ms·

Love to visit untrusted websites that feel entitled to over 4gb ram without asking.

by mwkaufma 2y ago

saagarjha 2y ago
4 GB VA space. Page tables aren’t that expensive.
- mwkaufma 2y ago
  The Memory64 proposal is for >4gb space -- and specifically to use it, not just reserve it. Learn context before commenting.
  - saagarjha 2y ago
    On the flip side, it would do you well to read this: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html. As for the actual content of your comment, pages already have access to more than 4 GB of RAM. It's actually quite easy to do just from JavaScript.
    - mwkaufma 2y ago
      Yeah, I hate that JS can do it too. Website bloat is a problem we should be fixing, not accepting. Have you tried to browse the web on a "budget laptop" lately?
      - saagarjha 2y ago
        I don't think "here is technology to let websites address more RAM" is the cause of web bloat.
- mort96 2y ago
  Isn't the whole reason they're adding 64 bit addresses to support websites which want to use over 4GiB? What other reason could there be?
  - mwkaufma 2y ago
    The website may want to, but I don't.
  - flohofwoe 2y ago
    Yes, but think of DCC applications like Figma which might run into the 4 GB restriction with large data sets, not regular websites which run a couple of WebGL demos written in C. ...also WASM is starting to become popular outside the browser where requirements might be very different from running stuff in webpages.
    - mwkaufma 2y ago
      Let figma ask me for explicit permission first, then, as opposed to making Memory64 support implicitly available.
      - flohofwoe 2y ago
        ...what's different than running any other application that uses more than 4 GB RAM on your computer, and why exactly 4 GB and not any other number? You can easily check the per-page memory footprint in Chrome's task manager and decide not to use such 'memory hogs'.
        mort96 2y ago
        Apps don't suddenly start running just from clicking a link, the relationship with websites is inherently adversarial while the relationship with apps is typically not
flohofwoe 2y ago
That's virtual address space, not physical RAM. E.g. (if my math is correct) 0.0015 percent of the available space per WASM process. I think that's acceptable ;)
- mwkaufma 2y ago
  [flagged]

Love to visit untrusted websites that feel entitled to over 4gb ram without asking.

saagarjha 2y ago

4 GB VA space. Page tables aren’t that expensive.

mwkaufma 2y ago
The Memory64 proposal is for >4gb space -- and specifically to use it, not just reserve it. Learn context before commenting.
- saagarjha 2y ago
  On the flip side, it would do you well to read this: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html. As for the actual content of your comment, pages already have access to more than 4 GB of RAM. It's actually quite easy to do just from JavaScript.
  - mwkaufma 2y ago
    Yeah, I hate that JS can do it too. Website bloat is a problem we should be fixing, not accepting. Have you tried to browse the web on a "budget laptop" lately?
    - saagarjha 2y ago
      I don't think "here is technology to let websites address more RAM" is the cause of web bloat.
mort96 2y ago
Isn't the whole reason they're adding 64 bit addresses to support websites which want to use over 4GiB? What other reason could there be?
- mwkaufma 2y ago
  The website may want to, but I don't.
- flohofwoe 2y ago
  Yes, but think of DCC applications like Figma which might run into the 4 GB restriction with large data sets, not regular websites which run a couple of WebGL demos written in C. ...also WASM is starting to become popular outside the browser where requirements might be very different from running stuff in webpages.
  - mwkaufma 2y ago
    Let figma ask me for explicit permission first, then, as opposed to making Memory64 support implicitly available.
    - flohofwoe 2y ago
      ...what's different than running any other application that uses more than 4 GB RAM on your computer, and why exactly 4 GB and not any other number? You can easily check the per-page memory footprint in Chrome's task manager and decide not to use such 'memory hogs'.
      - mort96 2y ago
        Apps don't suddenly start running just from clicking a link, the relationship with websites is inherently adversarial while the relationship with apps is typically not

flohofwoe 2y ago

That's virtual address space, not physical RAM. E.g. (if my math is correct) 0.0015 percent of the available space per WASM process. I think that's acceptable ;)

mwkaufma 2y ago
[flagged]