eirikbakke
Joined 4 years ago
Joined 4 years ago
The interesting part is in the handling of joins. We can show a list of artworks, and for each artwork, a list of provenance timeline entries, and related data from other tables, and then use all of this data as context for the appraisal task. The UI for this is intentionally minimal; the user enters only a few words for a prompt (Appraisal column: "an appraisal of the artwork, in US dollars, for insurance purposes". Rationale column: "rationale for the appraisal").
People are conflating destructive and productive activities. These are fundamentally different.
(Or at least AI-assisted to the point where the author feels like they should mention it.)
If I'm running Windows, it means that the files and projects that I care about are on the Windows file system. And they need to be there, because my IDE and other GUI apps needs files to be on a real file system to work optimally. (A network share to a WSL2 file system would not let the IDE watch for changes, for instance.)
WSL1 was a great way to get a UNIX-style command line, with git, bash, latex etc., for the Windows file system. WSL2 was just too slow for this purpose; commands like "git status" would take multiple seconds on a large codebase.
Now I switched back to MacOS, and the proper UNIX terminal is a great advantage.
(W3C standards, for example, require "multiple independent implementations to proceed along a standardisation path". https://www.w3.org/TR/webdatabase/ )
(I wonder if it would convert cleanly to a redstone circuit...)
"Judges frequently invoke anti-redundancy principles in the interpretation of legal language, whether it appears in classic private-law documents such as contracts or classic public law-documents such as constitutions and statutes."
Redundancy: When Law Repeats Itself, John M. Golden (2016)