HomeVideos

The Codeberg Situation | TheStandup

Now Playing

The Codeberg Situation | TheStandup

Transcript

1132 segments

0:00

Welcome to the standup. Today I have

0:01

with me Teach TV Trash Dev and Casey

0:04

Miratory, legendary game dev and snack

0:07

influencer. And we are going to be

0:08

talking about Codeberg today.

0:14

Uh anyways, sorry for those that are not

0:16

familiar. Codeberg is an online code

0:19

hosting platform with a focus on free

0:21

and open-source software. It is part of

0:23

their mission. A big part of their stuff

0:25

is that people who open source their

0:27

code should have a extremely permissive

0:29

license for everybody to be able to

0:31

enjoy and bask in the glories of

0:33

open-source software. Uh with that said,

0:37

there's been a recent proliferation of

0:39

LLM generated code in which is putting

0:41

strain on anyone that hosts code, i.e.

0:44

GitHub. GitHub has had a lot of issues

0:46

and I think we're all familiar with

0:47

GitHub's issues. Well, recently Codeberg

0:50

came out and said they will no longer

0:52

allow mostly vibecoded projects to be a

0:57

part of codebergonline.net.

1:00

Right? So, you can no longer host your

1:02

vibecoded stuff on code. They gave a

1:04

whole series of reasons as to why and

1:06

that is what we're going to discuss

1:08

today. Is co is this a good move by

1:11

Codeberg? Are we happy with it? Uh will

1:13

this work out for them or is this

1:16

terrible? All right. So, there we go. So

1:17

this is the addendum that they made. You

1:20

must not share projects that mostly

1:21

consist of code written by generative AI

1:24

tools including services such as claude

1:27

open a uh open AAI codecs. Such projects

1:30

have unclear copyright status. See the

1:32

requirements in section 211 section 213

1:35

and furthermore have little safeguards

1:37

to ensure that they do not include

1:38

harmful code. Those other sections just

1:41

uh they're just directly above saying

1:43

like hey we have certain standards. We

1:45

want certain things to be uh uh like if

1:47

you are posting a project, we want it to

1:49

be this type of permissive license. You

1:51

cannot guarantee that by having an LLM

1:53

is what they're effectively attempting

1:54

to say. So this is the line that caused

1:56

the controversy that everybody is

1:58

freaking out about. Okay, we're getting

2:00

a 504. So they might actually like they

2:02

might be getting hammered right now. Oh

2:04

yes, yes, we got it. And so they also uh

2:07

posted a blog post and they had a nice

2:10

little image right here which it looks

2:11

like they've also just recently deleted

2:13

which is super unfortunate because it

2:15

was right here within the first couple

2:17

but it showed the actual voting um it

2:20

showed the actual voting. So that has

2:21

been somehow removed or changed. But the

2:24

voting goes that 2/3 of all Codeberg

2:27

people supported the no LLM policies,

2:29

whereas about 1/3 said, "Hey, we don't

2:32

support the LLM stuff. You should be

2:33

able to have LLM projects."

2:36

>> I could be misremembering, but I'd add

2:37

one caveat to that, which is it wasn't

2:39

2/3 of Codeberg people. It was 2/3 of

2:42

people who voted, which is 50% of

2:44

codeberg people. So it's kind of 2/3 of

2:46

50% if you

2:48

>> Yes. Yes. Sorry. It was it was of the

2:50

yes the voting class of codeberg because

2:52

there is two different classes of

2:53

codeberg. There's the you know people

2:55

that can just host a small project and

2:57

of course the people that are members

2:58

that are involved that have voting

3:00

rights and all that. So that that side

3:01

of things

3:01

>> well I mean I think it's 50% of the like

3:03

it's they were talking about how many

3:04

people participated which may just be

3:07

people didn't vote like you know you had

3:09

rights to vote but didn't vote. I don't

3:10

know. Like I'm just saying they they

3:12

were sort of it was not clear exactly

3:14

how many people out of all of the people

3:16

it was. But just a slight caveat.

3:18

>> Here we see the elusive programmer. A

3:21

simple creature that spends [music] most

3:22

of its time working alone, often in

3:24

darkness. But what's this? Someone being

3:27

wrong on the [music] internet. Our coder

3:28

springs into action, reaching top speeds

3:30

of 120 words per minute before flash. A

3:32

light mode website. The natural enemy of

3:34

these code lovers [music] stuns our

3:36

friend. The chase is called off. We'll

3:38

have to get them next time.

3:41

When not on their computers, they can

3:43

spend [music] hours drawing crude

3:44

symbols on something they call

3:45

whiteboards. Researchers have discovered

3:47

thousands [music] of dialects, often

3:49

with more than a dozen used in a single

3:51

office. However, [music] no linguist has

3:53

yet deciphered what their purpose is.

3:58

Vein creatures, their bodies have

4:00

evolved over a millennia to be able to

4:01

sit in unusual postures while looking at

4:03

themselves online. This will often last

4:05

for many hours using the excuse they're

4:08

waiting [music] for code review,

4:09

depressed to why they're so inactive.

4:12

And finally, after a long day of

4:14

accomplishing very little, our keyboard

4:15

warriors [music] ready for bed. Quick

4:17

read and it's lights out.

4:20

Good night, little coder.

4:24

So, how do I sleep so well at night?

4:27

Well, I have Sentry to help me crush

4:29

those bugs. And I'm not I'm not talking

4:30

about like little teeny tiny South

4:31

Dakota bugs that die in the winter. I'm

4:34

talking about big mean jungle bugs and

4:37

I'm not scared of any of them by the way

4:39

just but I can squash those bugs with

4:43

seer by century. Their blog post went on

4:45

and shared several points about what

4:47

exactly uh is their reasoning behind and

4:50

a few of the big reasons of course is

4:52

that LLM put a natural strain on

