Both the "user configuration" and the library are configuration masquerading as code. One is dynamically evaluated, the other compiled.

I just figure users of Zed know this... so what are we pretending to talk about?

But I can't wait for the moral panic driving us to all pussy-foot around LLMs to die with prejudice.

Virgins often at some point in their lives assume that not having sex means they have achieved some higher level of self-control, a privileged position upon a high precipice from which they can judge others. They gather, stew, and throw stones at individuals who are going to and fro, living their lives.

Any and every gathering can mob individuals. It is not inherently moral to find yourself in a troupe. You have not reached "consensus" except within a single Discord room, a subreddit, some cesspool of comments on HN. No amount of back-slapping idiocy and corrupt self-evaluation will make any mob any more than just that.

I often say that the difference between an engineer and a mechanic is that the engineer can make a rocket fly the first time (given enough time). Still, good engineers know that time is a trade-off, that exposing errors and motivating problems sooner is very, very worth it. They contain failures. They pull errors forward in time.

But along come those most enabled by LLMs, the idiotic brigades of co-enablers who know only the high quality software made by others. They are experts in what they must be provided in order to open their wallets, and they bring this expertise into the arena of those sharing ideas. Ideas are rough, and idiots are not fond of them.

Lo the brigades demand the engineer never to show them anything that is not perfect. The brigades complain endlessly of laziness while giving no effort themselves. The brigades expect engineers with twenty years of experience make the inefficient time tradeoff of coding everything by hand even before having any idea if what they're building will be wanted by the world.

The brigades want the perfect software, but not the ugly, filthy process from which it is forged. They want it to impress them the first time they see it. They want it to be easy, low-price, available at the push of a button. They want it yesterday and without bugs. Add "Don't use LLMs!" to the list of unreasonable and ignorant demands.

The brigades hate a world where you can't trust a project from its heft and good looking README alone. They hate that what they have never had any interest in reading at all can now no longer be blindly trusted. They hate these LLMs. They hate them, HATE THEM!!! They hate the laziness, the long-winded replies, the hallucinations...

At the culmination of their frustrations, the brigades turn to the engineer with precise instruction: "Give me only the answer. Make no mistakes." We owe these lazy shits nothing.

HN is exaggerating to feel close to the action. It's childish.

There is a trench off of Tokyo that is likely to rupture in our lifetimes, and people who have other people to check on don't care about HN's disaster fantasies.

7 is not really top news of the day.

People with friends and family exposed don't really appreciate being false-alarmed with 7s and 6s.

The reason barking at open source will only get the dog thrown into the river is because there is a whole lot more cumulative power distributed among companies and consumers who don't want two incumbents to dictate which kinds of alternatives can exist.

Note that those rushing to the "all corpos evil" talking points will turn around and advocate delegating these decisions to "the government." This is the same government that they also claim is bought by the corporations. It's also the same government that will enforce the regulatory capture on behalf of the yucky corporation against the broad, diverse interests.

Thinking big vs small while embracing the biggest of the big is some kind of inconsistency that people need to deal with by looking in the mirror and finding some awareness. Nuance. If your problem model is wrong, so is every solution you propose except if your wrong model may get lucky from time to time. Not every broken model is a broken clock. Some broken models cannot admit the right answer ever.

The real dynamic on display here is broad, correlated mass of overlapping interests, big and small. The big pile of people and entities that don't want to be governed by OpenAI and Anthropic can push harder and win the tug of war. You don't have to like your temporary allies all the time, but at least know who they are and when you are aligned.

I think Mozilla is chasing a past formula, but the projection isn't linear enough to remain consistent, and the critical parts of the outcome, utter centralization of the market dominance of the three C's, are left out of the equation.

We might get the consolation prize, a few nerds having competitive alternatives to applaud, but we will be left with the hidden costs: stagnation by bloated market leaders, consumers and businesses pouring trillions of dollars into the commercial offerings while open development wonders where money comes from, and the leakage of these imbalances into political and social spheres.

If we follow a Mozilla template and get to the peak of Mozilla's success at the web, look at what that really is. Facebook, Amazon, Google etc are orthogonal to that equation.

Outside pressure behind much of it.

In any case, there's a fundamental mismatch between pressure groups and the leverage they can exert through single-consensus. I don't know how to describe the other consensus that is on my brain, but it is distinct.

> Then GPL fans can

Checks out

I tire so much of complainers who want someone else to make all their tools infallible yet want to do nothing. Let's just full-stop there. They not only want to avoid working on the tools. They prefer if the tool does everything for them, and they prefer having things done for them without bound.

Complainers want easy APIs. When the API isn't easy enough, they want easy Kubernetes containers "programmed" by YAML. When that isn't easy enough, it's all point-and-click hosted services on GCP and Amazon. You people don't want to program. You want apps. Infallable apps. You want to be consumers, fed from the sky like little birds who endeavor only never to fledge, never to fly. And you want to pay nothing for it.

The secret you people need to figure out is that the lifestyle you think is sustainable is actually a commensal relationship with people building things for you. There is no vast alliance to wrest power from corporations, to dissolve capitalism, no grass roots movement to "shake things up." There is food falling from higher in the water column from an ecosystem filled with people who do things. Those above do not have time to look down, but if they did, all they would feel is overwhelming contempt, so they only look across at the horizon.

But why do people seek to confirm comments like this? Because Rust scary. Churn on, little ant mill. Let be free any who understand the pointlessness of this performance.

After all that, people can talk about averaging methods, but there's a lot to be done before what this blog is talking about is even available.

The reason solving just-in-time rendering is important is because queue priority is not actually supported by most drivers. Some extensions can give us global priority for the process, not real priority for queues. The right way then to avoid workload A from causing workload B to miss a latch is to put workload A into the idle time that would exist from running B just in time. This is itself a luxury based on the fact that workload B is lightweight enough that its own uncertainty can only rarely exceed the latch deadline.

At least on VRR displays, making B a bit late has much less dire consequences, but driving refresh from the application needs exclusive access to the display, and not all compositors want to provide this.

Please do reach out if it seems like I'm only still catching up. I'm sure someone knows a decent way to get sub-millisecond just-in-time rendering accuracy without watching the phase suddenly double on FRR. Ping https://github.com/positron-solutions/mutate and we can get in touch.