hamandcheese

and not purchase any more.

why would anyone sign such a contract?

Is Claude's paraphrasing of Lord of the Rings equivalent to the original?

Cheap tokens only benefits SaaS that depends on AI. Otherwise, cheap tokens means it is only more cost effective than it already is to cut out the SaaS and build instead of buy.

OpenRouter doesn't fail over to a different model, it fails over a different provider of the same model.

A lot of my PRs are the result of hours of back and forth between an AI and myself. In many cases the sum total of my prompts is much larger than the final output.

where’s all this new magical software that the productivity improvements should imply?

It's running, privately, in my homelab.

I think we are entering what I call the "have it your way" era. If an open source project doesn't do exactly what you want it to do, fork it, or create a new version. It's too easy.

This makes me a bit concerned about the future of open source. Upstreaming used to be worth it, since maintaining a fork is effort too. But now the balance has shifted significantly. Especially with many projects becoming a lot stricter about contributing, and some becoming outright hostile to AI. I can't blame them. But I think the effect will be that improvements are less likely to make it back to the community as AI adoption increases.

I highly recommend Workers for Platforms for anyone wanting to deploy vibecoded apps: https://developers.cloudflare.com/cloudflare-for-platforms/w...

The issue that I foresee is that the point of error becomes decoupled from the UI and the UI doesn't handle a delayed error. Especially if retrofit into existing products.

I worry that optimistic updates is going to become trendy and applied to more software, but without any plan for the "sad path" - failed to sync, sync conflict, etc. Get ready for a whole new era of race conditions and frustration!

From experience: I work on a small team maintaining build infrastructure for my entire company. My goal, as much as possible, is to maintain a single build environment that can serve all purposes.

But it has proven quite the challenge to support old Linux distros. We have tried using nix to pin deps, but this easily leads to new issues: hardcoded RPATHs leaking into binaries, glibc compatibility issues, etc.

If we instead fork the build environment and use an old Ubuntu for building our Linux app, then my life gets harder, because now I have two targets for a whole lot of internal tooling that my team maintains, and that tooling needs to be deployed to both build environments. Again, its the same shit: glibc mismatches, missing/different shared libraries, etc. Just causing problems in a different place.

There is certainly some element of skill issue at play. But I wouldn't call it easy.

Couldn't the need for Zones have been solved with ARP-like probing? I.e. if you don't know on which interface to route a link local address, try pinging the address from each interface, and see which one responds.

Has wealth been distributed from exploiter to exploited? Doesn't seem like it. It just seems like the 99% are being exploited a little more evenhandedly.

It is my right to do with my printer whatever I want.

What printers are similarly priced and have similar specs, for someone relatively new to 3D printing?

None, really. Prusa printers are good enough though. If you value freedom and privacy, its worth a few extra dollars.

I do not want to be in a business relationship with a company for a trivial amount of money, be it $29.99/yr or $69.99/yr or $249.99 lifetime. None of that is real money. You have no leverage, you do not own your own destiny. Complaining about the price hike is missing the whole point - Plex does not care about any individual customer, and that's the real problem (and the problem with just about every B2C business).

They would do small PoCs, do comprehensive benchmarks and evaluations of those PoCs, and decide whether to actually go ahead

Perfect, $1mil in salaries to spare the company $500k in spend :)

Is lakeFS an FS....? Zero mention of FUSE or a kernel module at all in the README.

The corollary to that is a clever bureaucrat can kill a proposal simply by inviting many decision makers to a meeting.

My version of this:

For my friends, everything; for my enemies, pull security in.

Tesla is doing something right

Yes, capturing more shareholder value is a virtue.

but the action itself is reasonable.

I'm not outraged (the intentions were probably good), but I also strongly disagree. Don't touch my config without my consent.

This matches my experience. Keychain + fully unattended increases the complexity and adds a bunch of landmines that need to be dodged (e.g. GUI prompts like you mentioned).

And in 2026 it starts at $599.

it'll translate to doctors seeing more patients.

This is also a good thing. Even in supposedly developed parts of the world like San Francisco it can be difficult to find a PCP that is taking new patients.

Scoring 0, 1, 2, 3, or 4 all say better than 32% of players. Something isn't right.

unless you turn off your brain

This would be a great use case of SSH over HTTP/3[0]. Sadly it doesn't seem to have gained traction.

[0] https://www.ietf.org/archive/id/draft-michel-ssh3-00.html

Each agent is a TOML config with a focused job. Such as code reviewer, log analyzer, commit message writer. You can run them from the CLI, pipe data in, get results out.

I'm a bit skeptical of this approach, at least for building general purpose coding agents. If the agents were humans, it would be absolutely insane to assign such fine-grained responsibilities to multiple people and ask them to collaborate.

what's the difference if my agent uses fucking Next, Nuxt, Rails or Django?

The claim seems quite clear to me: "convention over configuration allows coding agents to be more effective".

But yes, I do agree that the main line should say what Ruby on Rails actually is, not why it's good for your agent.

Cloud challenges can be as or more complex than bare metal ones.

Big +1 to this. For what I thought was a modest sized project it feels like an np-hard problem coordinating with gcloud account reps to figure out what regions have both enough hyperdisk capacity and compute capacity. A far cry from being able to just "download more ram" with ease.

The cloud ain't magic folks, it's just someone else's servers.

(All that said... still way easier than if I needed to procure our own hardware and colocate it. The project is complete. Just delayed more than I expected.)

I don't in ow if I'd say it's "easy". The Python ecosystem in particular is quite hard to get working in a hermetic way (Nix or otherwise). Multiple attempts at getting Python easy to package with Nix have come and gone over the years.