4:54

hardware costs. So, the replacement of

4:56

their hardware and them being fully

4:57

self-hosted is being directly impacted.

4:59

Going from 700 non-freedom units, euros

5:02

to 3500s for a uh SSD is directly

5:06

impacting how much uh hardware they can

5:08

buy. That's realistic. Second, it

5:10

impacts actual infrastructure because

5:12

there's a higher rate of commits, more

5:14

code being generated, more of the

5:15

platform is being used by these uh by

5:17

people who can just generate huge

5:19

amounts of code and it's largely

5:21

untouched. Their big argument was that

5:22

you have a single piece of code which is

5:24

tens of thousands or hundreds of

5:26

thousands of lines long and it's just

5:28

one person interacting with it. Whereas

5:30

something like say Ghosty or some other

5:31

project that's hosted on Codeberg, they

5:33

have tons and tons of people interacting

5:35

with it. It creates a very healthy

5:36

community. And so it's like

5:38

disproportionately costing them more for

5:40

something that creates no community. And

5:41

so they're like, we don't really like

5:43

that. And then thirdly, they said, hey,

5:45

the copyright status, we don't really

5:46

know about that. And then fourth, they

5:48

said, hey, we really don't like

5:49

single-use software. Meaning like you

5:50

shouldn't generate something for your

5:52

exact need. Instead, it should be built

5:53

upon something that a bunch of people

5:55

should be able to have benefits and

5:56

that's kind of the hosting or style they

5:58

wish to have on their platform.

6:01

So I I believe I have given the the

6:03

rough outline as to everything. There's

6:06

also a very lengthy blog statement um

6:09

which is called protecting our floss

6:11

commons from LLMs

6:14

that was posted um here and you should

6:17

have the link to that because that's

6:18

pretty helpful because it kind of goes

6:20

through all of the

6:21

>> issues that they were concerned about

6:23

and kind of explained their goals which

6:25

is pretty important to understand like

6:27

the motivation of a terms of service

6:28

change obviously. So that was pretty I I

6:31

found that pretty helpful to just like

6:33

know why they were doing it, right? Um,

6:35

>> yep. I tried to explain most their

6:36

reasons. That's where

6:37

>> I said I feel like you got most of that

6:39

in your in your

6:40

>> I missed a few. I missed a few for sure,

6:41

but I really Yeah,

6:43

>> I missed this part which I don't think I

6:44

did very well. Let me say this last part

6:46

which was losing trust in each other was

6:47

another big point which is when you go

6:49

to a as a maintainer when you open up a

6:51

project if you have notifications and it

6:53

turns out the person on the other side

6:55

often well-meaning as they say put in

6:57

loweffort poll requests it kind of

6:58

builds into you a bias thinking that all

7:00

poll requests and all new people are

7:02

just going to be a bunch of LLM or

7:03

loweffort people and it makes you more

7:05

resistant to new people coming into your

7:07

community makes it harder for people

7:08

that are active in your community to be

7:09

able to like really reach you and have

7:11

good discussions because now

7:12

everything's being passed through this

7:13

filter of oh it's an LLM being

7:15

bothersome and so it kind of tears down

7:17

communities and creates a more toxic

7:19

place whereas if you didn't have that

7:21

you'd have good conversation much more

7:22

meaningful conversation at least that is

7:24

their intended argument

7:26

>> good summary prime

7:27

>> now prime you are the one who wanted to

7:30

talk about this originally you you were

7:32

like I want to talk about this so maybe

7:34

you could start by saying why did you

7:37

want to talk about it

7:38

>> for me I I I will first start off with

7:41

what I thought was their most

7:42

interesting point which was the last one

7:43

that that they said which is the tear

7:45

down of communities. Mhm.

7:47

>> Uh I I do think that there's something

7:48

very interesting to that because I've

7:50

noticed it a lot even just in my basic

7:52

communication is that anytime I read

7:53

something that's over three sentences

7:55

long.

7:56

>> I am now like more and more going I

7:59

think this person just generated this

8:00

response because it's just like way too

8:02

it's just like way too uh superolous.

8:05

like there's just the language is all

8:06

wrong and it just like and I realize

8:08

that it makes me stop really reading a

8:10

lot of people's responses and it's kind

8:12

of tearing down the community whether I

8:13

real like it wasn't

8:15

>> it was a uh it was my favorite part of

8:17

the four-part diagram which is called an

8:19

unknown known I didn't know I knew it

8:22

but I just knew it inherently and I just

8:24

operate under this bias where I just

8:26

don't even realize that I'm doing it to

8:27

myself whereas like I start looking at a

8:29

lot of stuff and going oh this is just

8:30

LLM generated without even giving them a

8:32

fair shake or really consideration to

8:33

their argument and I see why this is

8:35

actually tearing down uh tearing down

8:38

communities and codeberg being a place

8:40

that's probably much more tight-knit

8:42

than say GitHub. I bet you a lot of the

8:44

maintainers of projects know other

8:45

maintainers of project community is very

8:48

very important. And so I'm just curious

8:50

like how is that something that they

8:53

should be concerned about or is it

8:55

better just to say hey we we're growing

8:56

and adapting to the everanging field of

8:59

software engineering and we should just

9:01

move away from this even though I can

9:03

see why it's beneficial. I find this

9:05

part at least very interesting or very

9:07

unique.

9:08

>> Yeah. I mean I guess one thing I would

9:10

say is reading through their blog post I

9:13

didn't really hit any part where I was

9:15

like well that doesn't make any sense.

9:17

like it it kind of was just like very

9:19

reasonable. Now, I don't know for a fact

9:22

that the reasons that they're giving are

9:24

the real reasons like or whether they

9:26

just hate LLMs or something and and just

9:29

we're going to ban them either way. You

9:30

know, I don't know whether it was

9:31

rationalization or whether it was

