whimblepop

https://github.com/numtide/llm-agents.nix/

As a result, I never knew that Claude Code does a nasty thing like this, either. :-\

Fwiw, packages in that repo get version bumped each day, so if that's a fast enough pace for you it may be a good alternative.

  [features]
  daemon_auto_start = false

--

1: https://github.com/openai/codex/blob/0c329ad2c9d5a2592128a1d...

Many F/OSS maintainers care pretty deeply about things like software freedom, taking good care of our digital commons, and leaving their mark on the world in a public way. I imagine that's especially true at Red Hat. You can buy the company, you can change the relationship to the community of "outside" contributors, and you can even release new versions of the software under a proprietary license. You can create upheaval for a lot of people, including the users. But you will often not only fail to walk away with key maintainers on your team, but watch them go on to form your competition on a new fork.

I don't personally know anyone who works at Red Hat, but even from the interactions I've seen recently in issue trackers and PRs to projects maintained in part by Red Hat engineers, I'm inclined to have a bit of faith. The upstream-first culture there still seems pretty strong and pretty quality-oriented to me. I don't think you can reliably keep engineers like that and turn them into drones who don't care about the craft and their impact on users and developers.

Then, if the project lives and grows long enough to be published, you start soliciting involvement from human artists but with minimal budgetary commitments. If your project gains momentum, you start allocating more realistic incentives for human collaborators.

And Emacs is strictly more powerful than Vim. :)

(I mean that seriously, actually— I don't think people who have used both but prefer Vim would generally list "more powerful" among their reasons for preferring Vim. It's usually more about not liking Lisp, some kind of "minimalism", or a different sensibility about composability.)

> In the coming weeks, we will relicense all of our source-available tools, including Tart, Vetu and Orchard under a more permissive license. (HN discussion: https://news.ycombinator.com/item?id=47730194)

In this case they moved from one source-available license (Fair Source License v0.9 with seat restrictions) to another (Fair Source License 1.1-ALv2 without seat restrictions), with the same sort of restrictions on field-of-endeavor as before.

Why they've chosen this isn't super clear, as (1) there are already open-source alternatives that use the same storage formats as Tart, like Lume[2]; and (2) Tart is certainly already in the training sets of all of OpenAI's "direct competitors", who are practically held back little or not at all by the restrictions of the FSL. The only entities this really restricts are F/OSS distributions which might otherwise include Tart as a first-class package in their distros. :-\

--

1: https://web.archive.org/web/20260412071019/https://cirruslab...

2: https://github.com/trycua/cua/tree/main/libs/lume

> You can always ask me for feedback on your homework and I will mark up every part of it, but you won't receive a grade for homework. However, if you don't do the homework and take your time with it, you will fail the class. My office hours are in the syllabus and you're strongly encouraged to use them. There will be an early exam to give you a chance to know whether you are likely to fail this class before you lose your chance to drop it.

Correctness is harder to adjudicate in some humanities disciplines but the format of these exams is actually not super different from essay tests (when a math professor grades a proof, they're inspecting specialized prose for validity, coherence, persuasion in a way that also reveals knowledge).

When you don't rely on homework for determining whether or not a student passes the class, you make cheating on the homework into the student's problem instead of the professor's or the university's. Students have the right incentives to solve problems for which they are the ones responsible, and they figure it out after one failed (or ideally, dropped) class at worst.

Moreover, both of those questions are separate from questions that get at what IQ measures (does it measure aptitude, does it measure factual knowledge, does it measure social knowledge or acculturation within a specific context, etc.).

Lots of things are easy to identify as both substantially genetically determined and variable over time and mediated by environmental factors, e.g., height. Lots of things are likewise easy to identify as significantly environmentally determined but also largely stable over time if not altogether fixed (e.g., personality, attachment styles).

It's also at least possible for all of the following to be true at the same time:

  - IQ tests correlate with socioeconomic status
  - IQ test scores vary over time and can be increased
  - some IQ score increases, or some part of a given IQ score increase, reflects a genuine aptitude increase
  - IQ tests are somewhat gameable in that training for IQ tests can increase scores so that some of the measured increase does not measure improved cognitive ability

Besides, high-IQ students can still underperform for many of the same reasons that average-IQ students often do (e.g., under-preparation, lack of discipline, disorganization, mental illness, financial distress, unstable living situation). We should be better addressing those things before students get to a university no matter what their IQ is.

Beyond that, if you have good competency tests on both ends (i.e., the credentials before a four-year degree are accurate signals, and university degrees effectively prove a high degree of competency), who cares if someone manages to get those credentials by working harder while being dumber? I like working with clever people. I also like working with people who know their shit because they take their time to study and consider things. (When I'm lucky, I get to work with people who are both!)

The average university attendee's IQ is virtually indistinguishable from the average person's IQ.

People don't go to college because they're smart. They predominantly go so they can earn more money and/or work more enjoyable jobs when they graduate. Being smart isn't the main reason that adults encourage teenagers to pursue college either. It's mostly a matter of class reproduction; it's the "default" for anyone whose parents are college graduates.

And failing out once you get to the university isn't generally an IQ issue, either. Mediocre and slightly stupid people graduate from universities with degrees they've earned fair and square every year. You don't have to be smart to finish a degree. You do have to be reasonably prepared, and that's the primary issue.

Again, I love the ambition of the Asahi project and what they've done. They're impressive hackers, and thousands of people will doubtless get years of happy Linux life out of their work— maybe including me! I have no complaints for them, and no wishlist I want to bring to them. In fact, I think maybe I should send them a donation or a kind email or both upon their next release.

But I want to give the bulk of my financial support to a computer vendor who offers me first-class, day-1 support for software environments that make me feel happy and respected. The Asahi team can't turn Apple into that by themselves.

But I'm still excited about the Framework 12 because I don't love macOS. I don't need an alternative to beat Apple on every line of the spec sheet. I just need them to align with my values, support Linux well, and cross a certain "good enough" threshold. The latest laptops from Framework meet all of those requirements, and I'm excited to buy one after I've saved up enough money. I've missed Plasma for a long time. At the same time, I wouldn't even consider a MacBook Neo.

  rm -rf node_modules && npm install

Anyway you should generally run `npm ci` except when you're deliberately updating your actual dependencies. I'd only permit an `npm install` if I was adding or updating a dependency, or I'd just reviewed an `npm ci` failure.

It was like this in the days when the primary shortcut was StackOverflow as well. People who are allergic to RTFM treat things that are covered in the docs as "esoteric" knowledge because they never read anything except as a shortcut to solving their immediate problem.

I think the stats are clear that reading is in decline in general, though. I'm sure LLMs will add to this much like YouTube has.