I'm surprised this article doesn't mention that classical latin pronunciation actually had V realized as W or U depending on context.

Latin didn't have two letters to distinguish V and U. You can still find inscriptions with VVA (modern spelling UVA)

Later that sound morphed to a voiced labiodental fricative which is what we think of V now

I think both your arguments are true. It all depends on the velocity of the capability growth and the fact that opportunity cost is expensive.

Once we get out of this hypergriwth phase the very same AI companies that now are giving you llms will provide a service that employed a rich mixture of optimized models that will reduce the operational costs to achieve the required results

Your comment might be sarcastic, but AGENTS.md already exists for the explicit purpose of agents reading and using it.

yeah, my point is just that we agents can have their own docs and we can also have a nice curated experience for humans.

Hmm, I wonder if we can automate that

There are certainly consequences in participating in a war against Russia.

There are also consequences in letting Russia take Ukraine militarily.

Whatever you think about the motivations and the desired end goal, actions and lack of actions both have consequences

Plenty of old people now grew up in a phase in history where we were building ugly cheap things

That was all of history.

Being good at matching patterns doesn't mean the patterns you found have the causal relationships you think they have

Superstition in pigeons: https://psycnet.apa.org/record/1948-04299-001

but the pigeon doesn't have the benefit of using bayesian priors nor collaboration

"Music Theory, Bells and Whistles"

First review with that as a title:

”Beware, this is just a general book of modern music theory masquerading as a guide specially for the bell or whistle player”.

"BaW Music Theory", for that click-bait effect.

I wonder if we're doing virtual filesystems wrong.

There is a good reason why traditionally filesystem access was mediated by the OS layer, but there are many use cases where you just want to give processes a different view of what they already can access and it could be done as a library in the same userspace process.

However, for that to work across all the processes in a session we'd need a standard way to install such a hook in all peocesses and that's achievable to some extent using LD preload but falls apart quite rapidly with statically built binaries or different libcs

I think there is a good case to be made for these things not to be mediated by the operating system by default.

In Objective-Smalltalk[1], I can access a file as follows:

   hello ← file:hello-world.txt 

This is structurally the same way I would access a local variable, environment variable, database, remote http server etc.

   hello ← https://example.com/hello-world.txt
   hello ← env:GREETING
   hello ← var:greeting         //   hello defaults to var:hello

etc.

And you can also introduce shortcuts

   scheme:greeter ← ref:https://example.com/ asScheme.
   hello ← greeter:hello-world.txt

Or

   scheme:greeter ← ref:file:./ asScheme
   hello ← greeter:hello-world.txt

Sending -asScheme to a reference is just a shorthand that actually constructs a composition[2] of a "path relative" store with the underlying store of the original reference. So the following two are identical:

   scheme:greeter ← ref:https://example.com/ asScheme.
   scheme:greeter ← #MPWRelativeScheme{ base: 'https://example/com' } → #MPWURLSchemeResolver{} 

This composition mechanism can be carried further with post-processing, so for example an img-scheme can be constructed by composing an image-decoder store with the previous store

   scheme:img ← #MPWImageDecoderStore{} → scheme:greeter 
   helloPic ← img:wave.png 

And so on and so forth, caching is also a nice example.

[1] https://objective.st

[2] https://dl.acm.org/doi/10.1145/3359591.3359729

When models start to effectively employ sarcasm were screwed