Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ōryōki Web Browser

oryoki.io

Post reply on HN
Print view View original

41–50 of 181 posts

Re: Ōryōki Web Browser

#41

Post by overcast »

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.

Sure RAM is meant to be used, but not when the browser just consumes it forever, until it begins grinding to a halt. What could a browser POSSIBLY be doing with 4-500MB of RAM PER TAB? It's a huge problem, and extensions like The Great Suspender should not have to even exist.

Re: Ōryōki Web Browser

#42

Post by hasenj »

Maybe I'm ignorant but having Electron on top of Chromium sounds somewhat redundant to me. Don't they both have the same core more or less? I mean V8 and Blink?

Re: Ōryōki Web Browser

#43

Post by badminton1 »

Making a web browser is hard. You will be dealing with sensitive information, your credentials, etc. Security-wise it is very hard to produce a sandboxed environment. Chromium might provide this to some extent but building on top of it might not magically preserve the same level of security.

Re: Ōryōki Web Browser

#45

Post by amaks »

bpicolo wrote: post #33
wz1000 wrote: post #19

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/

I mean, they all use webkit, so not really that much different from using chromium.

Chromium doesn't use webkit, it uses Blink.

Re: Ōryōki Web Browser

#46

Post by vertex-four »

wz1000 wrote: post #19

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/

All of those are WebKit-based, which was Chromium's rendering engine until recently. The rest of Chromium is primarily UI and network code, along with their sandboxing system and extensions - WebKit's "ports" have their own implementation of said network code tying into the framework that they're porting to (GTK+ or Qt, usually), and all three browsers you list use the WebKitGTK+ port.

uzbl, the one I've used the most, primarily consists of a pile of code to map callbacks to a protocol on stdin/stdout, and a handful of example scripts to communicate over that protocol - it's certainly no more "from scratch" or smaller than any other WebKit-based browser.

I expect that the other two similarly focus on UI code rather than pointlessly fiddling with WebKitGTK+'s internals - how are they not just skins (albeit of WebKitGTK+, not Chromium) as well?

Re: Ōryōki Web Browser

#47

Post by scrollaway »

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.

Don't assume everybody uses their computer like you do and only runs one browser maximized on their only monitor connected to their powerhouse of a computer equipped with a last-gen CPU and 64 gigabytes of ram.

For example, I sometimes play very resource-hungry games and like to have a youtube video on my second monitor while I play. But that's not possible on my gaming PC, so I have to youtube-dl the video first and run it in vlc instead.

Re: Ōryōki Web Browser

#49

Post by nornagon »

benbenolson wrote: post #38
bpicolo wrote: post #33

Earlier quoted context omitted.

I mean, they all use webkit, so not really that much different from using chromium.

It's true that they use webkit (which is certainly not ideally minimalist), but even that is much lighter than using Chromium.

Not really, the Chromium content/ layer is pretty much stuff that every browser implementor using blink (or previously, WebKit) would want. See http://www.chromium.org/developers/content-module for more info.

Re: Ōryōki Web Browser

#50

Post by Fogest »

quantumtremor wrote: post #18

For Firefox users, this can all be done with Firefox and custom browser CSS (Vimperator helps), which offers significantly more control (without having to rewrite the core code). Screenshots: http://imgur.com/a/qDGP2 CSS base (I've made a few modifications): http://twily.info/firefox/stylish/firefox-css#view

Do you own twily? That is an interesting file explorer style thing on the webpage.
Post reply on HN