5,854 karma · joined April 7, 2015
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.
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.
None, really. Prusa printers are good enough though. If you value freedom and privacy, its worth a few extra dollars.
Perfect, $1mil in salaries to spare the company $500k in spend :)
My version of this:
For my friends, everything; for my enemies, pull security in.
Yes, capturing more shareholder value is a virtue.
I'm not outraged (the intentions were probably good), but I also strongly disagree. Don't touch my config without my consent.
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.
[0]: https://www.ietf.org/archive/id/draft-michel-ssh3-00.html
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.
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.
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.)
tl;dr it will put one package per layer as much as possible, and compress everything else into the final layer. It uses the dependency graph to implement a reasonable heuristic for what is fine grained and what get combined.
This makes no sense. It is possible for a totalitarian government which is threatened by dissent and concepts like "democracy" to also work in the interest of improving overall quality of life.