@wowaname I'm stating my position more strongly now in discouraging streaming, but I acknowledge that it's good fit for how many like to enjoy their entertainment. Even if it isn't how I like to enjoy it.
Ultimately I think that letting users rather than websites choose whether to download or stream is what'll make best use of bandwidth.
---
I'm with you in regards to blockchains, and would add that I have nothing against "closed blockchains" as a solution.
Also I'm taking care to modularise my browser engine for Rhapsode! My URL & CSS engines are totally independant of each other! Haskell's pattern matching syntax has helped a lot here.
I do this because I want to help others experiment with their own browser engines. Or find other uses for these libraries!
@crash_override Yeah, that piece of advice is *at best* redundant with their other recommendations.
I must say AMP strikes me as a Google identity struggle, they can't accept how much they're responsible for The Web's sluggish performance. Especially with Google's sheer influence at the W3C where they push in the opposite direction from AMP.
@jeroenpraat I hope the performance improvements of my libdggs project will bring necessary analysis tools into more people's hands than just the oil companies. And more generally in my software development I attempt to minimize my software's use of The Internet, which is currently consuming as much energy in total as aviation.
Wayland, which I'll start describing today, is the protocol by which apps on your freedesktop communicates with your window manager for their main I/O. Weston was it's reference implementation, but I believe they've decided that title is now meaningless.
To be clear nothing I'll be describing here is special to Wayland (beyond not requiring a seperate daemon from your window manager), as X11 has implemented these features before Wayland started superceding it.
@Wolf480pl@rysiek@jerry@Aaron I do kind-of have questions about Matrix. From a distance it kind-of looks like they decided to reimplement XMPP with the latest fashion of JSON. And I still have to explore it's encryption situation.
As for SSB I'm starting to look into it, particularly with Git-SSB. And from what I've seen, the tech looks very elegant when dealing with group comms or reliability despite the clients. Though again I have to look at the encryption again.
I played with Git-SSB today! And I used this peer-to-peer git hosting to begin to think through and describe how I'd implement a peer-to-peer triplestore database.
I've heard plenty about others evangalizing (even if that's not meant to be their job) software tools they say "do everything".
This view really perplexes me as we have software tools that do everything: they're called "programming languages". It doesn't take much to make such a tool. What does take effort is making a tool that actually solves a problem well for people.
A browser developer posting mostly about how free software projects work, and occasionally about climate change.Though I do enjoy german board games given an opponent.Pronouns: he/him