Live data from Hacker News

Ōryōki Web Browser

oryoki.io

161–170 of 181 posts

Re: Ōryōki Web Browser

#161
post #160
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'm amazed no-one has mentioned "dwb" in this thread. Yet another webkit-based browser with vi-like keybindings, but also an extension manager and plugins such as adblock and requestpolicy. Entirely keyboard-driven. http://portix.bitbucket.org/dwb/

Looks interesting! I'll have to give it a go today, thanks :)

Re: Ōryōki Web Browser

#162
post #14

Earlier quoted context omitted.

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 wonder if part of the solution is smarter caching at the OS level. Do all modern operating systems give the application a way to tell the OS, "This chunk of memory is a cache, so free it if it's needed for something else"? Of course, when the OS frees that memory, the app would need to know about that, so it can re-fetch or re-compute that cached data the next time it's needed.

They almost all do, yes. Android offers volatile ranges, OS X offers purgable pages, Windows offers MEM_RESET/MEM_RESET_UNDO. To my knowledge Linux is the only exception, because last time I checked they haven't merged Android's patches to enable the feature.

Re: Ōryōki Web Browser

#163
post #66
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/

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/

I just love Dillo!

On sites that require Javascript, it is useless, of course, and even moderately fancy CSS layouts look ... interesting in it. (OTOH, no Javascript means that it practically has a builtin adblocker.)

But for sites where that is not a problem, it is incredibly fast, plus one can have dozens of tabs open, and it will rarely if ever use more than 100 MB of RAM. For browsing documentation, it usually works perfectly well.

Re: Ōryōki Web Browser

#164
post #89

Earlier quoted context omitted.

For anyone interested, here are some web browsers that are very lightweight and don't bother with HTML at all: https://www.google.com/search?q=spiders&espv=2&biw=1439&bih=...

For anyone interested, I'm just gonna stick to Safari on my Mac and iOS.

For anyone interested, I hear gopher is making a comeback.

Re: Ōryōki Web Browser

#166
I really like the draggable windows, and the shortcuts for hiding and showing things. And the omnibox is, like, perfect; that's all I want.

But browsing a little, I immediately had problems zooming the viewport or increasing font size. Zoom gestures don't work, and neither does ⌘+/-. I couldn't find anything in the menu for it. Double-click on text does a zoom, but not enough. And sometimes content is moved off the viewport when you zoom in.

Very cool project.

edit: I'm still playing with it... it's got nice little notifications at the top. When you click a link, it says "loading...", then "850ms", or whatever; the page load time. And then ⌘← to navigate back shows "Navigating back", "Loading...", page load. It's cool. Looks nice. Dev tools open in a new window, and I couldn't find a way to open them in a panel, but maybe that can be set in the preferences.json.

Re: Ōryōki Web Browser

#168
post #167

For anyone interested, here's a monkey doing the dishes: http://giphy.com/gifs/monkey-dishes-dj3oNKpPWAGB2

We detached this subthread from https://news.ycombinator.com/item?id=12005185 and marked it off-topic.

It was meant as a joke... Lol, you can eve delete it if it is inappropriate

Re: Ōryōki Web Browser

#169
post #94

Earlier quoted context omitted.

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…

I ask myself this from time to time. It's hard to quantify quality, but I'm certain that the exponential increase of power in todays PC vs. that of a PC from the 90's is not reflected in an exponential improvement of the vast majority of software currently using this power. It seems that the more power that there is available, the sloppier the use of it. I wonder if someone already formulated some kind of law that de…

This. I think about this all the time and discuss it at length with people. Lotus 123 could do things people use Google Sheets for today with a few orders of magnitude less processing power, memory, and network bandwidth. In terms of UX, a lot of the stuff was near-instant vs noticeably delayed today due to everything running in browsers.

I argue that the UX has actually gotten worse since software is becoming more bloated faster than the hardware improvements can keep up with. There are more layers of abstractions and VMs running VMs running VMs simulating DOMs listening for changes to objects to update models to trigger actions which bubble up to listeners which fire events which change data structures that eventually update some text on the screen. Consider what happens in the physical memory, at the hardware layer, to have a modern React app print a line of text when a text box is modified. Contrast this with what a terminal does and what happens in memory. Printing text to the screen in a "modern app" is now so complicated that it's effectively impossible for a human to determine the CPU instructions and memory manipulations required to do the things we're doing.

And what do we do? We make more transpilers, more frameworks, move more to the browser, split our systems across networks and around the world. Contrast saving a file to a floppy disk with uploading that same file to a "modern app" which stores it on S3 using Paperclip with Rails, as many modern apps do. Think about all the systems that file goes through, the network requests, the protocols involved, the standards required to make that happen, and the infrastructure which powers it all. Think about the data centers those VMs running that app run in, the people who oversee them, the tooling they need to run those systems. Think about all the project managers who had a hand in setting any of that up, the financial planning of each aspect, the development time spent.

Recall the time when one could reason about what goes on inside a computer at every level, when key presses registered immediately, when the memory allocations of applications and the OS they ran in made sense to humans. When it felt like magic instead of digging through a trash heap of ads to find the tiny sliver of what you needed.

what the hell are we actually even fixing anymore?

Post reply on HN