[spec] comments on the proposed gemini spec revisions

Oliver Simmons oliversimmo at gmail.com
Wed Oct 13 23:26:42 BST 2021
On Wed, 13 Oct 2021 at 22:40, Omar Polo <op@omarpolo.com> wrote:
> Oliver Simmons <oliversimmo@gmail.com> writes:
> > very annoying and **slower** in most cases.
> I was contradicting that.

Oops, my bad.

> > The way I understand your message, I would have to use an else-if
> > list, which is hardly ideal.
>
> This depends on the language design.  Some languages allows expression
> inside switches, like Go IIRC, so you could write
>
> […]

Interesting.
I don't have a clue how this would work internally, but I imagine it'd
be less optimised than equality.
Although what you mentioned about string equality has me doubting
that's well optimised either… this is getting waay off topic :P

> I don't think taking into account the particularities of one specific
> programming language is a wise choice for a markup language meant to be
> written by humans for humans.

I'd've hoped I wasn't taking a too narrow viewpoint with my language
experience (Py3, C# & a little Go).
C# is used here as I've got a basic Gemini client made in it, and
that's in C# as I have to use it for my education :p

> Gemini doesn't have inline formatting, so why bother trying to support it?

This is not about inline-formatting, using emphasis in text /like/
*this* has been a thing since before I breathed.

> (I've used some *emphasis* on some pages too, but more I write and more
> I think I shouldn't, it's easier to read without too much noise.  That's
> my opinion, at least.)

I find it useful in moderation, I'm not the best at conveying what I
mean so it helps.

-Oliver Simmons (GoodClover)


Archive home | About this archive