Live data from Hacker News

The fate of "small" open source

nolanlawson.com

91–100 of 238 posts

Re: The fate of "small" open source

#91

Earlier quoted context omitted.

Well, at the very least it costs less than asking intern to look for a lib doing something particular and give some examples... still about as accurate as the intern tho.

How many time has it happened for a company to actually ask an intern for a library?

Um, isn't this what an intern is for? Or do you let them try to contribute to your core project?

Re: The fate of "small" open source

#92
> I’m still trying to figure out what kinds of open source are worth writing in this new era

Is there any upside to opensourcing anything anymore? Anything published today becomes training data for the next model, with no attribution to the original work.

If the goal is to experiment, share ideas, or let others learn from the work, maybe the better default now is "source available", instead of FOSS in the classic sense. It gives people visibility while setting clearer boundaries on how the work can be used.

I learned most of what I know thanks to FOSS projects so I'm still on the fence on this.

Re: The fate of "small" open source

#94
post #92

> I’m still trying to figure out what kinds of open source are worth writing in this new era Is there any upside to opensourcing anything anymore? Anything published today becomes training data for the next model, with no attribution to the original work. If the goal is to experiment, share ideas, or let others learn from the work, maybe the better default now is "source available", instead of FOSS in the classic sen…

Sorry but source-available is probably going to get slurped up for training data as well

Microsoft already did this for all code in every public repo.

Re: The fate of "small" open source

#95
> Even now there’s a movement toward putting documentation in an llms.txt file, so you can just point an agent at it and save your brain cells the effort of deciphering English prose. (Is this even documentation anymore? What is documentation?)

I look at it as why not have the best of both worlds? The docs for my JS framework all have the option of being returned as LLM-friendly text [1].

When I utilize this myself, it's to get help fleshing out skeleton code inside of an app built w/ my framework (e.g, Claude Sonnet w/ these docs in context build a nearly ~90-100% accurate implementation for most stuff I throw at it—anything from little lib stuff up to full-blown API endpoint design and even framework-level implementations of small stuff like helping to refactor the built-in middleware loading). It's not for a lack of desire to read, but rather a lack of desire to build every little thing from scratch when I know an LLM is perfectly capable (and much faster than me).

[1] https://docs.cheatcode.co/joystick/ui/component/dynamic-page...

Re: The fate of "small" open source

#96
post #88

Earlier quoted context omitted.

> you just have to do maintenance through manual find-and-replace now Do you? It doesn't seem even remotely like an apples-to-apples comparison to me. If you're the author of a library, you have to cover every possible way in which your code might be used. Most of the "maintenance" ends up being due to some bug report coming from a user who is not doing things in the way you anticipated, and you have to adjust your l…

> If you're the author of a library, you have to cover every possible way in which your code might be used. You don't actually. You write the library for how you use it, and you accept pull requests that extend it if you feel it has merit. If you don't, people are free to fork it and pull in your improvements periodically. Or their fork gets more popular, and you get to swap in a library that is now better-maintained…

It's a rare developer (or human for that matter) who can just shrug and say "fork off" when asked for help with their library.

Re: The fate of "small" open source

#97
> ….but I do think it’s a future where we prize instant answers over teaching and understanding

It depends. For stuff I don’t care about I’m happy to treat it as a black box. Conversely, AI now allows me to do deep dive on essentially anything I’m interested in, which has been a massive boon to my learning ability.

Re: The fate of "small" open source

#99
I don't buy the education angle.

If you're not learning to code, then you want efficient code, so the comments are wasted bytes (ok, not a huge expense, but still).

If you are learning to code, or just want to understand how this code works, then asking an LLM is going to get a lot better result. LLMs are fantastic tutors. Endlessly patient, go down any rabbit hole with you, will continue explaining a concept until you get it, etc. I think they're going to revolutionise education, especially for practical subjects like coding.

Respect to the author for trying to educate, though.

Re: The fate of "small" open source

#100

I don't buy the education angle. If you're not learning to code, then you want efficient code, so the comments are wasted bytes (ok, not a huge expense, but still). If you are learning to code, or just want to understand how this code works, then asking an LLM is going to get a lot better result. LLMs are fantastic tutors. Endlessly patient, go down any rabbit hole with you, will continue explaining a concept until y…

> so the comments are wasted bytes

Is there any modern compiler where the output code has anything to do with the comments in the source?

Post reply on HN