The full title was "Algorithm: Recreational Programming".

I have only 4 issues of this quarterly magazine from the early 1990s. The rest seem nowhere to be found online, at least so far as my efforts. Each issue was a unique 'deep-dive' into topics only scratched by the articles in Scientific American's 'Mathematical Recreations' and, later, 'Computer Recreations'.

Does anyone else have issues? We need to group any extant copies together and digitize them for www.archive.org. Please contact me if you have any issues.

I contacted the University of Waterloo's CS department back in 2016, and they stated they had contacted Dr. Dewdney himself about it but I never heard back so I think it's up to us, the internet at large, to preserve this unique snapshot of the hobbyist/enthusiast computer scientist era.

Will do, thank you.

But if the reload is triggered by a form submit to an iframe (thus staying on the page) with a timed call to window.reload(), the page resets to the top. Not so in Firefox.

OP here. It doesn't go to 'the same location on the page', that's the problem. It always jumps to the top of the page, as if the anchor didn't exist.

Note there is, in my case, a form submit action to a hidden iframe with the reload but the page location stays put in Firefox.

Remember, Go is MIT-licensed. If things become too bound to Google, it can and will be forked. People thought it was the end of the world when multiple Java SDKs arose didn't they? (Not to say that didn't hurt Java, but the language survived).

Is anyone forking it to remove the Google taint?

I'm aware of TinyGo, but not any other forks

What Google taint is there in the Go compiler/command?

TinyGo is more of a "reimplementation, using LLVM" than a fork.

That being said, some pieces of the Go standard library have been copied across where it makes sense to (and works).

I selfhost gogs and like it. And the releases link is at the top like many ppl wish here :)

Only thing I really miss vs. github is there's no code review built-in.

Yes, yes it is. That will force open hardware specs, right-to-repair, limit damaging DRM, and encourage competitive software and hardware markets. And even multiple software stores, if that's what the market wants.

For what it's worth from the Peanut Gallery™, I find the proposed syntax quite readable and am happy there are no angle brackets <> stabbing my eyes.

It seems powerful enough to cover most cases of generics. Architecture astronauts will never be happy, but tough.

I'd definitely prefer angle brackets. With everything being parantheses I just get lost keeping track of what is what - they're now used for type parameters, parameters and return values, one after the other with no separation, and two of them are optional. Quite confusing if you ask me.

And yet, if you think about parsing it, they're all ways to group things together. Avoiding adding reserved characters (see also the discussion about adding ternaries) is a worthy goal to pursue. Keeps the parser(s) simpler too.

An IDE / coloring scheme can help make things look more distinct if need be.

Comparing it with the builtin hashtable:

* the custom one: hashtable.Table(string, int)

* the builtin one: map[string]int

The syntax forms are quite different. Wouldn't it be better to make them consistent? Is it so hard to achieve this?

It would not surprise me to learn that the parser has special rules for the token "map".

Yes, the fact that "map" is a keyword and "Table" is not really makes a trouble for parser. But I think we should think towards the road. There should be always a solution.

warehouse23.com/basement and its higher levels was a great timesink... SJgames put a minimal version back online recently, but it no longer allows new box submissions and seems to have lost a lot of the old content.

Consider self-hosting via gogs.io or gitea, and use them to mirror your key repo dependencies ...

>use them to mirror your key repo dependencies ...

Is this possible with a self-hosted gitlab?

Trying to get that to push to a cloud repo (GCP/Azure/whatever) as backup. Managed to selfhost gitlab but at the edge of my technical git knowledge here