Ōryōki Web Browser • Hacker News Board

Re: Ōryōki Web Browser

#21

Post by JustSomeNobody » Wed, Jun 29, 2016, 7:17 PM UTC

dmit wrote: post #14

jfe wrote: post #7

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.

>RAM is meant to be consumed.

By users, not developers.

Edit: I know, I know, I know... But you all get my point.

Re: Ōryōki Web Browser

#22

Post by amelius » Wed, Jun 29, 2016, 7:17 PM UTC

jfe wrote: post #7

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.

I'm afraid that in order to solve those problems, the specs from W3C need to be radically simplified and improved.

Re: Ōryōki Web Browser

#23

Post by swalsh » Wed, Jun 29, 2016, 7:18 PM UTC

I fully support innovation in terms of a new web browser... but this isn't really what I'd like to see. I feel like the web browser should be more of an OS than what it is today. Why does the language attribute in the script tag only support javascript? Wouldn't it be rad if I could write C#, and not have to transpile it... wouldn't it be rad if browsers could add more language support automatically (with your permission first). So if you go to hipster.io and they've decided to develop their whole client side in lisp, but you don't have support yet it goes to mozillas module repository and downloads the plugin? Wouldn't it be rad if jquery was installed as a module, and you only downloaded it once for ALL sites, and you only redownload it if the site's version is different/customized...

Re: Ōryōki Web Browser

#24

Post by bduerst » Wed, Jun 29, 2016, 7:18 PM UTC

jhardcastle wrote: post #15

jfe wrote: post #7

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.

Don't you think that removing all the extensions, bookmark bars, and extraneous UI cruft will make this browser consume a lot less RAM? Seems logical to me.

You still have the duplicated processes across the different tabs to contend with. That's the real RAM killer.

Re: Ōryōki Web Browser

#25

Post by caffeinewriter » Wed, Jun 29, 2016, 7:18 PM UTC

pen2l wrote: post #3

Seems similar to Uzbl (a minimalist browser that was receiving a lot of attention a few years back): https://en.wikipedia.org/wiki/Uzbl

Or even Min[0] which was on here a few months back.

  [0]: https://news.ycombinator.com/item?id=11484770

Re: Ōryōki Web Browser

#26

Post by brianwawok » Wed, Jun 29, 2016, 7:19 PM UTC

jfe wrote: post #7

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.

Why would I not want my browser to use RAM?

What else with my 16 or 32GB of ram am I going to do when I surf? I would happily give double the current gen ram for better performance.

Re: Ōryōki Web Browser

#27

Post by dijit » Wed, Jun 29, 2016, 7:19 PM UTC

dmit wrote: post #14

jfe wrote: post #7

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.

Never assume your application is the only application running on my machine. And never assume I will be running only one version of your application.

My girlfriend who is a non-power user regularly has 2 browsers open and her laptop is swapping constantly with it's 8G of ram.

Re: Ōryōki Web Browser

#28

Post by exDM69 » Wed, Jun 29, 2016, 7:19 PM UTC

The typical web browser UI is a terrible waste of pixels. It might be a requirement for non-techies but no-one surely clicks the back button or drags the scroll bar, at least no power user does.

I personally use Firefox + vimperator with menu bar, address bar and scroll bars disabled. A single line status bar has all the info I need.

I've also dabbled with some of the "micro browsers" but none was satisfactory without a lot of trouble configuring proxies, etc.

For the future, I am hoping that someone will put together a Servo based micro browser with a keyboard oriented user interface.

Re: Ōryōki Web Browser

#29

Post by dijit » Wed, Jun 29, 2016, 7:20 PM UTC

brianwawok wrote: post #26

jfe wrote: post #7

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.

Why would I not want my browser to use RAM? What else with my 16 or 32GB of ram am I going to do when I surf? I would happily give double the current gen ram for better performance.

Then that should be configurable. Personally having 8G of ram dedicated to my browser limits the possibilities of the machine I have.

(remembering most Macs come default with 8G of ram)

Re: Ōryōki Web Browser

#30

Post by [deleted] » Wed, Jun 29, 2016, 7:20 PM UTC

dmit wrote: post #14

jfe wrote: post #7

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.

[deleted]