I tried to open source a weekend personal project while at $BIGCO via their "Invention Assignment Review Committee". It turned into a minor bureaucratic nightmare and I was ultimately never given the OK to release it, or any clarity over whether my employer was choosing to assert an IP ownership interest in it. In retrospect, I wish I had never notified them of its existence, and released it under a pseudonym instead…
Ugh, you gave me bad flashbacks of the same committee. I tried to re-license a previously-released project (like from GPL to MIT or similar) and they wouldn't budge. I had written all the code. In the end, I decided that them suing (or firing) me to assert their ownership of $VALUELESS_PROJECT, so they could then license it back, was ridiculously unlikely, said fuck it, and did it. And I was right.
Ask HN: Have you ever regretted open-sourcing something?
81–90 of 454 posts
Re: Ask HN: Have you ever regretted open-sourcing something?
#82I regret open sourcing an offline patch I made for an Unreal Engine 3 game. The game was unplayable due to an always online backend that got shut down, but was still being sold so I required everyone buy a license to play with my mod. I had to reimplement stock UE3 netcode, and a bunch of other really cool stuff. Someone who was mad at me for not giving them more help when they struggled to develop on my software dec…
I'm very interested in your stock UE3 network code reimplementation, but I understand if you no longer publish these details.
Re: Ask HN: Have you ever regretted open-sourcing something?
#83The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
Re: Ask HN: Have you ever regretted open-sourcing something?
#84The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
Re: Ask HN: Have you ever regretted open-sourcing something?
#85The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
That's just the main idea, but also:
1. LLMs make existing software (even obscure stuff, so long it fits in the context window) more intelligible:
- how do you compile this (when you are inexperienced and the ecosystem of that language is a baroque mess, it might seem impossible)?
- what does this error message mean?
- what parameters do I need to use in my invocation to get it to do XYZ?
- what does this function do? why does it use this algorithm?
2. They also make new software easier to write, and existing software easier to modify:
- ask about anything concerning the part of source code that fits in a context window, and you'll get a (probably correct) explanation of what it does, faster than a half-dead IRC channel or StackOverflow would respond
- the above, but also: the LLM has infinite patience and can drill down as deep as you want. You can ask "OK, but why?" for as long as you want, as about anything you want. You might get a hallucinated answer sometimes, but a frustrated human who would be asked the same way, could also just make something up to shut you up.
- for anything in the context window, ask about how to go about making a functionality change to add or modify a feature
- the above, but if it's small enough, just get the LLM to write the change for you. It might be buggy and messy, but you'll be one step ahead if you lack the skill to make the change yourself
- how do I set up the build chain? Why is my compiler not picking up the path properly? Is the project directory structure wrong? This used to be a huge problem before LLMs, and relied on undocumented knowledge.
---
For me, the whole point of open source is ready-made, (hopefully) not too buggy components that I can use and customise as an end user, or plug into the thing I am building as a developer. LLMs make the freedom of FOSS become much more practical, particularly to those sympathetic to the movement but technically less experienced.
Re: Ask HN: Have you ever regretted open-sourcing something?
#86The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
> The new approach That won't work. The breaking of that model is far more widespread than one thinks because of how it was broken. The breaking of the model breaks underlying models all the way down to the basis for economic distribution of labor. Its a phase change where labor and expertise are free, without restriction and the people with that expertise do not receive economic benefit for it anymore. In short, you…
Better to do that by not sharing how as much (source code), but rather what (interactive demos).
Re: Ask HN: Have you ever regretted open-sourcing something?
#87The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
do you want to give RMS a heart attack?
RMS founded the Free Software movement to protect the users of software.
to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless
ignoring the fact the big philosophical different between Free Software and Open Source, neither had the above as a goal. for the first decade or so of the movement, all Free Software and Open Source development was done by people in their free time. practically none of it was done at work. the exceptions are MIT and BSD projects which both predate the Free Software and Open Source movements.
on other words, developers always had the ability to do stuff in their free time regardless of the license. those that live in countries that allow employers to own everything had to fight their employers to be allowed to do so, and they still have to do that. the cases where employees are getting paid to work on Free Software or Open Source are rare, although they are less rare today than in the past because more companies release their sources. but again, this was not the goal at the founding. at least not that this should help the developers. the goal was always to support and protect the users, to allow them to share and modify the software they use.
Re: Ask HN: Have you ever regretted open-sourcing something?
#88The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
My understanding is that the purpose of Stallman's free software movement is "that the users have the freedom to run, edit, contribute to, and share the software." The FSF is focused on "defending the rights of all software users." Its about the users, not the developers.
Re: Ask HN: Have you ever regretted open-sourcing something?
#89I wrote a network security tool (if you can call a glorified shell script that) and it was used by script kiddies to harass people. It made me feel maybe magicians had something, when they decided some knowledge should be esoteric and earned, given that it was so trivial I never listed it on my CV. I think infosec, as a field, sometimes darts between too much obscurity and too much openness.
Re: Ask HN: Have you ever regretted open-sourcing something?
#90The purpose of Stallman’s open source movement was to redistribute power back into the hands of creators who were getting walled out of anything but proprietary work for an employer. If they were fired, they had nothing to show for years of work except a reference, since their deep expertise was essentially meaningless. (An experience I’m sure almost everyone here is familiar with, since we’ve all spent some years on…
I see what you mean, but this knife cuts both ways. It makes proprietary software easier to write by extracting knowledge from open codebases, but it also makes open source software easier to write by extracting knowledge from those same open codebases. That's just the main idea, but also: 1. LLMs make existing software (even obscure stuff, so long it fits in the context window) more intelligible: - how do you compil…
BTW most business-astute maintainers always managed a closed piece of expertise which is what they charged for. I’m saying that proportion needs to grow now.