Something you might find interesting to look at is Rego, a datalog-derived language been used for writing security policies. Rego is dynamically typed, so no real protection. It's input is basically JSON and it can apply JSON-Schema, but that's it. I think it would be interesting to look at Rego as a restricted version of this and see what types buys for a Rego user. It's probably one of the larger areas of logic programming and has brought people into the fold, so to speak.

Oh wow, Zoltan was one of my lecturers at UniMelb, and in one semester we were tasked with learning his Mercury language. So good to see it thriving still.

I TA-ed for Zoltan's 2nd year "learning how to use bash/gdb/etc" class and it was a lot of fun. I hope they're still teaching that class.

It was called "433-252 Software Engineering Principles & Tools" until ~2008 I think (433-244 before that) but then it seems to have been reorganised. Tbh, Unimelb Comp Sci is a shadow of it's former self, a victim of the 'Melbourne Model' common core sausage factory concept.

Is it the same model as the "Bologna process" in Europe, which is kind of funny because "Bologna" also refers to a type of sausage in the US of A.

I hope he's stopped drinking Fanta.

prince, a high quality html renderer used for typesetting, is written in mercury:

https://www.princexml.com/doc/acknowledgements/

Was it written in Prolog at any point in time ?

Perhaps I am misremembering, but my brain is telling me of a CSS or PDF parser written in Prolog.

The closest that I could find to a "what the fuck is this?" page is:

https://www.mercurylang.org/about.html

There are files in this repository that were last touched 32 years ago. Any reason to be posting it now?

Not that it necessarily applies here, but as a heuristic: https://en.wikipedia.org/wiki/Lindy_effect

Interesting point. My understanding of Mercury is that it is hard carried by Zoltan so it has a bus factor of 1.

I always understood it was a teaching language for students who wanted to get programming language implementation experience.

Why is that relevant or noteworthy? There are files that were updated recently too.

Why the aggression? This language while cool has existed for decades and never taken off. I just wanted a reason to believe it relevant so I could have an excuse to take another look.

Why do you think "oldest untouched file" is a good metric for relevance? Do you know what is the oldest untouched file in gcc or Python?

There was no aggression.

"Taking off" is an unreliable metric of capability and fitness to a problem you may want solved.

Damn dude you're making me feel old

Last commit was 2 minutes ago. Seems like a better measure than releases, different projects have different release cadences.

You say “dead”, I say “stable”. Not everyone wants to base their work on a moving target.

But the repo has had fairly consistent commits since then. Not huge activity, but not sure I'd call it dead.