I guess this makes sense for now. You can build integrations leveraging the user's personal access credentials. Later, once Claude takes over the world, they can move sessions to live in their own walled garden.
381 karma · joined September 7, 2021
I guess this makes sense for now. You can build integrations leveraging the user's personal access credentials. Later, once Claude takes over the world, they can move sessions to live in their own walled garden.
What remains in MMOs place are massively singleplayer/co-op experiences. ARC Online, Helldivers, etc.
For a single organisation, a list of vouched users sounds great. GitHub permissions already support this.
My concern is with the "web" part. Once you have orgs trusting the vouch lists of other orgs, you end up with the classic problems of decentralised trust:
1. The level of trust is only as high as the lax-est person in your network 2. Nobody is particularly interested in vetting new users 3. Updating trust rarely happens
There _is_ a problem with AI Slop overrunning public repositories. But WoT has failed once, we don't need to try it again.
https://steve-yegge.medium.com/bags-and-the-creator-economy-...
This tool is dangerous, largely untested, and yet may be of interest if you are already doing similar things in production.
My favourite part of these tools is the zany use of numbered file descriptors. `keypair` outputs the public key on fd 5 and secret key on fd 9. But signing reads the secret key on fd 8, while verification reads the public key on fd 4! Why aren't they the same?? I have to read the manpage every time.
What I want is software that can glue these things together. Each week, announce the fixture and poll the team to see who will play.
So far, the complete fragmentation of all these markets (fixtures, chat) has made software solutions uneconomic. Any solution's sales market is necessarily limited to a small handful of teams, and will quickly become outdated as fixtures move and teams evolve.
I'm hopeful AI will let software solve problems like this, where disposable code is exactly what's needed.
Your consumer/enterprise/industrial framework is orthogonal to the articles focus: how AI is massively reducing the cost of software.
https://gist.github.com/alexjurkiewicz/1abf05f16fd98aabf380c...
"Which poker hand is better: 7S8C or 2SJH"
as
"What is 77 + 19"?
[1] https://bigdatastream.substack.com/p/how-aws-s3-scales-with-...
Maybe software written in the age of DOS was relatively trivial compared to modern tools. Maybe there's a benefit to writing code in Rust rather than C89.
The original article didn't talk about any of these things....
> My son is in school. And the teacher literally said they need to use an LLM otherwise they won’t score high enough because the other pupils are using LLMs and the teacher is using an LLM to grade/check it. This is ridiculous.
Ah. The article's author heard a bad take on LLMs and accidentally attributed it to Ptacek's article.
But if you give this a cool name, it's a New Idea.
I have nothing against Signal implementing screenshot hiding. But it's not exactly fixing a gaping security hole.
You could instead consider:
* How many major version releases / rewrites happen in this language? (This might be a sign of ecosystem instability.)
* How much new code is replacing old code? (This might imply the language needs more bugfixes.)
Better solutions would be things that make the VPN invisible, rather than 'easy'. Tools such as Teleport, IOW.
Until one product becomes clearly better, the code AI ecosystem might just churn and churn and churn.
A consistent structure helps humans parse the output. I have host(1)'s output order in my mental memory.