This datalog implementation uses prolog syntax, can even run the queries in prolog to contrast the model: https://des.sourceforge.io/

If FSF trained a net on all the code that has Copyright assigned to FSF, could it be used to ethically vibe code free software retaining the same Copyright and license? Perhaps even pointing to a file on fsf.org with all the author's names?

The practical solution is to generate several CSV files and distribute work at the granularity of files

Sure, now you need to do this statically ahead of time.

It's not unsolvable, but now you have a more complicated system.

A better file format would not have this problem.

The fix is also trivial (escape new lines into \n or similar) would also make the files easier to view with a text editor.

But in practice, you’ll receive a bag of similar-format CSVs.

I have found two somewhat usable (your point still stands): soufflé (high performance but more limited) and DES, which works well for some simple personal data management, after some code massage (it’s written in Prolog). Any other recommendations? And since the prolog experts are here: what do you think about Ciao? Seems quite polished but also adventurous to (non-expert) me

Not using LSP does not mean not compiling/running. Using an LSP should not qualify you to commit without compiling or running either!

If you're new to the language or stack and make absurdly basic syntax mistakes, yes I consider using an LSP-capable editor of some kind a qualifier.

Don't do your job worse just because of your tooling preference. Do what you want when you know you can do the job well and not waste reviewer time.

So there must be at least three of us. Hi!

Hello. BTW, if there's no Motif tool available, there's always TCL/TK. As an example, TKDiff.

Or a Gemini/Gopher client:

https://codeberg.org/luxferre/BFG

It just requieres TCL/TK and tcl-tls. It's run faster than compiled browsers, even if the browsers have Javascript disabled. Services:

gemini://gemi.dev News Waffle, perfect for newspapers, no ads, no 700 cookies tracking you.

gopher://magical.fish Big portal, good news service

gopher://hngopher.com HN

gopher://gopherddit.com Reddit

This came to mind while considering your interesting point: After such a change, wouldn’t you feel the urge to inspect all users of the stricter return type and remove unnecessary handling of a potential null return?

I don't know about such urges. But sometimes there is no possibility to inspect all user code, e.g. when you are providing a library or API function.

Good point. In such case I would probably consider leaving the signature as is, even after tightening, and possibly offer a function with stricter signature for new code to use while deprecating the older variant. This would inform the users without rug pulling.

But that's not necessary in a language with union types of this sort. No rugs being pulled.

Looks fine (subjective) and there is also ctags

It is a personal choice of course, but some people enjoy the feeling of fully learning a piece of software, which is impossible with most.

Inferno is not a successor. For example you can have Golang for Plan 9 but doesn’t make much sense on Inferno. You would even run Inferno on Plan 9 on some scenarios. I suspect most people who know about Plan 9 also know about Inferno, but it’s just a different thing, does not supersede it in general.

Plan 9 => Inferno, which is still Plan

Alef => Limbo => Go.

Being able to backport Go into Plan 9, doesn't make sense in this context, that isn't how historical evolution works.

Also even Inferno has the necessary C infrastructure to port Go, if someone hasn't done it already.

I suspect you would have to port Go to run on Dis, the VM. C is for the OS. It’s a different design, without mmu. Plan 9 is still a classic OS with hardware isolation