Also, don’t be the one who fights sharp swords with Marvin Minsky’s useless boxes.

I guess GitHub is in a similar bunch of sources, it should be also more efficient to crawl by cloning. Anyway, isn’t it the whole sales pitch that it generates tailored solutions fast?

The Metals documentation includes instructions for setting it up with Emacs. I followed them, and everything works, including worksheets.

https://scalameta.org/metals/docs/editors/emacs

The code we've shipped throughout our careers certainly wasn't reviewed only by us. It was reviewed by programmers with more expertise in the relevant area. That's a healthy and efficient division of labor, expertise, and responsibility.

This reminds of a moisture farm from the Star Wars — https://starwars.fandom.com/wiki/Lars_homestead

"Well, if there's a bright center to the universe, you're on the planet that it's farthest from."

On a tangential point, one thing that should definitely not be possible for apps these days is determining whether you enabled a VPN. AFAIK, it’s possible indirectly in iOS by enumerating network interfaces with specific/telling names.

Looks similar to the halting problem to me (https://en.wikipedia.org/wiki/Halting_problem)

Whether an arbitrary piece of code can be exploited is obviously undecidable (i.e. it is equivalent to the halting problem). Let me give you an example that will sketch why this is the case: `if(sha(input1)==12345) { run_shell(input2);}`. The real question is how does this look like in practice, for the code that we as humans actually use in our networks.

> Polynomials are for people who think AGI is "decades away."

Je suis un polynôme

And https://en.wikipedia.org/wiki/Mottainai I guess

There is also a way to import a table from the STDIN (see also https://duckdb.org/docs/data/json/overview)

cat my.json | duckdb -c "CREATE TABLE mytbl AS SELECT * FROM read_json_auto('/dev/stdin'); SELECT ... FROM mytbl"