Biggest problem I had with Void, was that the musl libc support wasn't as good as Alpine.
This is because Void gives you the choice between glibc and musl. Therefore the team spreads themselves thin trying to support both. So some packages for Void musl are unavailable.
I use it and it works quite fine! Just a few differences you need to learn, all of which are noted on their concise wiki. It's best to think of Arch as the fallback distro, therefore all other information is obtained from the Arch wiki as normal.
> meaning the net effect is just to make browsers more complicated.
Maybe it would, slightly. But would it make the browser anymore complicated then the unessential features that Firefox has in its default build right now?
Pocket integration, FF Sync, some screenshot function?
The web is so broken that my Firefox even has some Protection Dashboard thing (about:protections). Not that I've ever used or noticed it before.
So did I. But I'm not going to let one drawback distract me from something otherwise very good, nothing is perfect after all.
I can even understand why they did it. To keep the doc format very simple.
I hope that more clients will add unique rendering features that will turn this drawback on it's head. It could be in-line rendering or a gallery-like feature.
> Gemini has no support for caching, compression, or resumption of interrupted downloads. As such, it's not very well suited to distributing large files, for values of "large" which depend upon the speed and reliability of your network connection.
> How is a network protocol proof against being used to transport CSS files? Does the network stack inspect what you're shipping and ensure you're only sending 100% Pure Plain Text?
It's just like the web, the transport protocol (HTTP/S) can be used on any file. But there is a separate spec for the document format (HTML etc.). You could transport CSS over Gemini, just don't expect any of the browsers to render it. Just like how web browsers won't execute alternate scripting languages natively.
> Isn't that TCP's job? Is this person saying Gemini doesn't use TCP?
I didn't really elaborate on this point while writing, because I had nothing to add. I will quote from the projects FAQ:
>> Gemini has no support for caching, compression, or resumption of interrupted downloads. As such, it's not very well suited to distributing large files, for values of "large" which depend upon the speed and reliability of your network connection.
Hopefully that clears up what I meant.
> Back in the Gopher days, my "Gemini browser" would be my Web browser.
You might be interested in Castor[1]. It's a browser for the minimalist internet. Rolls support for Gemini, Gopher and Finger all in one.
I can understand why FF removed support. But hopefully smaller applications, like Castor, can fill this gap.
I probably won't run anything besides Firefox for my web browser. But I see the web as broken beyond repair in regards to the way it is.
So I am more interested in moving away from the web. Things like using terminal programs (youtube-dl, rtv etc.), native GUI apps, or complete alternate protocols like Gemini[1].
I see the web being completely out of my control as it is. I see my usage of it as being more of a virtual machine for the things I need it for (government stuff, communication platforms etc.).
I feel like slowly packing up and leaving.
But I will still try and exert some decision making while I have to use it. And I intend to do this by choosing Firefox-based browsers.
I've been playing Deus Ex from GOG.com on Linux (under Wine) myself and it has worked great.
But I think that an open-source release of Unreal Engine 1 that could potentially give us the power to fix these issues, would be great. The final thing that Deus Ex needs before becoming perfect is an open-source engine (kinda like OpenMW).
Here is a review for those interested in the game: https://www.youtube.com/watch?v=Valmsq_Ku90
If you want to try this, use a development build. Releases are stale, plus git head contains a few additional fixes.