Live data from Hacker News

Ōryōki Web Browser

oryoki.io

121–130 of 181 posts

Re: Ōryōki Web Browser

#121
post #54

Earlier quoted context omitted.

Seems like the market is moving to almost all second-tier browsers (e.g. Opera) building from Chromium. I think this is a positive development as it should strengthen the underlying code if more people use it as a standard and then innovate UI, tools, services and so forth on top of it. Similar to what you see with the custom Android flavors/knock offs/whatever you want to call them in China.

it also seems that browser built on chromium faces a lot of resistance, because "then I'd just use chromium" I myself jumped from Opera when they rewrote to blink

I can think of many reasons why folks would want to use a custom browser built on top of Chromium rather than Chrome. Take Opera for example - Adblock and VPN are two services that can live more efficiently deeper in the core versus the extension layer where they are on Chrome. And these are two services that Google does not want to promote any more than they have to in order not to shed users. Browser competition is great for the market, the last thing we want is to end up in an IE6 type situation (and yes it can happen to anybody, even Google).

Re: Ōryōki Web Browser

#122
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/

Conkeror (n.b. not Konkeror) is quite good too.

Re: Ōryōki Web Browser

#124

Earlier quoted context omitted.

This is a good example of what is right with HN. Technical people expressing their technical demands w/r/t a technical project. If you want people to ooh and ahh over a project and keep quiet about its faults, show it your relatives.

You don't get it. Someone built an experiment in minimalistic UI design . "Technical people" started a massive pile-on, declaring "this is stupid, this doesn't have a minimalistic codebase at all." That's not a technical demand , and it's not identifying a product's faults. That's a demand that this project have an entirely different purpose . Personally, I use `chromium --kiosk-mode` as my everyday browser, and this…

You don´t get it.

Labelling dark skinned electron as experimental browser is bs.

Re: Ōryōki Web Browser

#125
post #14
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.

I understand your point, but there is inefficient vs. efficient use of resources. You could say it's ok to package a toothpick in a shoebox because cargo space is meant to be consumed.

When the ASCII text of a webpage is measured in tens of kilobytes, and the RAM in hundreds of megabytes, something is wrong.

Re: Ōryōki Web Browser

#126
post #82
post #17

Earlier quoted context omitted.

I agree completely. Taking buttons off of the GUI and using different hotkeys doesn't make a better web browser. You just end up with a browser for hipsters.

A lot of the hate here comes from the fact that there are people who are being creative, and you aren't. It's easy to shut people down...try to help them, instead. It's an experiment, made public. What's the purpose of shitting on it?

> It's an experiment, made public. What's the purpose of shitting on it?

Providing data.

Re: Ōryōki Web Browser

#127

Earlier quoted context omitted.

Do you know of any independent rendering engines? That's something I'd truly be interested in seeing. It seems like a herculean task to undertake. Edit: Thanks very much for the links. This will be a lot of fun testing out. Just responding here to avoid triggering the anti-flamewar protection.

Depends on what you mean by independent. If you just mean not any of the big three and their derivatives, you've got Servo[0], although that's still a herculean effort with direct support from Mozilla in terms of paying people to work on it. On the other end of the spectrum, you've got things like Dillo[1], which don't support much modern HTML/CSS/scripting, but do seem to get on by with far less effort. [0] https://…

These days it seems most pages are more JS and CSS than HTML...

Re: Ōryōki Web Browser

#128
post #90

Earlier quoted context omitted.

Blink is a fork of WebKit and is still largely the same.

Depends on what you are counting as the "same". Edge put together a really great visualization of the API surface of all the browsers. - https://developer.microsoft.com/en-us/microsoft-edge/platfor... The API surface (and bug surface) is actually pretty different these days. Internally Blink and WebKit are also diverging reasonably rapidly. As a specific example here is the project to re-architect how blink does it's…

More and more it feels that corporations have discovered that with FOSS, those that do the work get to define the standard. And thus they throw manhours upon manhours of churn at whatever market segment they hope to control.

Re: Ōryōki Web Browser

#129
post #54
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/

Seems like the market is moving to almost all second-tier browsers (e.g. Opera) building from Chromium. I think this is a positive development as it should strengthen the underlying code if more people use it as a standard and then innovate UI, tools, services and so forth on top of it. Similar to what you see with the custom Android flavors/knock offs/whatever you want to call them in China.

How quickly we forget the IE years...

Re: Ōryōki Web Browser

#130
post #65
post #24

Earlier quoted context omitted.

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

How much of the overhead is actual overhead though? Operating systems know better than to store multiple identical copies of the same shared library in memory, for example. And it's not like the process-per-tab approach has no benefits - you use more RAM to get increased reliability and security in return.

Chrome specifically runs these processes as duplicate services at the OS level so that when one fails in memory the rest don't.

http://blog.chromium.org/2008/09/google-chrome-memory-usage-...

Post reply on HN