Live data from Hacker News

The fate of "small" open source

nolanlawson.com

201–210 of 238 posts

Re: The fate of "small" open source

#201
> it’s a future where we prize instant answers over teaching and understanding

It doesn't have to be this way- coupled with verification (to mitigate hallucination), llms can help so much with personal education.

It's a purely judgement free environment and for a lot of people that's incredibly meaningful.

Re: The fate of "small" open source

#202
post #4

Earlier quoted context omitted.

But some webdev said they are 10x faster now so it cant be bad for humanity /s

They must be slackers, I heard from multiple sources that AI makes you a 100x developer.

So this is why all the leading AI companies normalize 72 hour weeks.

Re: The fate of "small" open source

#203

Given that some 80% of developers are now using AI in their regular work, blob-util is almost certainly the kind of thing that most developers would just happily have an LLM generate for them. Sure, you could use blob-util, but then you’d be taking on an extra dependency, with unknown performance, maintenance, and supply-chain risks. Letting LLM write utility code is a sword that cuts both ways. You often create a th…

This mostly sounds like a good thing to me from a utilitarian standpoint. Getting all your utility classes from somewhere like npm and creating dependencies on 20 different people and organizations who may or may not maintain their software has been a security nightmare with many highly public examples. If a LLM writes a utility class for me then my supply chain is smaller, meaning less surface area to attack plus I…

Your supply chain is superficially fewer, but not smaller. The way you're counting the number of suppliers is heterogeneous: ChatGPT has a bigger surface area than 20 individuals.

Re: The fate of "small" open source

#204

Earlier quoted context omitted.

I think you have some of your wires crossed, asking Google for "here's the type of message that the author of this page is trying to convey" is not what most people think is a simple question (also asking Google to reprint copyrighted material us also a non starter). Asking Google "what is the flag for persevering Metadata using scp" and getting the flag name instead of a SEO article with the a misleading title go on…

"here's the type of message that the author of this page is trying to convey" is not what most people think is a simple question It's also not the question I asked. I'm literally trying to parse out what question was asked. That's what makes AI slop so infuriating: it's entirely orthogonal to the information I'm after. Asking Google "what is the flag for persevering Metadata using scp" and getting the flag name inste…

At least with Google, it quotes the pages where it gets the information from. Also, I think you are definitely underplaying the fact that it answers the question in one sentence,as wellas the whole ask a question get a compact answer. I am going to need a concrete example, because in my experience, the AI summary has never even required me to verify the source except out of curiosity, much less click on any search results.

Re: The fate of "small" open source

#205
post #202

Earlier quoted context omitted.

They must be slackers, I heard from multiple sources that AI makes you a 100x developer.

So this is why all the leading AI companies normalize 72 hour weeks.

Code reviews when generating 100x lines of code must be tiring.

Re: The fate of "small" open source

#206

Earlier quoted context omitted.

This mostly sounds like a good thing to me from a utilitarian standpoint. Getting all your utility classes from somewhere like npm and creating dependencies on 20 different people and organizations who may or may not maintain their software has been a security nightmare with many highly public examples. If a LLM writes a utility class for me then my supply chain is smaller, meaning less surface area to attack plus I…

Your supply chain is superficially fewer, but not smaller. The way you're counting the number of suppliers is heterogeneous: ChatGPT has a bigger surface area than 20 individuals.

Your supply chain is smaller in the sense that every person or organization you obtain code from is similar to a vendor, just an unpaid one. They are a separate entity your business depends on.

If we replace code written by 20 of those organizations with code written by ChatGPT, we've gone from 20 code "vendors" we don't know much about who have no formal agreement to speak of with us, to 1 tools vendor which we can even make an enterprise agreement with and all that jazz.

So whatever else the outcome may be, from this perspective it reduces uncertainty to quit using random npm packages and generate your utility classes with ChatGPT. I think this is the conclusion many businesses may reach.

Re: The fate of "small" open source

#207

Earlier quoted context omitted.

This is an AI issue because people, including the developers of AI tools, don't care enough. The Tragedy Of The Commons is always about this: people want what they want, and they do not care to prevent the tragedy, if they even recognise it. > Project owners should instead be working ways to filter out careless code more efficiently. Great. So the industry creates a burden and then forces people to deal with it — I g…

We don't need an AI detector, we need a "human vetted" detector.

People arguing against my point here seem to be doing a good job of validating my point.

Re: The fate of "small" open source

#208

Earlier quoted context omitted.

Your supply chain is superficially fewer, but not smaller. The way you're counting the number of suppliers is heterogeneous: ChatGPT has a bigger surface area than 20 individuals.

Your supply chain is smaller in the sense that every person or organization you obtain code from is similar to a vendor, just an unpaid one. They are a separate entity your business depends on. If we replace code written by 20 of those organizations with code written by ChatGPT, we've gone from 20 code "vendors" we don't know much about who have no formal agreement to speak of with us, to 1 tools vendor which we can…

What enterprise agreement would you make with OpenAI that would make you feel better about the supply chain? Seems to me you just get stochastic output that may or may not be battle tested level code, without guarantees either?

Re: The fate of "small" open source

#209
Node.js's core library is purposefully minimal. Purposefully or not, it's still an issue. Wether you add many small things to your project using an LLM or NPM, it still requires work and the annoying thing is that you'll have to do it for every new Node.js project.

Node.js is very good for IO and it has decent performance even for CPU-intensive work considering it's a dynamic language, but it would sure be nice to have a rich core library like Ruby or Clojure has.

The fact that ClojureScript can do it proves that it's doable even for front-end javascript (using advanced optimisations).

Re: The fate of "small" open source

#210

Earlier quoted context omitted.

> or a spammer where your incentives have probably increased. Slight pushback on this. The web has been spammed with subpar tutorials for ages now. The kind of medium "articles" that are nothing more than "getting started" steps + slop that got popular circa 2017-2019 is imo worse than the listy-boldy-emojy-filled articles that the LLMs come up with. So nothing gained, nothing lost imo. You still have to learn how to…

The problem isn't that AI slop is doing something new. Phishing, blogspam, time wasting PRs, website scraping, etc have all existed before. The problem is that AI makes all of that far, far easier. Even using tooling to filter articles doesn't scale as slop grows to be a larger and larger percentage of content, and it means I'm going to have to consider prompt injections and running arbitrary code. All of this is a r…

> The problem isn't that AI slop is doing something new. Phishing, blogspam, time wasting PRs, website scraping, etc have all existed before. The problem is that AI makes all of that far, far easier.

The term I like is that AI has _industrialised_ those behaviours. While native hunted buffalo, it wasn't destructive until it was industrialised [1] it that it became truly destructive.

[1] https://allthatsinteresting.com/buffalo-slaughter

Post reply on HN