Comment

Comment on Ladybird Browser adopts Rust, with help from AI

veniasilente@lemmy.dbzer0.com ⁨4⁩ ⁨days⁩ ago

Every minute that passes, Gemini (not the Google one!) looks more viable, which is already a shame because as I described in lemm.ee before it went down, that itself feels like “Gopher but in the format of a brutalist buttplug”.

What we need is some sort of return to HTML + CSS 1.0, or a web engine that simply ditches JS, so that development can be tackled by Individuals again.

source

Sort:hotnew top

CameronDev@programming.dev ⁨4⁩ ⁨days⁩ ago
github.com/DioxusLabs/blitz - This kinda covers the “engine without JS” part, it’s a bit more limited, but also in alpha. It’s part of the dioxus project, they use it for rendering UI on desktop.

source
- veniasilente@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago
  Oh now that’s interesting. I’ve always wondered (not knowing much about how they’re made) if it would be possible to make a desktop compositor for Linux that simply uses HTML and CSS. One could even natively embed local pages in it.
  
  source
  - CameronDev@programming.dev ⁨3⁩ ⁨days⁩ ago
    Gnome shell uses JS and CSS (i beleive anyway), and the w11 start menu is supposedly react native, so I think the answer is definitely yes.
    
    source
    veniasilente@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago
    
    Gnome shell uses JS
    
    I knew there was a reason why it sucked so much!
    
    source
vacuumflower@lemmy.sdf.org ⁨4⁩ ⁨days⁩ ago
Separation of server styles, server markup and client styles is definitely something Gemini lacks, not having server styles at all.

But it’s not as much a problem of browsers as it is of the environment in which information is shared and propagated. While we still connect to websites using a browser, those websites will behave however their owners wish, inflating web standards and requiring complex browsers.

I was dreaming of something like “hypertext Usenet”, and making descriptions of another system I was interested in trying to make, I am still not even close to that, and I’m not sure I’m still interested, because it appears NOSTR now has much of what I wanted in its standards.

Basically if you imagine a system for propagating posts addressable by ids and with markup inside, referring to styles and containing hyperlinks by ids to other posts, you can throw away the idea of a website, and still have the hypertext web. That markup can be anything, while the URLs in the links leading to images and such (and other pages) are using those ids or are at least Blossom-compliant.

I think NOSTR of new protocols is the one most likely to eventually attain such functionality. People here wouldn’t like it, I suppose, because of huge intersection with Bitcoin community and because most clients and client libraries are for the web. But there’s now a C client library, functional enough, and architecturally NOSTR is worlds above the thinking of designers of Lemmy, for example.

source