Ultorg creator here. Ultorg is a GUI for relational databases that knows how to deal with joins and one-to-many relationships. In this demo, I use the new "Fill with AI" feature to generate appraisals for artwork objects in the National Gallery of Art.
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").
I pay $100/month for Claude Max and it's like having a (nearly) free, very competent employee. Value _way_ exceeds $100/months. But there's a datacenter that has to run that.
"Larry Ellison has been involved with two philanthropic organizations. First he made a $300M donation to Stanford, in exchange for not admitting wrongdoing in an options backdating scandal. All other philanthropic work is to the Larry Ellison institute for prolonging of life--namely his." -- Bryan Cantrill
I concur. This was my main experience with WSL1 vs. WSL2.
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.
I suspect the non-standard JSON license was in part a strategy to encourage third-party implementations, so that the format would become a standard.
(W3C standards, for example, require "multiple independent implementations to proceed along a standardisation path". https://www.w3.org/TR/webdatabase/ )
"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)
The "rule against surplusage": Where one reading of a statute would make one or more parts of the statute redundant and another reading would avoid the redundancy, the other reading is preferred.
Afterwards, they ship the entire engine, with turkey giblets and all, to a lab where the resulting damage is analyzed. Smells awful, according to the engineer I sat next to at a Thanksgiving dinner once...
In Norway, the card terminals usually go into an "accept with signature" mode if they are temporarily offline. So they print a receipt that the customer has to sign. (This is for BankAxept debit cards, which are standard in Norway.)
In a grocery store line once, I remember a distraught customer whose card was declined due to insufficient funds. The store manager came over, yanked the ethernet cable from the payment terminal, and told the customer to try again. "Accepted with signature."
Nations with high GDP tend to be service economies. Service professions tend to require good reading and writing skills, and often a college-level specialization. (No need for PhDs, though, except for scientists.)
No, it's a whole scientific field, with experiments, lit review, publications, peer review and everything.
The engineering artifact is just a by-product. More often than not, the code is thrown away or never used again, once the experiments have been run and the paper has been published.
CS theory is indeed closer to mathematics. But other areas--database systems, computer architecture, networking, user interface design etc., is in fact evaluated via experiments, which is what makes it "science".
For example, if you propose some new technique to make databases faster (e.g. "store tuples column-wise instead of row-wise"), you'll implement it and run various workloads with and without the technique enabled. That gives you a quantitative measurement of the merit of the technique.