I wonder, is there a good reason to use Dillo over something like Netsurf or Ladybird nowadays? They support far more of the Web (i.e. more likely to be useful) while still being lightweight.
25 Years of Dillo
61–70 of 100 posts
Re: 25 Years of Dillo
#62For those curious about Dillo, you can try it right now in your browser. On the JSLinux site, the graphical VMs come with Dillo 3.0.5: https://bellard.org/jslinux/vm.html?url=alpine-x86-xwin.cfg&... (Warning: this will download 30+ MB) After it starts up, right click, and then choose Browser - Dillo. There's no HTTPS support, but Google and httpbin.org work at least.
I heard you like browsers dog
"yo dawg, I heard you like browsing, so we put a browser in your browser so you can browse while you browse"
Re: 25 Years of Dillo
#63Re: 25 Years of Dillo
#64Earlier quoted context omitted.
oh I just looked into it again for fun and noticed that indeed it defaults to sleeping at least 2 seconds every time you open a URL but this can be changed in lynx.cfg by altering these defaults: #INFOSECS:1 #MESSAGESECS:2 #ALERTSECS:3
Why would they possibly include this?
Re: 25 Years of Dillo
#65Earlier quoted context omitted.
oh I just looked into it again for fun and noticed that indeed it defaults to sleeping at least 2 seconds every time you open a URL but this can be changed in lynx.cfg by altering these defaults: #INFOSECS:1 #MESSAGESECS:2 #ALERTSECS:3
Why would they possibly include this?
That and developers often conflate knowing how to construct UIs with how to design UIs. When lynx was first built, the difference in speed probably wasn’t that noticeable and people didn’t have the same expectations for responsiveness, so it didn’t matter, though times quickly changed.
I don’t know about that project specifically, but based on my experience trying to do design work in developer-controlled projects, maintainers and core users often convince themselves that some terrible user-hostile counter-intuitive UI— focused on graphically representing the API to the back end rather than using abstractions to solve the problems users actually want to solve— is the proper UI approach and if it doesn’t fit your use case, the problem is either you or your use case.
Re: 25 Years of Dillo
#66it can show a basic unbloated news site from my contry it can show lwn.net it can show HN it can show old popular local forum it can show rss feeds it automatically blocks (does not work on) all the popular social networks -- what else is there?
gopher and gemini plugins work great, it needs dillo mainline. Also: gopher://magical.fish Huge portal, with news sources gopher://goherddit.com Reddit gemini://gemi.dev News Waffle, able to browse Ars Technica and so over Gemini.
Also, there's the Floodgap Public Gopher Proxy:
Re: 25 Years of Dillo
#67Re: 25 Years of Dillo
#68Earlier quoted context omitted.
Unfortunately, with it's use of Swift code, QT (which is now a bloated piece of trash since version 5) etc. It's just not tenable unless they give us a pure version without that shit
Why/how does the presence of Swift make QT a bloated piece of trash? Genuine question. I know little of QT and nothing of its history re: Swift or version 5.
QT is bloated and resource intensive. Most of us don't want gigabytes of data being spent on special effects.
Re: 25 Years of Dillo
#69Earlier quoted context omitted.
Unfortunately, with it's use of Swift code, QT (which is now a bloated piece of trash since version 5) etc. It's just not tenable unless they give us a pure version without that shit
QT I can see how it is disturbing. Swift I can not see how it would bloat anything for end users. It’s just another compiled language.
Re: 25 Years of Dillo
#70Earlier quoted context omitted.
Unfortunately, with it's use of Swift code, QT (which is now a bloated piece of trash since version 5) etc. It's just not tenable unless they give us a pure version without that shit
QT I can see how it is disturbing. Swift I can not see how it would bloat anything for end users. It’s just another compiled language.