There are good reasons why HTML became the dominant front-end format in the late 1990s.

Before that, developers had to build separate native apps for platforms like DOS, Mac OS, MS Windows, NeWS, X Windows, etc

Not only was this expensive, it was tiring.

As the internet spread, HTML became the ubiquitous front-end format, eliminating the need for multiple versions

But, this put these 2 use-cases (doc vs app) at odds

#GeminiProtocol #MercuryProtocol #SmallNet #SmallWeb #SmolNet #SmolWeb

The point of small-net / small-web isn’t about plain-looking documents — you should still be able to make them look good.

One of the goals is to separate document formats from app formats, so they aren't at odds — and through it try to eliminate the kinds of abuses seen on the Web today.

Some have chosen GemText or Markdown as that document format. Other use a subset of HTML.

#GeminiProtocol #MercuryProtocol #SmallNet #SmallWeb #SmolNet #SmolWeb

At least as of the current date — the small-net / small-web communities have focused a lot on document formats

Which is great!

(Although I think people should try stuff that doesn't look like GemText & Markdown)

But, there hasn't been much effort to create app formats

I think a risk is, if we don't create app formats too, people will start trying to use document formats as app formats — just like what happened with HTML

#GeminiProtocol #MercuryProtocol #SmallNet #SmallWeb #SmolNet #SmolWeb

@lazarus

Back in the day, GTK/GNOME had the Glade XML format.

But, I think Blueprint has become more popular now. Ex:

```
using Gtk 4.0;

template $MyAppWindow: ApplicationWindow {
default-width: 600;
default-height: 300;
title: _("Hello, Blueprint!");

[titlebar]
HeaderBar {}

Label {
label: bind template.main_text;
}
}
```