9:33

actually like these were the motivating

9:35

factors. But to me, it doesn't really

9:37

matter. It's like the explanations they

9:39

gave were very sound explanations. I

9:41

felt like all of them were pretty

9:42

reasonable. about the only thing that I

9:44

would say as a slight counterpoint was I

9:47

was like well you know could you just

9:50

turn this into a monetary policy could

9:52

it just be that well if you want to do

9:55

this like if you want to use LLMs to

9:58

generate a lot of code we're going to

9:59

charge you a lot of money like that's

10:01

going to cost you so like you can't use

10:03

this service for free uh you're going to

10:05

have to pay us if you submit LLM

10:07

generated stuff uh you're already paying

10:09

for the LLM so you know whatever or

10:11

something like that because at least

10:13

that way it would it would be something

10:16

where um it could be adjusted. But I

10:20

also understand the perspective of if

10:22

they just don't want this, like if

10:23

they're just like we don't we don't see

10:25

this as being something we want to be

10:26

involved with at all, then I can

10:28

understand the policy because they're

10:29

just basically saying like look, we

10:30

don't want this at all. So we don't want

10:32

to we don't want to pessimize it. We

10:33

don't want to reduce its use. We just

10:35

want to get rid of it and h have those

10:36

people go somewhere else. Totally fine

10:38

if that's their decision.

10:40

>> I have a quick comment. So the I thought

10:42

the same thing as Casey said. I thought

10:44

all like this blog post was good. I

10:45

thought everything was written very

10:47

well. I agreed with everything. What

10:49

what I can't get past is like

10:53

I don't understand how you can even

10:54

enforce such a thing that they're saying

10:56

here. So there's like a lot of like

10:58

blurry lines where it's like you can't

10:59

have a project that's mostly created by

11:02

like an AI LLM, which that just blurs

11:05

the lines. Now it's like well who's

11:06

deciding what's mostly or who's not?

11:08

Like it almost feels like you really

11:10

can't really have a repo on Coberg

11:12

unless you have like some like past

11:13

reputation of being like some great open

11:16

source person like someone who's coming

11:17

in like it almost shuts off anybody new

11:20

to like the space. Um because they have

11:22

no previous like like credentials or

11:25

anything like that. And if you can't

11:26

prove that they they didn't create with

11:28

an LLM, you're going to almost just

11:29

assume just kind of like what you said

11:31

earlier, you almost just assume

11:32

everyone's using LLM. Like I've never

11:34

seen such detailed PR requests or PR

11:37

descriptions until like this past

11:38

[laughter] year. And every time I see

11:40

like a wellthoughtout PR description,

11:42

I'm like I'm not reading it because it's

11:43

slop. Um, which is funny cuz when I do

11:45

it, I don't feel that way. I'm like,

11:47

yeah, this is well detailed. But when

11:48

someone does it to me, I get like I get

11:49

like offended almost. [laughter] I'm

11:51

like, wow, you didn't take the time. So

11:52

funny. This morning I actually got a on

11:54

one of my open source projects I got uh

11:57

[clears throat] a pull request and it

11:58

was definitely just like autogenerated

12:00

and I was like almost pissed off when I

12:03

got it. But at the same time like this

12:04

whole past week I've been using uh LLMs

12:07

to just like knock out a bunch of like

12:08

tech debt. But for whatever reason when

12:10

I saw someone do it to me and it wasn't

12:12

me doing it I could I just got like

12:15

super bad for some reason. I'm like I'm

12:16

going to close it. But yeah, I don't

12:18

know. I can't explain the I can't

12:19

explain the psychology there right now.

12:21

It's weird.

12:22

I I think that's kind of a thing that is

12:24

almost to be expected though because uh

12:28

everyone

12:30

this is common for humans right like

12:32

it's just a thing that everyone does

12:34

which is you believe that you are

12:37

responsible when you use something like

12:39

I am a good driver and I drive

12:41

responsibly right but these other people

12:43

>> that's why I can text and drive case

12:45

>> yeah [laughter]

12:46

right it's like I can look at the map

12:49

but if someone else is doing that

12:50

they're just irresponsible Well, they're

12:52

going to kill somebody and whatever,

12:53

right? And uh you can name just about

12:56

anything, gun ownership, drinking,

12:59

whatever it is, drugs. It's always like

13:01

the people who think that they can do it

13:03

responsibly don't just automatically

13:06

then think, well, anyone can do it

13:07

responsibly. They're like, no, everyone

13:09

else could, right? LLMs feel a lot like

13:12

that to me. Um, I feel a lot I I feel

13:15

sort of ambiently that people generally

13:18

are like I think that AI is bad and that

13:22

it's generating a lot of slop, but of

13:24

course I use it and I use it really well

13:26

and I make like good stuff with it. It's

13:28

like no, you probably make roughly the

13:30

same stuff as everyone else and you're

13:32

just like downgrading what they're

13:34

making and upgrading what you're making

13:36

kind of unfairly. uh because probably

13:39

their stuff isn't as bad as you're

13:40

making it out to be and your stuff

13:41

probably isn't as good as you're making

13:42

it out to be, right? Uh and that's just

13:44

how it goes, unfortunately. So, I think

13:47

you're touching on something very real.

13:49

I don't think it's specific to AI, but I

13:51

do think it probably is happening a lot

13:53

right now.

13:54

>> I would say

13:55

>> I think that summarizes my feelings

13:56

exactly. No sign, but yeah,

13:59

>> I was going to say the other thing for

14:00

like Oh, go ahead, Trash. No, sorry. No,

14:02

no, no. Go for Well, my last comment is

14:04

after I read this, I almost felt like it

14:06

was like a Masttodon blue sky blog post

14:09

and I was just like, "Wow, this is this

14:11

is like very pretentious. Like, come

14:13

on." But then I get it. Like after

