HomeVideos

This Is Crazy

Now Playing

This Is Crazy

Transcript

266 segments

0:00

Open source is dead. And no, I'm not

0:02

talking about the AI slop apocalypse PR

0:05

epidemic that has been going on for the

0:06

last 6 months. I'm talking about

0:08

something much much much more serious.

0:11

And the weirdest part about this whole

0:12

thing, it's being disguised as a joke.

0:17

We're only joking. Listen here, pal.

0:19

Even the Bible hates this behavior. And

0:21

this was from 3,000 years ago. Ain't

0:23

nobody likes this. All right. To

0:24

understand what's going on, may I

0:27

present to you first the website Malice

0:30

Liberate opensource. Now to understand

0:32

what is happening and what's going on

0:34

behind all this, you got to know a

0:36

little bit of history. And the first

0:38

piece of history starts right here.

0:40

Baker versus Seldon. Now, effectively

0:42

what happened is that Baker studied

0:45

everything that Seldon did and then

0:47

recreated effectively Seldon's

0:49

accounting work and his new novel

0:51

principles and was able to sell his own

0:53

version of the book. Now, of course,

0:54

this went off into the courts. The

0:57

courts eventually reached the Supreme

0:58

Court and the Supreme Court said, "Hey,

1:00

you can copyright expressions, but you

1:03

cannot copyright ideas." This is

1:05

important. Again, in the same talk and

1:07

also on Malice's website is another very

1:10

important piece of lore from our

1:12

history. In 1984, a company called

1:15

Phoenix Technologies did a very kind of

1:18

clever thing. Effectively, at one point,

1:20

IBM had a strangle hold on the entire

1:22

computing like ecosystem. And so what

1:25

Phoenix Technologies did is that they

1:27

hired an engineer that would go through

1:30

and effectively create a perfect spec to

1:32

match exactly how the BIOS would operate

1:34

from IBM. And then a second engineer

1:37

would just simply implement the spec,

1:40

never interacting with IBM, never

1:41

attempting to steal any information,

1:43

just simply looking at the spec and

1:46

copying its behavior. And this allowed

1:48

Phoenix Technologies to actually write

1:50

its own version of some IBM firmware.

1:52

And then legally they were given the

1:54

thumbs up. Yes, that is okay. Legally

1:56

this is called clean room engineering.

1:59

Effectively you create a buffer between

2:01

person who understands the technology

2:03

and person who implements the

2:04

technology. And by having this legally

2:06

distinct separation, you prevent

2:09

yourself from falling into a bunch of

2:10

issues. Hopefully now it's a little bit

2:12

more obvious where I'm going at this

2:14

point. Robot A reads the documentation,

2:17

understands the code, sees what's going

2:19

on, generates a specification. Robot B

2:22

implements from just the spec package

2:25

liberated. What this means is that there

2:27

are packages out in the ecosystem that

2:29

have say GPL licenses. If you're not

2:32

familiar with copy left or GPL,

2:33

effectively what happens is that if you

2:36

use a GPL package, you must make your

2:39

package open source for everybody and

2:42

you must have a GPL license. It is a

2:44

viral licensing. So say you wanted this

2:46

package and you're like, "Oo, I could

2:48

really use that. that would be pivotal

2:49

for my project. But I also don't want

2:51

GPL. This is a commercial project. Well,

2:54

what could I do? I could AI clean room

2:56

engineer that. And this is exactly what

2:58

was built by these two right here. They

3:00

gave an entire presentation. It's up on

3:02

YouTube and they call it the death of

3:03

open source where they argue quite

3:06

thoroughly of all the dangers of open

3:08

source, why effectively there's a bunch

3:10

of problems with it, why licenses can be

3:12

pretty bad, and why copyright law is

3:14

actually in their favor. Nolan right

3:16

here proposes this idea of clean room as

3:20

a service. So if you actually go to the

3:21

website Malice, I just assumed this was

3:23

just a joke, right? The name it's way

3:25

too on the nose. It seems pretty

3:27

