dillo VS buildroot

TLDR: Dillo is a fast and small graphical web browser. It kind of died in 2017 and this is the first release after 9 years from the last one.

You can read the main website for more details[1].

[1]: https://dillo-browser.github.io/

And the release page[2], which explains a bit of the history of the project and the current state.

[2]: https://dillo-browser.github.io/latest.html

Sort-of mentioned this in a previous comment also, but I suppose FLTK is alive and well for regular users of Tiny Core Linux (of whom there are quite a bit, I guess -- myself included). The recently resurrected Dillo web browser also relies on it: https://dillo-browser.github.io/

I'd put this dillo fork:

https://github.com/dillo-browser/dillo

Thanks for your DPI work. I tested the gemini plugin and works very well.

My only complain is that it keeps asking to confirm new keys every time a new server is visited which causes a lot of friction to explore several gemini servers. I understand that is a tradeoff between usability and security, but I wish there was a better solution than that.

For now I uploaded Charles plugin written in shell script[1], which always trusts the certificate.

[1]: https://github.com/dillo-browser/dillo-plugin-gemini/

But I'm considering switching to the Go version if I can find a way to improve the UX.

Also, I kindly ask you to add the tag "dillo-plugin" so you can make Dillo plugins easily discoverable by searching for the tag in GitHub[2].

[2]: https://github.com/topics/dillo-plugin

> I believe that in recent versions of Dillo, even https is implemented as a DPI plugin.

This was done initially[3] (before 2007) but it was moved to the browser itself[4] in 2016.

[3]: https://github.com/dillo-browser/dillo/commits/afd2763caa56d...

[4]: https://github.com/dillo-browser/dillo/commit/bf5a7783f4a192...

I did it few times. It's so much easier nowadays with https://buildroot.org/

If you dig through the rootfs of the K1 it becomes clear that Creality is using buildroot so we should be able to do that ourselves - at least some of us.

An embedded system like Roku doesn't need to "run everything", it just needs to run their "platform", which is probably quite small. It's pretty trivial to assemble your own OS from "off-the-shelf" components. You can use something like buildroot to spin up a new OS in half a day, using only the components you want. You can also use "smaller" components that have far fewer features, meaning less bugs and less updates.

https://github.com/buildroot/buildroot

> I do this for every Windows installation that is used for similar purposes, like embedded machines that has to run a single application, virtual machines, etc.

Have you tried running Linux for these use cases? This sort of thing is an area Linux excels, in my experience.

When you run Windows, you're in for the whole kit and caboodle. Most of the components are proprietary, closed-source black boxes. You can only poke and prod and test and hope things don't break in unexpected ways.

Conversely, Linux can be easy stripped down to a bare bones kernel and a single statically-linked binary. I can run a useful application on top of Linux with the whole system weighing in smaller than bootmgfw.efi.

Something more complex, but still custom, is easily crafted with Buildroot.

https://buildroot.org/

Have a look at the commit history of Linux or buildroot for nice readable commit histories.

Gentoo could teach you more about what is involved in dependency handling and actual ‘construction’ of a Linux system. But Linux From Scratch is a much better teaching tool for learning this, and even things like Buildroot are arguably better than Gentoo for this because they generally force you to care about a lot of the stuff that Gentoo hides away to make the system nicer to use.