14:15

reading this blog article, I was like,

14:16

"Okay, okay, this all makes sense." Like

14:18

financially, too, it also makes sense.

14:19

Um, but I still feel like it's going to

14:22

shut out a lot of like future like open

14:24

source creators that do use LLM but also

14:26

use them responsibly. But to your point,

14:29

Casey, it's like how do we know they're

14:30

using it responsibly? because I use it

14:32

responsibly, you know. So, it all it all

14:34

just seems very handwavy, not very

14:36

enforcable, and pretty much like you got

14:39

to know somebody almost kind of thing,

14:41

which I don't really like. I don't know.

14:43

>> Tee, you were going to say something.

14:44

>> Yeah, the thing I was going to say was

14:46

it's uh I I think similar to the thing

14:49

you're saying, Casey, but maybe slightly

14:51

different, too, is like for my code

14:53

base, I don't care if I fill it up with

14:56

trash, right? Like if I do something in

14:58

my house and I scuff up the wall, I'm

15:00

kind of like, "Well, that stinks. I wish

15:02

I didn't scuff up the wall." But like if

15:04

I was at my friend's house and I scuffed

15:06

up their wall, I would feel like really

15:08

bad cuz it's like their thing, right? So

15:10

I do think there's like a little bit of

15:13

an asymmetry

15:15

there where like if I do something to

15:17

someone else's repo, I do feel like I

15:19

should do better than I would do on my

15:22

own repo, right? So, I do think like at

15:24

least for I feel like a responsibility

15:26

that like, oh, I'm going into your

15:28

house. What's your rules? How do you do

15:30

stuff? I'm going to do it your way. You

15:32

leave shoes on. That's disgusting, but

15:35

I'll do it at your house. [laughter] My

15:37

house, you're taking your shoes off.

15:38

Okay. Everybody at the door. Okay.

15:40

>> Reasonable.

15:41

>> Gotcha. [laughter]

15:43

>> Um, okay. So, I wanted to jump back on

15:45

uh trash. What were you saying? What

15:48

What What did you just say? What was the

15:50

Cuz I had a great Oh, yeah. Okay, I got

15:52

it. Ghosty. How does Ghosty work in this

15:55

world? For those that don't know, Ghosty

15:56

was a terminal uh started off being

15:58

written by Mitchell Hashimoto in his

16:00

retirement years and then gain gained

16:02

popularity and over the last

16:03

>> He's unretired as of today, by the way.

16:05

>> Yeah, he's unretired.

16:06

>> He's back in the

16:08

>> And over uh over the last like year and

16:10

a half, he's been talking about how he

16:11

uses AI all the time to generate uh

16:14

patches and all that. Like, how do you

16:17

even enforce the idea of mostly? Like

16:20

why would Ghosty deserve a spot on

16:23

Codeberg because we know at least one

16:25

person committing to Codeberg uses AI

16:27

regularly? Like what is the what is the

16:29

the mark of too much slop? Like I don't

16:33

I don't know what that is.

16:34

>> I I kind of have something tangential to

16:37

say. I don't think there is a way to

16:38

know, but I have something sort of to

16:41

add to that or to sort of it's not

16:42

really a pylon, but it's like a thing

16:44

that goes along with it, I think, which

16:46

is I think there's I based on their blog

16:51

post, they have a lot of goals like

16:54

there were a lot of things outlined

16:56

there, right? And I think there's a

16:58

simpler version that has less goals. So,

17:01

if your goal is just that you want the

17:03

projects to be good and you want them to

17:05

work well and you want the system as a

17:07

whole to work well, then really I think

17:09

the only policy you probably need in

17:12

that scenario is no one should be able

17:15

to tell this was done by an LLM. That's

17:17

the goal, right? The goal should be I

17:19

get the pull request and it's been

17:22

looked over correctly. There's no

17:23

obvious mistakes. The thing isn't too

17:25

verbose. like somebody prepared it so

17:27

that it looks like a nice human

17:29

generated pull request and maybe it was

17:31

generated largely by the LLM, but a

17:33

human was there to make sure that you

17:34

didn't get the slop, right? And so

17:37

that's the real thing that like a

17:39

project that just doesn't want to drown

17:40

in lowquality stuff should be concerned

17:43

with, right? But then there's a separate

17:45

thing where they've piled on all these

17:48

other things which I don't necessarily

17:50

disagree with. So I'm not saying pile on

17:51

in a bad sense. I'm just saying they've

17:53

added a lot more past that baseline of

17:55

just don't disrupt the service. They're

17:57

basically saying like they don't really

18:00

want to invest time in the LLM sort of

18:04

economy. They're saying they want to

18:06

invest in people, right? I've heard this

18:08

from multiple places. I believe this was

18:11

the stated reason why Zigg stopped uh

18:14

accepting LLM generated political

18:17

>> contributions. And then exactly that

18:19

>> they basically said I think Andrew Kelly

18:21

literally said in an interview he said

18:23

something like we want to invest in

18:25

people who we believe will become future

18:29

contributors to Zigg and we want those

18:32

people to be spending a lot of time in

18:34

the code. Again don't know if that's the

18:37

real reason or not. I can't like intuit

18:40

it or or I can't like see into people's

18:42

souls and know like what they're

18:43

actually saying. But as a statement, it

18:45

is very reasonable, right?

18:47

>> Yes. If that's your goal is to have is

18:49

to cultivate people who are going to

18:51

contribute, then not wanting them to be

18:54

using LMS as the way that they learn

18:56

about the codebase could be a very

18:58

reasonable thing to say. Like I don't

19:00

know, right? I'm not in a position to

19:01

really uh judge that. So I do think

19:04

there's kind of this there's kind of

19:05

different stages, right? when you get to

19:07

a certain point, the goals that you're

19:10

trying to sort of go for kind of have to

19:12