obvious. The comments are from

3:28

Wellington bottomline stockholder and

3:31

offshore, right? Like this is all

3:33

extremely on the nose. But here's the

3:35

thing. I bought the service. I got is

3:38

number copied. I got leftpad copied.

3:41

This is the exact code that it produced.

3:43

And yes, this passes the 111 test for

3:47

JavaScript is number. Now, your obvious

3:50

first reaction to everything I'm saying.

3:51

I know it's been a lot. Your first

3:53

reaction is JavaScript has an is number

3:56

package that you have to download and

3:58

execute to understand what a number is.

4:00

Yes. Yes, it is true. And second, yes,

4:04

this is a potential implementation which

4:06

is entirely more than one line of code.

4:09

I JavaScript is truly a cursed language.

4:11

Okay, it is just the worst. But I think

4:14

the second and more important reaction

4:15

is, okay, this was obviously uh an

4:18

elaborate setup to kind of show the

4:20

weakness of our current copyright law

4:22

and what's happening within open source.

4:24

You can now have commercial entities

4:25

effectively copy anything with AI and

4:28

just say, "Yeah, we don't care about

4:30

licenses." Oh, sorry. Is that GPL? More

4:32

like goodbye. More like don't give a

4:34

licensing going on right here. And

4:36

there is legally apparently nothing we

4:39

can do about it. That is just the state

4:41

of affairs. You put your code on the

4:43

internet, a robot can write a

4:45

specification and a second robot can

4:47

just straight up snatch it. Clean room

4:48

engineering, baby. As you can imagine, I

4:50

I feel a lot of things, right? I feel a

4:52

lot of upsetness towards this entire

4:55

experience. Even just reading it, it

4:56

just feels very upsetting because for

4:58

me, it's not really a joke. Like, yes, I

5:01

believe these guys for setting up it as

5:03

a joke. It's such an elaborate joke that

5:05

they even took money. For me, that's

5:07

typically when the I'm just joking phase

5:09

stops being a joke. But you must

5:11

understand that this is what's

5:13

happening. Look at this tweet from Sammy

5:15

Samboy right here. I have so much

5:17

gratitude to the people who wrote

5:19

extremely complex software character by

5:23

character. It already feels difficult to

5:26

remember how much effort it really took.

5:28

Thank you for getting us to this point

5:31

because you know what what comes after,

5:33

right? Great, huh? I mean, by the way,

5:35

somebody somebody needs to be monitoring

5:38

some of these tweets over at Open AI and

5:39

be like, "Yo, bro, just don't say that."

5:41

Okay, they Okay, you just got to

5:42

remember that public perception of AI is

5:44

in the actual toilet. It's been falling

5:46

among developers. It's been falling

5:48

among game developers. It's been falling

5:50

among the entire public. You just don't,

5:52

whatever you do, don't say something

5:53

stupid like, "Thanking everybody for

5:55

their hard work. Now I'm going to go

5:56

make billions of dollars off of you."

5:58

Just don't do that. That's the one thing

5:59

you can't do. And Sam's like, "Hold my

6:01

Apple teeny. I got a tweet to send,

6:03

brother. This is so bad. This is a real

6:07

thing. This is not just a proof of

6:08

concept. This actually works. You can

6:11

actually go and pay money right now and

6:13

go liberate whatever package you want.

6:15

All you need to do is have a

6:17

package.json and bam, it's yours. Now,

6:20

new license, new code, new you. Sure,

6:23

your your soul might be a little bit in

6:25

trouble, but hey, you get that you get

6:27

those sweet corporate dollars. Now,

6:29

here's the part that I kind of have with

6:30

the joking. like yes uh the these two

6:32

went off and set up this whole kind of

6:34

experiment saying hey this is what we're

6:36

doing it's a fun joke but then they also

6:38

might be making some money off of it. I

6:40

don't know where the joke, you know,

6:41

like when does the joke stop being a

6:43

joke? Like when do you become the

6:45

biblical idiot that says, "Bro, I was

6:47

just joking." And even more so at this

