91–100 of 181 posts
This project is solving the wrong problem. It's not the interfaces of web browsers that suck, it's the gigabytes of RAM they consume.
No. This project is solving a different problem. Let it be.
This project is solving the wrong problem. It's not the interfaces of web browsers that suck, it's the gigabytes of RAM they consume.
To be fair, the biggest offender in all this IS javascript in webpages. Though even more Javascript in the browser UI isn't going to solve the Javascript problem when it comes to performances. Anybody can shift+Esc on Chrome and see how Javascript heavy pages consume a shocking amount of Memory.
While crazy site do crazy things with JS and have crazy bad user experiences (TMZ.com makes 700+ requests and takes over 90seconds to load), 98 MB of ram for a HN tab is ridiculous. This has very little to do with JS.
For anyone interested, here are some web browsers that are actually minimalist and not just reskins of chromium: http://surf.suckless.org/ https://fanglingsu.github.io/vimb/ http://www.uzbl.org/
For anyone interested, here are some web browsers that are actually lightweight (if not html5-compliant) and not webkit-based: http://www.dillo.org/ http://www.netsurf-browser.org/
This project is solving the wrong problem. It's not the interfaces of web browsers that suck, it's the gigabytes of RAM they consume.
Sometimes it's discouraging to think about how RAM requirements keep going up. The laptop I bought in 1999 had 64 MB of RAM, and that was enough for a comfortable multitasking system (dual-booting between Windows 9x and Linux with a GUI) for about two years. Now, we have this, paraphrased from the 2012 novel _Off to Be the Wizard_ by Scott Meyer. Phillip, a time traveler from 1984, asks, "What on earth can a person d…
This page is a good example of what's wrong with HN. Someone publishes their open source experiment in minimal browser UI design, and everyone shits on it for not being a built-from-scratch web browser with low memory usage.
This project is solving the wrong problem. It's not the interfaces of web browsers that suck, it's the gigabytes of RAM they consume.
RAM is meant to be consumed. If your browser is using 50MB of RAM and has to swap every background tab to disk then you're not utilizing the resources of your computer, and getting a crappy user experience as a bonus.
This project is solving the wrong problem. It's not the interfaces of web browsers that suck, it's the gigabytes of RAM they consume.
Something is seriously wrong, and it has nothing to do with client side JS, or huge retina images, or CSS animations and rendering jank.
This page is a good example of what's wrong with HN. Someone publishes their open source experiment in minimal browser UI design, and everyone shits on it for not being a built-from-scratch web browser with low memory usage.
This page is a good example of what's wrong with HN. Someone publishes their open source experiment in minimal browser UI design, and everyone shits on it for not being a built-from-scratch web browser with low memory usage.
This page is a good example of what's wrong with HN. Someone publishes their open source experiment in minimal browser UI design, and everyone shits on it for not being a built-from-scratch web browser with low memory usage.
Why should this be wrong? People can be who they want to be. If something is cool it's appreciated, if it's not, it's been shit on. That's life, deal with it. Not everyone is made of porcelain. Some are able to deal with critisism even if it's not delivered like it's taught in management classes.