Live data from Hacker News

All my new code will be closed-source from now on

twitter.com

101–110 of 118 posts

Re: All my new code will be closed-source from now on

#101
post #91

Earlier quoted context omitted.

Fair enough: the Chinese Marxists seem to love their robots, a lot. But, also, they handle all that automation to the capitalists. Because capitalists are simply much better at doing it. So it seems that, even when it succeeds, socialism can't really get rid of "the system", after all.

The CCP isn't Marxist and doesn't claim to be. Deng basically copied parts of Lenins "New Economic Policy" of "limited capitalism" because he like Lenin realised they'd made a mistake in preempting dismantling of the market, in direct contradiction of the Marxist view that a socialist revolution requires a well developed capitalist economy, and Marx explicit warning against attempting socialism too soon. That's what…

> The CCP isn't Marxist and doesn't claim to be.

This is just adorable!

May I assume that the Cuban, North Korean, Laos and Vietnamese Communist parties aren't Marxist also? Naturally, same goes to former USSR, Khmer Rouge, etc

Re: All my new code will be closed-source from now on

#102
What do we think the future is going to looks like?

"I need a caching component in my stack. Oh, I just let AI create it from scratch, so AI can also run it, maintain it etc."

or

"I need a caching component in my stack. Oh, let me just grab an existing, well maintained and supported cache component and let AI write the glue logic to run it, maintain it etc."

Personally I think it will be the second one. There definitely is a case for generating one off tools but I don't think AI will replace established, well written and maintained software (being it open-source or not).

Not all software is equal. I can get 80% of my new SaaS to be generated by AI as it's mostly considered boilerplate and mostly the same as any other SaaS. It's the 20% that makes it unique OR something that AI can't touch like a special relationship with a supplier or a first to market position etc.

Re: All my new code will be closed-source from now on

#103

Earlier quoted context omitted.

Yeah it can be, but you'd really prefer to know without having to go do an exhaustive search I think. The closer to the root cause you catch the problem the easier it will be to tell what happened. Plus, it's not always easy to run exactly the right tests and to run them at exactly the moment they're needed. I usually won't run the whole test suite on each commit if I'm just doing a rebase, say, but it would still be…

The amount of code changes as seen in a git diff is roughly close to the amount of text changes. So reviewing is scaled linear with the change. In the way your are diffing are there any confounding changes? i.e. I make what seems like a small textual diff but it realigns the whole model of the code base that causes your diff to look like a big chunk of your code base is changed? Maybe that's a good thing? Just thinki…

The methodology is like a codemod or a lint rule. If you've worked with codemods you usually review a combination of the (small) script that describes the intent behind the changes you want and the (larger) diff of (text) changes that were generated by applying the codemod.

Re: All my new code will be closed-source from now on

#104

Earlier quoted context omitted.

So? If some other riser used my code to make money sould I be upset? Isn't it the whole point to me useful to others?

Some AI companies have jobs where human coders solve algo problems for model training. Why not apply directly to those jobs and doing it for free? That would maximize your usefulness to others, would it not? I'm actually asking, that's not a rhetoric question.

It would not, actually, maximize my usefulness to others. They way you do it is making your work maximally available and exapndable so others can build on it. The end result is greater than the sum of its parts. So... open source.

My point is that I don't see a reason why someone making money off my work that I donate should bother me. But again, this is MY stance, clearly it's not an universal outlook. What I wanted to challenge was underlying assumption that someone making money off your code and not giving you any back is a problem or that is _should_ be a problem. It might bother some, but it's not an universal assumption.

Re: All my new code will be closed-source from now on

#106
post #33

Earlier quoted context omitted.

What are some examples of big OSS projects that work with this model? Aka “pay us to get feature X?” It sounds to me that this would invite an insane level of bloat and one-off features.

Igalia, Collabora, Red Hat, GCC, LLVM, Wine, the entire Linux kernel. Tons of open source consulting companies out there working on all kinds of projects.

I don’t think I can pay Linus to implement a specific feature for me. But maybe I just misunderstood and you were talking about consulting only?

Re: All my new code will be closed-source from now on

#107

Tailwind makes more money than ever through donation, but that isn't a business. It's the tailwind proprietary themes that wasn't doing well. It's just bad to say tailwind is losing because of AI.

Tailwind being funded is evidence to me that there’s still far too much money in making software compared to the rest of society, not too little as the author would like us to think.

What does it even mean. It's not funded, companies donate there is a huge difference.

Re: All my new code will be closed-source from now on

#108
post #3

This is a foreign position to me. I open sourced my code not to make money but because I saw that others can benefit from it. I never made money from open source. If I did my mental model would be that these are charitable donations, not an income stream I can rely on.

The post mentions this: > Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. I'm all for non-monetary motives, but the reality is that most people have to work for a living, leaving quite limited time/energy for volunteering. The scale of OSS that we have today would not (perhaps sadly) be possible without OSS development paying the bills.

Wealthy devs context is also foreign to me. I started to open source my code way before I was making any money. I just did it because I saw no reason for it to be closed sourced. It would only benefit me. But in the open it can benefit many people without taking anything away from me.

Re: All my new code will be closed-source from now on

#109

I don't mean to trivialize the OP's experience. This is definitely a very important matter and serious issue in the industry. So forgive me for raising a much smaller, side point. > I've contributed millions of lines of carefully written OSS code over the past decade I have never tracked my own output, but I would be surprised if I have written even a single million lines of code, let alone several. Out of curiosity,…

Side projects on my laptop in one language I use is currently about 200k lines (as measured by "wc -l" so includes blank lines and such). This covers about a decade and a half. This doesn't count all the lines added/changed/removed in the history, a few other languages I use, or anything for work.

Including all those other excluded things, I could see a million per decade across all languages and personal/work projects pretty easily for myself.

Re: All my new code will be closed-source from now on

#110
post #33

Earlier quoted context omitted.

Igalia, Collabora, Red Hat, GCC, LLVM, Wine, the entire Linux kernel. Tons of open source consulting companies out there working on all kinds of projects.

I don’t think I can pay Linus to implement a specific feature for me. But maybe I just misunderstood and you were talking about consulting only?

The vast majority of Linux kernel development is corporations paying devs to implement the features they need. Some of that is in-house developers, some of that is hiring contractors like Igalia or Collabora or many others. That's what I'm talking about.
Post reply on HN