be like, "Yeah, we don't want you using

19:14

LLMs much because we think we we think

19:16

there's something to preserve in the

19:18

human layer and we're going for that."

19:20

>> So, I guess I guess the follow-up

19:22

question is that this obviously caused a

19:24

huge amount of uh kind of stir on the

19:26

internet and I I like you said, I like

19:29

their if you take what they're saying at

19:31

face value. Yes. and you believe they're

19:33

being like honest in all of their

19:35

thoughts that it's purely a very

19:37

practical educational type of pursuit,

19:39

then you would say, "Okay, well this I

19:40

think it's totally fine." Like I think

19:42

that there's nothing wrong with it. But

19:43

obviously the internet kind of freaked

19:45

out and there was people just saying how

19:47

they're going to get left behind and all

19:48

these different kind of things. Uh is

19:51

this actually a real concern or is this

19:53

just like a Twitterism that people throw

19:56

out there that actually has no real

19:58

impact into the future of Codeberg?

20:01

Does anyone else want to go first

20:02

because I have something to say about

20:03

the Left Behind thing? That's kind of

20:05

its own direction.

20:06

>> Oh, with Kirk Cameron, famous movie

20:08

>> and book series.

20:09

>> Really famous series.

20:10

>> And book series.

20:11

>> Yeah.

20:11

>> What do you mean left behind? In what

20:12

sense?

20:15

>> Come back, idiot.

20:16

>> Yeah. [laughter] Yeah. And then there's

20:17

a bunch of people here get left behind

20:20

here. Okay.

20:21

>> Okay.

20:21

>> No, I mean like uh

20:22

>> like they're good. I'm talking about

20:24

like Cobs, but like I don't understand

20:25

like why they'd be left behind if they

20:27

took out LLMs.

20:29

Well, I think the I the implication is

20:31

that if everyone's going to be

20:33

programming with LLMs in the future

20:35

because that's the new way that people

20:36

are

20:38

>> well that people are starting to program

20:39

now like most people are using these

20:41

things or at least a significant portion

20:43

of developers are using these things

20:44

then if you ban them you are effectively

20:47

not going to have enough people right

20:50

doing work to to contribute to codeberg

20:54

repositories I think I think right I

20:56

mean that's just the basic implication

20:57

is there won't be enough programmers is

20:59

doing programming without these LLMs to

21:02

to constitute a you know a relevant set

21:05

of of projects on Codeberg. Is that I

21:07

mean am I just out

21:08

>> they're not banning LLM straight out.

21:10

They're just banning like strictly like

21:12

only LLM stuff, right? That's what I'm

21:15

getting.

21:15

>> Well, yeah,

21:16

>> but I guess that's like that's where the

21:17

gets weird.

21:18

>> Yeah. I mean the I I mean I don't know.

21:20

I'm just saying like I think that's what

21:22

they mean by left behind is just like

21:24

because people will be mostly mostly

21:26

they will be generating code with LLMs

21:27

and if you're doing that you know that's

21:29

that's not allowed

21:30

>> right

21:31

>> so Casey you may not know this but uh

21:33

sorry T you can go next sorry I just got

21:35

to throw this in there trash knows this

21:36

very very well which is a very common

21:38

Silicon Valleyism so I think this is

21:40

actually a holdover from just another

21:42

time which is that if you were to build

21:44

a product in 2021

21:47

>> and you didn't use React

21:49

Mhm.

21:50

>> You were effectively making it so that

21:52

no one can work on your project and it's

21:53

going to be super hard to hire and all

21:55

these kind of things like you saw that

21:56

kind of phrasing and phrasiology

21:58

constantly. So I do think that that that

21:59

mentality whatever it is yet again shows

22:02

up in these type of arguments which is

22:04

well if you're not doing the current

22:05

thing then you're done. You're cooked.

22:07

You're you know whatever the kid you're

22:09

chopped the kids say. I think that's

22:10

what they say. All right. Sorry teach

22:12

go. Yeah, I was going to say I think

22:14

there's

22:16

like if you think of Stack Overflow and

22:19

it like used to be a company and

22:21

basically now it's not is my

22:23

understanding, right? Like it used to be

22:25

popular and now I think they get like

22:27

sometimes days go by with no questions

22:29

asked. Am I crazy? Is it that small now?

22:31

>> It is. No way.

22:33

>> Yeah, it's like it's like 10 questions

22:34

on average a day was the last time I

22:36

looked.

22:37

>> That makes sense.

22:37

>> And it used to be like over 100,000 or

22:39

something insane, right? Sometimes it

22:40

peaked something crazy. whatever. Um,

22:45

so I think like from a if you're saying

22:48

like from a business perspective, I

22:50

think like some of what they're, you

22:51

know, what people are getting at is like

22:52

Codeberg, you won't be able to like pay

22:54

people to work on your stuff or like to

22:57

host it or do all these other things

22:59

because there's literally just not going

23:00

to be enough people like doing whatever

23:04

version it is that Codeberg says is like

23:06

acceptable coding policy. I think is

23:08

like the the conjecture. The thing that

23:11

I always feel like is kind of crazy for

23:14

that where I just, you know, want to

23:18

take a step back and make sure people

23:19

are considering like a lot, you know,

23:22

spent a lot of time working on Neoim.

23:23

Did a lot of fun stuff on my setup,

23:25

whatever. I had a lot of fun doing that.

23:27

Some of it was productive, some of it

23:28

was just fun. I always uh said as much.

23:31

I know that a bunch of people absolutely

23:34

demolished me using Notepad or Notepad++

23:38

or like Ed still and made a whatever

23:42

metric you would pick like crushed me in

23:46

term number of users, amount of money,

23:49

amount of money raised, cultural impact

23:51

like you could pick any vertical and

23:55

they crushed my entire career, right?

23:59

So, I always feel like the like you'll