6:50

point, even if they take down the site,

6:51

somebody's going to put it back up,

6:53

somebody's going to make the money. And

6:54

this is actually their literal argument,

6:55

which is somebody is going to make the

6:57

money off of this, so why not be us? And

6:59

then they actually do. This is the world

7:00

we're going to live in. And I do want to

7:02

talk about kind of a more important

7:03

point for just a quick second. Okay? I

7:04

know this is not what we do around here,

7:06

but I do have kind of like a follow-up

7:08

worry that I've just been thinking a lot

7:09

about. You see, in 2013, 2012, there was

7:13

a group of people who made React. You

7:15

know that I have not the highest

7:17

opinions about React, but at the time it

7:19

was revolutionary, right? Someone made

7:21

this technology which made a great leap

7:23

forward in UI programming. I don't think

7:26

React could be made today. I don't think

7:28

the company that produced React has any

7:30

appetite for that type of engineering.

7:32

Follow up. I don't think any of the

7:34

engineers that are focused on trying to

7:36

make some big sort of impact in the

7:38

engineering world care a dime about

7:41

programming anymore. I am not sure if

7:43

we're going to see a world that actually

7:45

gets new technology. This is it. To me,

7:49

this is the final place. This is where

7:51

we're at. And not only that, thank you.

7:53

We have the death of open- source

7:55

software. The corporations will in fact

7:57

get what they want, one license change

7:59

at a time. Now, what I'm actually hoping

8:01

for, the actual outcome of this is that

8:03

Malice, this Malice Corporation is so

8:06

egregious and enough people freak out,

8:08

right, that they end up having some sort

8:11

of law change saying, "Hey, AI clean

8:13

room engineering in fact does not

8:15

count." My guess is that will never

8:17

happen. But I assume that's the actual

8:20

goal. That's the I was just joking

8:22

behind all this. What which is I'm not

8:24

joking. I actually want to create a

8:26

change. And the only kind of way I can

8:28

see a change happening is by creating

8:30

such a stir, creating such an outrage

8:32

that government officials have to step

8:34

in and make up some law. All right,

8:36

that's it. That's all I got to talk to

8:38

you about. Uh, happy open source is dead

8:40

day. I guess this is actually like my

8:42

third time recording this video. Uh, the

8:44

reason being is that I actually got too

8:45

frustrated the other two times. Like I

8:47

really I I really dislike this strongly.

8:49

It makes me it makes me angry on the

8:51

inside. You know what I mean? Little a

8:53

little little freef fall of emotional

8:55

parachuting going on right now. Okay.

8:58

Quite turbulent. Buffeted by a lot OF

8:59

EMOTIONS. I'M NOT HAVING FUN RIGHT NOW.

9:02

The name is the primogen. Hey, is that

9:05

http? Get that out of here. That's not

9:08

how we order coffee. We order coffee via

9:10

ssh terminal.shop. Yeah. You want a real

9:13

experience. You want real coffee. You

9:15

want awesome subscriptions so you never

9:17

have to remember again. Oh, you want

9:19

exclusive blends with exclusive coffee

9:21

and exclusive content? Then check out

9:24

CRON. You don't know what SSH is?

9:27

>> Well, maybe the coffee is not for you.

9:34

Living the dream.

Interactive Summary

The video discusses the "death of open source" due to AI clean room engineering, a service offered by a website named Malice. This service leverages legal precedents like "Baker v. Seldon," which states that ideas cannot be copyrighted, only expressions, and the traditional "clean room engineering" approach. An AI can now read existing open-source code, generate a specification, and then another AI can implement that specification to create new code. This new code, being legally distinct, bypasses restrictive licenses like GPL, making it commercially usable without adhering to the original license terms. The speaker expresses deep frustration and concern that this development will stifle future innovation, as corporations can now freely copy open-source work without obligation, potentially leading to a decline in new technologies. The speaker's hope is that the outrage generated by such services will prompt legal changes to prohibit AI clean room engineering.

Suggested questions

7 ready-made prompts