A look at the Gemini protocol: a brutally simple alternative to the web

Re:A look at the Gemini protocol: a brutally simple alternat... by iamstupidsimple on Saturday July 04, 2020 @09:29AM (#23732071)

The original Facebook and Google did not use much JavaScript, so I'm always skeptical when literal documents need it for anything other than ads (and even then...).

[ Parent | on HN ]

Re:A look at the Gemini protocol: a brutally simple alternat... by colejohnson66 on Saturday July 04, 2020 @05:03PM (#23734895)

And the screen refreshed every time you did something as it loaded a new page. Just because it’s abused doesn’t mean JS doesn’t have uses.

[ Parent | on HN ]

Re:A look at the Gemini protocol: a brutally simple alternat... by lal on Sunday July 05, 2020 @02:40PM (#23740867)

the screen refreshed every time you browsed to new content or did something that required accessing new content, as one would intuitively expect

[ Parent | on HN ]

Re:A look at the Gemini protocol: a brutally simple alternat... by ddalex on Tuesday July 07, 2020 @06:37AM (#23757687)

I never understood the hangup on screen refreshes - I mean, why is it important that the screen doesn't refresh?

And if it's that important that EVERYBODY deploys JS to render client side to avoid the refreshes, why isn't this handled at the browser level in the first place (i.e. declare "ExtendDisplayTime"-something on your document and the browser should replace the screen content only AFTER the new page is completely painted).

But at the core of it, the web is a document-display system, and back-hammering and shoe-horning apps that masquerade as documents will always be painful.

[ Parent | on HN ]