Earlier quoted context omitted.
NetSurf actually looks good.
I use NetSurf on a Raspberry Pi B regularly. Does the job unless you need JS.
There is limited JS support now too, which will likely get better over time.
Ōryōki Web Browser
131–140 of 181 posts
Re: Ōryōki Web Browser
#132Worked on something similar[1] for a school project (although didn't implement nearly as many features) Electron makes it really easy to experiment with browser UI. [1] https://github.com/reedrosenbluth/Concept-Browser
Actually, upon further inspection mine has more or less the same features
Re: Ōryōki Web Browser
#133Re: Ōryōki Web Browser
#134This 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.
I'm going to shit on it for being at the top of hacker news and after a minute of looking at the web site I still have no idea what the point of it is.
Please don't do this here.
Re: Ōryōki Web Browser
#135Earlier quoted context omitted.
That seems like exactly what you are doing. So you want to run a game and a youtube video and browse at the same time, while on a low end PC. Cool. A lot of people don't use their computer like that. I can do all of that at the same time as is...
What kind of ridiculous, fallacious logic is this? First of all, it's not a low end PC, it's an expensive gaming-dedicated rig barely a couple of years old. The amount of resources browsers consume is just ridiculously high . Second, the argument that browsers should use all the resources and ram available in the world only holds if your computer is dedicated to web browsing. This is quite obviously false - I shouldn…
What sort of hardware are you talking about? Just curious.
I can youtube+[Witcher3|DarkSouls3|Skyrim+10GBMods] just fine with my 4k series i7, 16GB, GTX970.
Re: Ōryōki Web Browser
#136Earlier quoted context omitted.
Chromium doesn't use webkit, it uses Blink.
Blink is a fork of WebKit and is still largely the same.
Blink has diverged a fair amount. There are different new features, bug fixes and optimizations.
Most things based on Chromium also use more components of the Chromium stack than just Blink. For example, in WebKit multiprocess support and sandboxing is provided at a batteries-included level. But Blink just has the hooks for it, while the actual implementation of the process architecture is done by other aspects of Chromium.
This is not to say one way is better or worse, but rather that there's significant differences between being WebKit-based vs Chromium-based.
Re: Ōryōki Web Browser
#137This 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.
This is a common objection that does carry some weight, but turns out not to hold in HN's context. In a large, semi-anonymous, weakly cohesive internet forum, the behavior referred to in this thread as "shitting" propagates into a force that's destructive of the community. The best people begin to leave, the shit piles up, and soon we're in a death spiral.
That's the #1 risk to HN, so we worry about it. Like many here, we've seen it happen before, and HN was literally founded on the idea of not letting it happen again—or at least trying to stave it off.
That doesn't mean we don't get the value of hard-hitting technical critique done in a right context; it means that HN is not a right context for the shitting variety. Nor do we ask users to be namby-pamby milquetoasts; we ask them to understand enough about the fragility of the community to preserve it for the future. We don't want a scorched-earth outcome.
So go ahead and make clear technical criticisms, but make them without the extra jabs that people often feel compelled to stick in. That latter behavior isn't hard technical critique anyhow, just chest-beating.
Re: Ōryōki Web Browser
#138Just in case anyone else is curious:
応量器 Noun 1. mendicant priest's begging bowl (Buddhist term)
Re: Ōryōki Web Browser
#139Earlier quoted context omitted.
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.
Each tab is a separate process. A separating operating system, you could say. Would you complain that your OS needs that much RAM? I wouldn't.
[deleted]
Re: Ōryōki Web Browser
#140Earlier 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…
When a experiment has a domain and a splash page, it's left behind the status of "an experiment" and gone into the realm of "a product".
IMHO, free or not, it's a product, and should be judged appropriately.