What's the benefit of Dillo versus, say, NetSurf?
Show HN: Resurrecting the Dillo browser
31–40 of 179 posts
Re: Show HN: Resurrecting the Dillo browser
#32The extension system[0] seems interesting; it reminds me of w3m's local CGI
scripts. (From what I can tell, w3m's local CGI came first, but I don't know
if it influenced DPI and/or if w3m's system had a predecessor too...)
For a short description of what w3m local CGI scripts can do:
* They can be used for implementing a man page viewer, as in w3mman. It seems Dillo has a similar plugin[1].
* w3m's bookmark system is implemented using local CGI; it seems Dillo's bookmarks are implemented as a dpi plugin too.
* w3m can use urimethodmap + local CGI to implement additional protocols. I guess DPI can do that too? (At least the custom man: scheme in dillo-plugin-man seems to indicate it can.)
I had no idea any browser supported this besides w3m. I mostly imitated w3m's design in my own project (which includes the twist that support for every protocol, including HTTP, is implemented on top of a similar plugin system); I guess I have a second reference point now :)
Re: Show HN: Resurrecting the Dillo browser
#33Hypothetically, could JavaScript support be added by using a lightweight engine, such as QuickJS?
Probably but my guess based on the state of the web is that this a rabbit hole without end
Re: Show HN: Resurrecting the Dillo browser
#34What's the benefit of Dillo versus, say, NetSurf?
A lot more lighterweight, and nowadays it's good to have less (it has less CSS compatibility, less html compatibility and no JS).
Re: Show HN: Resurrecting the Dillo browser
#35Very nice to hear!
Anybody knows what happened to Jorge A. Cid?
Re: Show HN: Resurrecting the Dillo browser
#36Given the circumstances, I am happy to read this. I own two ~2009 netbooks with Intel Atom N270 CPUs and 1GB of RAM each - running Firefox on those is ridiculous, whereas dillo will run very well on these. I used to use dillo on my main desktop too, for browsing documentation that wasn't too heavy on CSS - having 20 to 40 tabs open would gobble up a lot of RAM in Firefox, whereas dillo happily stayed around 100MB no…
I also like dillo, but just as an option - have you tried netsurf as well? Likewise very lightweight.
Re: Show HN: Resurrecting the Dillo browser
#37What's the benefit of Dillo versus, say, NetSurf?
I'll have to do an in depth analysis first, I have very little experience with NetSurf.
I would say that the plugin system is one of the things makes Dillo a bit different.
I had some ideas to do performance tests and also check how well the rendering engine works with choppy connections (while content is still slowly downloading), but I didn't do any tests yet.
There were some very old results against firefox comparing memory usage in the old page [1].
Re: Show HN: Resurrecting the Dillo browser
#38Well done! Dillo is a great little browser.
Re: Show HN: Resurrecting the Dillo browser
#39Earlier quoted context omitted.
Thanks! > What's the minimum compiler you target? I didn't defined any (yet), but shouldn't be too hard to add to the CI. > Any big long term plans? First preventing it from dying and getting removed from distros. Then it depends of how much free time I can dedicate to it, but at least maintaining it. > Fuzzing? I would say first adding some of the other browser tests suites. That should catch a lot of rendering issu…
I would suggest switching to Meson instead of CMake.
I would suggest neither of those, nor ninja nor anything but make. Whatever sucks about a simple/shallow stack, what sucks about tall fat stacks is worse.
Re: Show HN: Resurrecting the Dillo browser
#40Nice to know Dillo still gets some love! I've got a lot of dillo plugins stored up that I managed to get from scuttlebutt a while ago(dillo-adb, dillo-dat, dillo-finger, dillo-git, dillo-gopher, dillo-gemini, dillo-ipfs, dillo-ssb and dillo-ytdl), and if you're interested I can zip them up and send it to you to be forked and worked on the project
I think most of them are from Charles, and he maintains a scuttlebutt-web interface, so you can download them from the homepage: https://celehner.com/projects.html#dillo-plugins I already talked with him about keeping a copy of them in GitHub under the dillo-browser organization. > and if you're interested I can zip them up and send it to you to be forked and worked on the project Feel free to open an issue and uploa…
Done!
I actually had forgotten where I had got them, but it's great that their original repos are still up!