24:01

get left behind because you're not using

24:03

whatever the current thing is is like

24:06

usually very overstated in just in terms

24:09

of like there are people who are just

24:11

like either much more persistent or much

24:13

more lucky or work harder or whatever

24:14

it's going to be and they like still win

24:17

and carve out their thing and

24:18

unironically uh and without malice the

24:23

successful by their own standards a

24:25

phrase that I know Prime is familiar

24:26

with at least

24:27

>> my favorite phrase by the way

24:29

>> that's a really good

24:30

>> is actually is actually true though if

24:32

codeberg doesn't want to be acquired by

24:34

Microsoft and be the default place where

24:36

people host code instead they want to be

24:39

a place that's like a sustainable

24:41

business where people can share code

24:43

with other humans then they can like

24:45

still meet that goal without getting

24:48

every new programmer so it's like you

24:50

can't you might get left behind by the

24:52

like VC hype cycle thing [clears throat]

24:55

like you'll never get the growth that

24:56

like your venture capital firm would

24:58

have wanted you to get, but that doesn't

25:00

mean that the project is like a failure,

25:02

which is a thing that I just feel like

25:04

is so just like everyone's talking way

25:07

past each other about that online in the

25:09

conversation.

25:11

>> I I feel like that's 100% correct. It's

25:14

like the idea of getting left behind

25:16

doesn't really make very much sense

25:18

because it suggests that everyone's goal

25:20

is to be at the forefront of something,

25:23

right? But that's not right. Like there

25:25

are, you know, like you've got people

25:28

like the Amish who are just like, you

25:30

know what, I'm just not going to use

25:31

electricity, right, in 2026. Like people

25:34

have to have the freedom to define their

25:37

own ways of living. And one of the

25:39

things that I try to tell people,

25:41

although people rarely seem to want to

25:43

listen, is that that is a feature, not a

25:47

bug, of humanity. Because you never

25:50

really know when humanity in large

25:52

numbers is going to go do something

25:54

fantastically stupid. Like we have no

25:56

idea if AI is going to be a huge

25:58

mistake. It might be for reasons we just

26:00

can't foresee, right? And so having some

26:03

percentage of the population who doesn't

26:05

like it reflexively and chooses to go do

26:07

something else, that is not bad. Even if

26:11

they're wrong, it's good. It's

26:14

insurance. It's basically like

26:16

humanity's protection

26:19

about everyone doing something dumb,

26:21

right? So you always want a diversity of

26:24

sort of directions forward where some

26:28

amount of your populace is not doing the

26:30

new thing. Even if the new thing turns

26:33

out to be correct, it was not a good

26:35

idea to try to pressure them into not

26:37

going their own way. Because having that

26:40

sort of different set of people doing

26:42

different things for different reasons

26:44

is why we survive. And the instant you

26:46

try to homogenize everybody and say

26:48

everyone should do it this one way, you

26:51

are effectively like eliminating

26:52

humanity's greatest strength, which is

26:54

not all doing the same thing all the

26:56

time.

26:58

>> They did. This was the problem in

27:00

Interstellar. They all had the exact

27:01

same corn. That's why they had to go

27:04

inside of a black hole.

27:06

>> I mean, I don't know.

27:07

>> Trash. That's literally a bookshelf.

27:09

>> No way. What?

27:11

>> Then Michael Matthew McConey had to go

27:13

behind a bookshelf and like and like

27:15

punch it to like get some stuff happen.

27:17

It's It's hard to recover from corn.

27:20

[laughter]

27:20

>> If you all are doing the same corn, it's

27:22

GG's. Okay. Timothy Shalomé might

27:24

disappear from your timeline and never

27:27

get referenced in the last 45 minutes of

27:29

your movie. Okay.

27:31

>> You get hit by this huge wave, like the

27:33

biggest wave you've ever seen, and you

27:34

have very little warning trash.

27:36

>> Okay.

27:36

>> Very little warning. Noted. Noted on

27:38

corn. Got it.

27:39

>> Yeah. And then then Matt Damon lies to

27:42

you about the planet. It's there's a ton

27:44

of bad stuff that happens in this.

27:46

>> He's a good guy when he's on Earth, but

27:47

every time you see him not on Earth,

27:49

he's a bad guy. Think about it.

27:51

>> That's right.

27:51

>> Uh something I I you know, I feel like

27:54

people don't talk about is Matthew

27:55

McConn spent like years behind that

27:57

bookshelf.

27:59

>> I mean, it's probably a pretty cool

28:00

little space back there.

28:03

>> I'm just throwing it out there. It was a

28:05

long time. He was he was he was out

28:06

there for a long time. patient man.

28:08

>> Very patient.

28:09

>> Very patient.

28:10

>> He got binary.

28:11

>> He He doesn't have

28:13

>> trash. That is what happens though, by

28:14

the way. They all have the same corn and

28:16

then they gets afflicted by the same

28:17

disease and they can't stop it because

28:19

they ran out of corn. That's what they

28:21

can't live anymore.

28:22

>> I had no idea.

28:24

>> You're not paying enough attention.

28:26

Trash.

28:26

>> I'm not paying attention. I'm not.

28:28

>> Yeah.

28:29

>> Trash. But the the serious point to echo

28:32

Casey's point is

28:34

>> if you love AI, you should be thankful

28:36

that there exists people putting out new

28:39

untainted fresh training and keeping the

28:43

light alive of uh trades that we may

28:45

forget how to do. We don't actually want

28:47

to have the meme where it's like we lost

28:50

the technology, whatever the meme is.

28:52

Like my dad showed me this TV and asked

28:55

how did we put this on the moon? He said

28:57

son we lost the technology. You don't

28:59

actually want that. So, you should be

29:00

thankful that people exist that are

29:02

like, I hate AI. I'm going to keep

29:03

writing code by hand.

29:05

