If you need ten pages to explain your project and even after I read your description, I'm still left confused why I need it at all, then maybe... I don't need it?

Draw your own conclusion.

So repeating the same mistake that Spring made by using runtime exceptions everywhere.

Now you can never know how exactly a function can fail, which means you are flying completely blind.

Why is this written

    lea eax, [rdi + rsi]

    lea eax, rdi + rsi

?

    sum_(i=1)^n

How about using some symmetry instead, e.g.

    sum(i=1)(n)    "Means: sum from i=1 to n"

Very similar idea as Bruno: everything is configured in text, which I always find myself more productive in that full blown GUI where I need to tab from edit text to edit text to get anything don.

[1] https://www.jetbrains.com/help/idea/http-client-in-product-c...

The Amiga with its revolutionary coprocessors (Denise, Agnus, Paula) was a game changer.

However, id Software taught the world that the important part of the software revolution was not in these coprocessors but in fast 3D code. And the Amiga architecture was simply not ready to face that challenge.

Now to be fair, I don't think DOOM killed the Amiga, but I am reasonably confident Windows 95 did.

Uh? How is that innovation? 100% of mainstream languages that I can think of that predate Go do this.

Can you name one programming language that we should care about which, once you define an interface, FORCES YOU to provide an implementation of said interface?

I don't.

The hardest part in implementing generics is when you support inheritance of implementation.

Go doesn't.

Go had the easiest job in implementing generics.

The only reason why they didn't was not technical: it was ideological and purely based in ignorance, and the fact that most Go designers stopped paying attention to the field of PLT in the late 90s.

ProDOS came up with this new call syntax where the parameters to the API follow the call to it.

For example:

            ldx #$00
            ldy #$10        
            sty params+4
            stx params+5    ; setup number of bytes to read (16)
            jsr $BF00       ; call ProDOS
            .BYTE $CA       ; ProDOS command number = CA (read)
            .WORD params    ; address of parameter table, lo/hi
            bcs error       ; carry set, error
            .
            .
            
     params .BYTE $04       ; number of parameters for a read
            .BYTE $00       ; file reference number, 0, 1, 2 in MacQForth
            .WORD BUFFER    ; pointer to data buffer
            .WORD $0000     ; requested number of bytes to read, fill in
            .WORD $0000     ; number actually read, returned by ProDOS

It's going in a random direction, and probably in a straight line.

Statistically, even at light speed, they would probably only encounter another system every few millions of years or so.