| > The closer reads like people might've made the right call refusing the engagement. I think there's enough history of my contributions to various open-source projects over the past ~20 years to serve as evidence that I go pretty far out of my way to be accommodating to projects that are open to contributions. > It also reads like a refusal of true disengagement. I'm not sure what "refusal of true disengagement" means. My goal is generally to accomplish something like building a piano recital scoring app, or being able to run an old game on my laptop. There's a few dozen steps needed to achieve that, which incrementally go down the stack until it encounters a library that works well enough that I don't need to debug it. Sometimes this is a very short list -- I've been amazed at how well the Vulkan ecosystem works, ditto the Go stdlib and the major Go ecosystem libraries. But sometimes it's like falling down a ladder, hitting each rung on the way down, in which case I turn to an LLM to make the ladder go away. A lot of C projects seem to be like this -- it's a conservative choice of language in general, for people who saw the rise of C++/Java/C#/Go/Rust/etc and decided to skip them, so the attitudes and tooling are likewise conservative. > Maybe you can now work on that, given that your profile says you're retired? Being retired means that I want to spend more time doing fun things and less time arguing about file descriptor lifetimes on mailing lists. |
| |
| ▲ | hypfer 3 hours ago | parent | next [-] | | Yes, sure, but the initial comment is still full of vitriol, and that's why I said what I said. > I'm not sure what "refusal of true disengagement" means. It means not being mad anymore at the people and "showing them" by using LLMs to the degree where one feels the need to rant on about their perceived bad decisions on HN. I _suspect_ you might not be able to fully turn that off, as it sounds like spite might be a driving force. And that's good, but also, you've kinda made it?
So if anything, you could probably be happy that you're retired and that you do not have to have these discussions anymore. And maybe also see that the people probably did their best. Which may or may not have been very good, but they did so nonetheless. | | |
| ▲ | jmillikin 3 hours ago | parent [-] | | > but the initial comment is still full of vitriol
If you think this comment is full of vitriol then you should try reading the kinds of emails people send to mailing lists. > It means not being mad anymore at the people and "showing them" by
> using LLMs to the degree where one feels the need to rant on about
> their perceived bad decisions on HN.
I think you're reading things into my comment that aren't there.HN is full of threads lamenting that projects are seeing a decline in community interaction and contributions because LLMs let people vibe-code whatever software they want. I hesitate to use the word "universal", but there's definitely a strong feeling that greenfield LLM-generated projects are in some sense stealing effort or attention that could be put toward an existing project. I'm sympathetic to that claim on the surface, but the actual experience is that a lot of projects have only had that sort of interaction in the first place because the maintainers forced it as a pre-requisite to getting a patch accepted. There's some 30 kLoC library out there that decodes an obscure audio codec, it almost works but you need to add some #ifdefs or whatever so it builds on Clang. The would-be user has to mentally prepare themselves for the next few weeks (or months!) of trying to cajole the maintainer into accepting their patch. And maybe it's never accepted, and now you're stuck, and that project goes into the shelf forever. The article acts as if people with LLMs are the ones whose behavior needs to change to be more pro-social, but from my perspective its the maintainers' attitude that needs to change (if they want their project to continue receiving attention). There's no reason to put up with a maintainer's dictatorial control over a project any more, because the value of code itself is plummeting to epsilon. > And maybe also see that the people probably did their best. Which may or
> may not have been very good, but they did so nonetheless.
Outcomes have never been judged by whether someone has done their best, but whether they have done well. | | |
| ▲ | hypfer 3 hours ago | parent [-] | | > Outcomes have never been judged by whether someone has done their best, but whether they have done well. Yes but FOSS is primarily about the journey, actually. You can (and probably should, if you want to get things done) judge the outcomes and plan accordingly, but it's just people doing stuff in their free time. That cannot be measured purely with the measuring stick of the general market. Yes, this also means that a lot of it will be complete garbage, but that's fine and nothing to be upset about. At least beyond general disappointment with the lack of skill and sense of an average human. That's my point. |
|
| |
| ▲ | s3graham 2 hours ago | parent | prev | next [-] | | > less time arguing about file descriptor lifetimes on mailing lists. Hey, I'm retired too, we can argue about that here! After working in the open for ~15 years, and generally being enthusiastic about collaborating and making shared common base-level tech internally at companies, I'm finding it shocking how much I don't want to even bother pushing projects to a public repo. Never mind doing any sort of releasing, contributing, "marketing", maintenance, patching, etc. | |
| ▲ | zahlman 2 hours ago | parent | prev [-] | | > I think there's enough history of my contributions to various open-source projects over the past ~20 years to serve as evidence that I go pretty far out of my way to be accommodating to projects that are open to contributions. I mean, signing email and avoiding HTML sound to me like pretty trivial accommodation. And you only have to set up GPG once; it's not as if all these projects have their own mutually incompatible security/privacy/anonymity schemes. |
|