>> That's a good

29:06

>> This is This is the exact same thing as

29:08

back in the old old days where people

29:11

were like, why are you working on like

29:13

game engine stuff? Why don't you just

29:15

use Unity? And the answer is don't. Why

29:19

would you ever say that to somebody? The

29:21

people who you're saying that to are the

29:22

people who built Unity. Like, that's why

29:25

you have a Unity is because of these.

29:27

You should just say, "Great, have fun

29:29

with that. I'm going to leave you alone

29:31

because I want my unity later." Right?

29:34

Like that's it's people are arguing

29:36

against their own self-interest. Like

29:38

people who are LLM afficionados are

29:40

arguing against their own self-interest

29:42

when they tell other people not to

29:44

pursue other p. It doesn't make any

29:45

sense. It's like the Codeberg people's

29:48

blog makes perfect sense. The people who

29:50

are saying they shouldn't do this or

29:51

they're going to be left behind. I don't

29:53

really take that seriously because

29:54

that's not what you would say if you

29:56

actually thought about the system as a

29:58

whole. And again, so when you look at

30:00

those people's motivations, it kind of

30:02

feels more like they're just

30:04

self-conscious or something like they

30:06

they they don't have enough self-esteem

30:07

to just go, I'm using LLM and I'm fine

30:10

with it and I don't mind if other people

30:11

aren't in the band. It's like somebody

30:13

else not doing it is like makes them

30:15

afraid maybe there's something wrong

30:16

with them or something and they have to

30:18

get everyone involved in this thing and

30:20

everyone has to agree it's great to do

30:22

this and that there's nothing wrong with

30:24

using them. It's like just have some

30:26

self-confidence. You use LLMs, it's

30:28

fine. You're fine with it. Go ahead and

30:31

let the people who don't don't it it

30:33

just what's the problem, right? I don't

30:34

understand.

30:35

>> Casey, can I read you a QUOTE FROM

30:36

GEORGE HOT?

30:38

>> ALSO, I called it in the chat. As soon

30:40

as Casey said this, I typed in the cat,

30:42

"Ge hots reference incoming." Prime is

30:44

so excited. [laughter]

30:46

>> Tee, I actually had a completely

30:47

different point, but when I saw that, I

30:49

was like, "Oh, that's a good reference.

30:50

I'm going to use that."

30:51

>> Your face [laughter] lit up. You did a

30:53

little bit of shaping, future shaping by

30:55

accident.

30:55

>> What is What is it?

30:57

>> All right. Well, let me let me show you.

30:59

So, this is from his famous blog post

31:01

called I love LLMs. I hate the I hate

31:03

the hype. Where he also casually drops

31:05

that he runs GLM2 just to set up his

31:07

[laughter] Linux machine. you know,

31:08

whatever. A multi-million dollar machine

31:10

just to set up Linux. Uh, you're the

31:12

Linux, by the way. Uh, so anyways, he

31:13

said this, "What I don't like, uh, is

31:15

two things. One, the constant

31:17

about the window closing or perpetual

31:19

underclass or falling hopelessly behind.

31:20

This is a negative valance hype. Not

31:22

only is it not true, it's mostly

31:24

designed to make you feel bad about

31:25

yourself and move to shitty San

31:27

Francisco where everything really does

31:29

suck like how these people claim."

31:31

[laughter] Oh, it gets better, Casey. It

31:32

gets better.

31:33

>> All right. Again, just in case anyone's

31:35

wondering, hots, open invite whenever

31:37

you want to be on here.

31:37

>> Hot stakes. I love these hots takes

31:39

>> dude. He's my favorite writer uh of the

31:42

modern age. And two, this straw man

31:44

jumped from, oh hey, it's a fancy

31:46

autocomplete, smart compiler, better

31:48

search engine to it's like going to own

31:49

the whole Lite Cone, bro. If you aren't

31:51

in San Francisco and at the right

31:53

parties, there's going to be a flash of

31:55

light in the sky one day and you're not

31:56

even going to know what happened. But

31:58

everything just changed. I'll bet you

32:00

everything I I have that this doesn't

32:02

happen. The people per perpetuating this

32:05

are terrible people, but the justice is

32:07

that this is how they feel inside all

32:10

the time themselves.

32:12

>> I I guess, you know, all all I'm doing

32:15

is is unknowingly paring geoh here. So,

32:18

yes, I mean, that's kind of what I was

32:20

trying to say, but put more eloquently,

32:22

I suppose.

32:23

>> I I love that phrase, but uh I mean, I I

32:26

I do want to throw this out there that

32:28

there's this there's this one big

32:30

problem when it comes to AI. Well,

32:31

really it comes to anyone talking about

32:33

technology, and I do this myself all the

32:35

time because Neo Vim's still the

32:36

greatest editor if you want to actually

32:37

be a real programmer. But, uh,

32:39

[laughter] the thing is,

32:41

>> is that when you approach a problem,

32:44

especially like you'll definitely see

32:45

this from people recommending LLM is

32:47

that they can identify and say, "Oh,

32:49

this is a part that LLMs are not that

32:51

good at, but don't worry, it's really

32:53

great at backends." Oh, no, don't worry.

32:55

It's really great at this other thing.

32:56

And and so I I hearken it to like

32:59

something like the gentleman amnesia,

33:00

which is you open up a magazine, you

33:02

read the first thing about horses. You

33:04

say, "Wow, they're so smart about

33:05

horses. Look at all these cool facts."

33:06

You go to JavaScript and you read it and

33:08

they're like, "Oh, they know nothing

33:09

about JavaScript. They're so they're

33:10

such idiots." You turn the page and

33:11

you're like, "Oh man, this be article is

33:12

so amazing. Look, I know so much about

33:14

bees now." It's like you completely

33:16

forgot the fact that when you knew

33:17

something, then it was not that good.

33:20

But when you don't know something, it's

33:21

like the most fantastic thing in the

33:22

universe. So it has some strong

33:24

parallels to that. And I think that

33:25

people often forget that what they work

33:28

on and what they're doing may be very

33:30

good with LLMs. That doesn't mean

33:32

everybody has a problem that's really

33:33

aligned with LLM. Like if I was just

33:35

building uh some SAS tools that is

33:38

taking stuff from the back end and

33:39

putting it on the front end, like you

33:40

bet your sweet ass I'd be using LLM like

33:42

wild. Like I'd be setting up every last

33:44

thing cuz it's like this is such a

33:46

mechanical obvious, you know, put the

33:49

data in the box, bro. Like there's not

33:51

like a lot you got to do there. And so

33:53

it's like this is a perfect example of

33:54

you saying, "Hey, you could probably get

33:56

to the point of even automating PR

33:58

review through a lot of this stuff with

34:00

barely like any oversight." Whereas like

34:02

that you can't do that for everything.

34:04

But people see this one thing and they

34:05

go, "Dude, why aren't you automating PR

34:07

review? It's obvious. You should do it

34:09

this way. This is the future, idiot."

34:11

But like their their circle is so much

34:13

different than other people's circle,

34:15

but it's the you know, I see it this

34:16

therefore everybody has this exact same

34:18

thing. And also they feel really crappy

34:20

on the inside based on geohods. And so,

34:22

uh, that's kind of like how I look at

34:23

this and why people are angry at

34:24

Codeberg is because they see their

34:27

future and what they're doing and they

34:28

see codeberg going against it and they

34:30

cannot imagine a world in which is

34:32

different than their own world. Well, I

34:35

would also just point out the difference

34:36

in goals at least because from my

34:38

perspective I I've never really been

34:41

super concerned I mean I guess I am

34:42

concerned sort of because I have to use

34:44

software about how good LLMs are

34:47

compared to human programming, right?

34:49

I'm slightly concerned because like if

34:51

they were if they don't get any better

34:53

maybe that's a problem because people

34:54

are using them. So I I you know I kind

34:56

of want them to improve in the sense

34:58

that if they don't improve we're kind of

34:59

in trouble. But you know that sort of

35:01

that's a separate thing. So assuming

35:03

that they get good enough that it's just

35:05

fine all the time and they can write

35:06

really good code and we don't really

35:07

have to worry about it too much. to me

35:10

that's really just not part of the

35:11

equation at least for me because it's

35:13

like I like to program like I want to do

35:15

it right and and so when I look at

35:18

things other things in life uh I think

35:21

te used chess as an example before I

35:23

find that very compelling it's like if I

35:25

want to play a game of chess I'm not

35:27

thinking well I'm not going to play that

35:29

game of chess because I know that I

35:31

could get a computer that can play it

35:32

better than me [laughter] I still just

35:34

want to do it right

35:36

>> you know

35:37

>> it's good

35:37

>> yeah so

35:39

>> I Like TJ, I I actually even prefer

35:41

that's one of TJ's really great

35:42

analogies. A second one of his is the

35:44

Amish chair one, which you kind of

35:45

alluded to, which is Amish people still

35:47

make chairs that I can go buy.

35:49

>> Yeah. Well, and the other thing I was

35:50

going to say is

35:50

>> why not just massproduce it from IKEA,

35:52

idiot? Just use the massproduced one,

35:53

dummy.

35:54

>> Drum drum machines versus live music,

35:56

right? It's like we have things that can

35:58

do stuff on a type. So, it's like I may

36:00

just want to learn to play the drums

36:01

because I enjoy playing the drums. It's

36:03

not that I think I will be more precise

36:05

than a drum machine or whatever.

36:07

[laughter] It's just that I wanted to

36:09

play the drums, right? And so to me,

36:12

those things should be acceptable. Like

36:14

if you say that, people should not be

36:17

likeounding you for some reason. It's a

36:19

perfectly rational thing that exists in

36:21

all other things. Like, hey, we could

36:22

probably design a robot that hits a

36:24

baseball really well. That doesn't mean

36:26

that we shouldn't have people playing

36:28

baseball as something we watch. Like,

36:30

it's just it might just be something we

36:32

want to do and that should be fine. and

36:34

you should not care because if again if

36:37

you're not really self-conscious or

36:39

something and you and you actually have

36:41

some self-confidence, then if you want

36:43

to go build the future with LLMs, those

36:46

people are not in your way, right?

36:48

They're like not they're not creating a

36:49

problem by going and doing something a

36:51

different way. So, what's the what's the

36:52

issue? Like, why do you have to convince

36:54

them not to? I I don't I don't see it.

36:56

Hey guys, if you like this episode, you

36:58

can watch the rest of it on the Spotify.

37:00

And don't forget to LIKE AND SUBSCRIBE.

37:02

WOO! WOO. See you later.

37:04

>> Boot up the day.

37:08

Voting [music]

37:09

errors [singing] on my screen.

37:12

Terminal [music]

37:13

coffee

37:15

and

37:17

living the dream.

Interactive Summary

The video discusses Codeberg's recent policy change to no longer allow projects primarily consisting of LLM-generated code. Codeberg, an open-source code hosting platform, cites several reasons for this decision, including increased hardware costs and infrastructure strain due to large, often untouched, LLM-generated codebases, unclear copyright status, and a desire to foster community over single-use software. A significant point of discussion is the negative impact of low-effort LLM-generated pull requests on community trust and maintainer engagement. While some argue this policy is reasonable for Codeberg's goals, others express concern about being "left behind" in the evolving software engineering landscape. The hosts and guests debate the enforceability of such a policy and the psychological aspects of developers' views on AI-generated code, ultimately emphasizing the importance of diversity in development approaches and individual project goals.

Suggested questions

5 ready-made prompts