YouSaid · the spoken record

James Gosling

lines on the record: 104
first: 2020-09-24
most recent: 2020-09-24
sittings or episodes: 1
sources: podcast

Every line below is reproduced as it was said and linked to the record it came from. Nothing here is summarised or generated. Directory · Search · Corrections

“You get a pass on the first time or two that you do something stupid, the third or fourth time, yeah, not so much. Also, you know. I don't know why, but really early on I started to think about ethical choices in my life. And because I'm a big science fiction fan. I got to thinking about just about every technical decision I make in terms of how do you want, you know, are you building Blade Runner or Star Trek?”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“You down well. It worked out right. And I think some of the weirder stuff that I've done. Has been the coolest, and some of it crashed and burned. You know, I think well over half of the stuff that I've done has crashed and burned, which is occasionally been really annoying.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Well, I mean, it was in billions of phones before Android came along. And I'm just as proud as of the way that the smart card standards adopted Java. And they did a, you know, everybody involved in that did a really good job. And that's billions and billions.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“I guess I've sort of came to believe that it didn't matter what Andy did, it was going to blow up I kind of started to think of him as like a manufacturer of bombs.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Yeah, lines were crossed, but have since, you know, mushroomed into giant court cases. And they didn't need to do that. And in fact, it would have been so much cheaper for them to not cross lines”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Have to do a short answer to that. So, you know, I'm happy that they did it. Java had been running on cell phones at that time for quite a few years and it worked really, really well. There were things about how they did it. And in particular, Various ways that they Violated all kinds of contracts. The guy who led it, Andy Rubin. He crossed a lot of lines”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“And I think it's, you know, and it worked out over time. I mean, the. The biggest fights were with Intel. Because they had done some strange things with rounding. They had done some strange things with their transcendental functions, which turned into a mushroom cloud of weirdness.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“And one of the ways that I got into fights with people was that There were a few machines that did not implement IEEE 754 correctly.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Just do that Of the other places where there was a lot of variability was in the way that floating point behaved. And that was causing people throughout the software industry much pain because you couldn't do a numerical computing library that would work on CDC and then have it work on an IBM machine and work on a DEC machine. And as a part of that whole struggle, there had been this big body of work on floating point standards. And this thing emerged that came to be called IEEE 754, which is the floating point standard that pretty much taken over the entire universe. And at the time I was doing Java, it had pretty much completed taking over the universe. There were still a few pockets of holdouts, but I was like, you know, it's important to be able to say what 2 plus 2 means. And so I went.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So I figured good, I can be lazy again. Sometimes I think that most of my good ideas are driven by laziness. And often I find that some of people's stupidest ideas are because they're insufficiently lazy. They just want to build something really complicated. And it's like, it doesn't need to be that complicated. Yeah, and so that's how that came out. But that also turned into kind of almost a religious position on my part, which was which got me in several other fights. So one of the things that was a real difference was the way that arithmetic worked. Once upon a time, it wasn't always just two's complement arithmetic. There were some machines that had one's complement arithmetic, which was like almost anything built by CDC. And occasionally there were machines that were decimal arithmetic. And I was like, this is crazy.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Yeah. And I think that was a key part. So then, you know, clock comes forward a few years. And it's like, we've got to be able to, if they want to be able to switch from this weird microprocessor to that weird and totally different microprocessor, how do you do that? And I kind of went, Maybe by doing something kind of in the space of Pascal P code, I could do like multiple translators. And I spent some time thinking about that and thinking about what worked and what didn't work when I did the P code to VAX translator. And Talk to some of the folks who are involved in small talk because small talk also did a byte And then I kind of went, yeah, I want to do that. And it had the other advantage that you could either interpret it or compile it. And interpreters are usually easier to do, but not as fast as a compiler.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“And so everything just got really fast, it was really easy. It was like, wow, I thought that was a sleazy hack because I was lazy. And in actual fact, it worked really well. And I tried to convince people that that was maybe a good thesis topic. And nobody was, you know, it was like, nah.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“From the perk machines to VAX And I think know what he had in mind was something that would translate from like Pascal. Or Pascal, who actually at those times pretty much you could translate to C or C. And if you didn't like translating to C, you could translate to C. There was, you know, it's like the Henry Ford, any color you want just as long as it's black. And I went. That's really hard And I noticed that, and I was like looking at stuff and I went. I bet I could rewrite the P code into Vax Assembly code. And then I started to realize that there were some properties of Picode that made that really easy, some properties that made it really hard. So I ended up writing this thing From P code on the three rivers perks into assembly code on the backs. And I actually got higher quality code than the C compiler.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“What they did was they built a machine whose instruction set was. Was literally the bytecode for UCSD Pascal, the P code. So we had a bunch of software that was written for this machine. And for various reasons. The company wasn't doing terrifically well. We had all this software on these machines and we wanted it to run on other machines, principally the VACs. And And Sir Raj asked me if I could come up with a way to port all of this software.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“In our conversations with all these vendors, these problems started to show up. I kind of had this epiphany. Because it reminded me of A summer job that I had had in grad school. Back in grad school, my thesis advisor. Well, I had two thesis advisors for bizarre reasons. One of them was a guy named Raj Reddy. The other one was Bob Sprow. And Raj, I love Raj. I love both of them So the The department had bought a bunch of Like early workstations from a company called Three Rivers Computer Company. And Three Rivers Computer Company was a bunch of electrical engineers who wanted to do as little software as possible. So they knew that they'd need to have compilers and an OS and stuff like that. And they didn't want to do any of that. And they wanted to do that for as close to zero money as possible. So”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So, Like one of the things that sucked about a year out of my life was when Sun went from the Motorola 68 OTAN processor to the 68020 processor. Then they had a number of differences and one of them hit us really hard. And I ended up being the point guy on the worst case of where the new instruction cache architecture hurt us.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Right. Well, and So that's like across the spectrum of providers of chips. But then there's also the time thing because as you went from one generation to the next generation to the next generation, they were all different. And you would often have to rewrite your software.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“We were stuck to that particular machine, which meant that they couldn't decide, you know, Intel is screwing us. I'll start buying chips from. You know, Bob's better chips. This drove the purchasing people absolutely insane. That they were welded into this decision And they would have to make this decision before the first line of software was written.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“There were interesting conversations with purchasing. Um, So, if you look at how these devices come together, they're sheet metal and gears and circuit boards and capacitors and resistors and stuff. Everything you buy has multiple sources, right? So you can buy a capacitor from here, you can buy a capacitor from there. And you've got kind of a market. So that you can actually get a decent price for a capacitor. But CPUs, and particularly in the early 90s. CPUs were all different and all proprietary. So if you use the chip from Intel You had to be an Intel customer for the end till the end of time. Because if you wrote a bunch of software, when you wrote software using whatever technique you wanted, and C was particularly bad about this because there was a lot of properties of the underlying machine that came through.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So, the Java virtual machine You can think of it in different ways Um, Because it was carefully designed to have different ways of viewing it. So one view of it that most people don't really realize is there is that you can View it as sort of an encoding of the abstract syntax tree in reverse Polish notation. I don't know if that makes any sense at all. I could explain it, and that would blow all of our time. But the other way to think of it and the way that it ends up being explained is that it's like the instruction set of an abstract machine that's designed such that you can translate that abstract machine to a physical machine. And the reason that that's important, so if you wind back to the early 90s when we were talking to all of these companies. Doing consumer electronics And you talk to the purchasing people”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“And so it was kind of like a social engineering thing. And People ended up discovering that that really made a difference. In terms of, you know, and a bunch of this stuff, you know, if you're just like screwing around writing your own class project scale stuff, a lot of this stuff doesn't isn't quite so important because both sides of the interface. But when you're building sort of Larger, more complex pieces of software that have a lot of people working on them, and especially when they span organizations. Having really clear, having clarity about how that gets structured saves your life And, you know, especially, you know, there's so much software that is fundamentally untestable until. You do the real thing”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Mad at them, yeah, and so one of the things I did that on the one hand upset a bunch of people was I made it so that you really couldn't go through backdoors, right? So the whole point of that was to say, If the interface here isn't right. The wrong way to deal with that is to go through a back door”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“But a lot of times, you know, You can't get away, you can't just slap their hand and tell them to not do that. Because it's somebody's. Some banks, you know, account reconciliation system that some developer decided, oh, I'm lazy, I'll just sneak through the back door.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Is really slows things down. But also there were, you know, one of the things that you get out of object-oriented programming is a strict methodology about, you know, what are the interfaces between things and being really clear about how parts relate to each other. And what that helps with is so many times what people do is they kind of like sneak around the side. So if you've built something and people are using it. And you say, well, okay, I built this thing. You use it this way. And then you change it in such a way that it still does what you said it does. It just does it a little bit different. But then you find out that somebody out there was sneaking around the side. They sort of tunneled in a back door, and this person, their code broke. And because they were sneaking through a side door. And normally the attitude is.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“All that kind of stuff, yeah. If you, you know, so if you measure time from, you know, you first touch fingers to keyboard until you get your first demo out. Not much different. But if you look from fingers touching keyboard to solid piece of software that you could release in production. It would be way faster”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Right. Because when you're doing a billion operations a second, One in a million chance means It's going to happen. And so I got really religious about this thing about making it so that if something fails, it fails immediately and visibly. And one of the things that was a real attraction of Java to lots of development shops was that we get our code up and running twice as fast”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So when I was originally thinking about that, I was thinking about that in terms of Of safety and security issues. And one of the things I sort of came to believe that it wasn't just about safety and security, but it was about developer velocity. And I got really religious about Hunting down mystery pointer bugs. And, you know, like two-thirds of my time as a software developer was, you know, because the mystery pointer bugs tend to be the hardest to find because they tend to be very, very statistical. The ones that hurt, they're like a one in a million chance And”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Concurrency was a big deal. Because when you're interacting with people, the last thing you ever want to see is the thing like waiting. And issues about the software development process, when faults happen, can you recover from them? What can you do to make it easier to create and eliminate complex data structures? What can you do to fix one of the most common C problems, which is storage leaks? And it's evil twin, the The freed, but still being used of memory. You free something and then you keep using it.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“We have to make sure that this cannot happen. And that was kind of the original thing for me, this cannot continue. One of the things I find really entertaining this year was I forget which rag published it, but there was this article that came out that was an examination. It was sort of the result of an examination of all the security vulnerabilities in Chrome. And Chrome is like a giant piece of C code. And 60 or 70% of all the security vulnerabilities were stupid pointer tricks. And I thought 30 years later”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Just pointers, it was just bugs. And it was like, you know, 50, 60, 70 percent of all security vulnerabilities were bugs. And the vast majority of them were like buffer overflows.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“You know, so back in the early 90s, it was well understood that, you know, the number one source of security vulnerabilities.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“You know, there were a bunch of things that were kind of. And we would talk about things that were going wrong or things that were going wrong, things that were going right. And as we thought about things like the requirements for security and safety. Some low level details and see like naked pointers.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Well, so it was a bunch of things. So after all that, we started, you know, the way that we decided that we could understand things better was by building a demo, building a prototype of something. So kind of because it was easy and fun, we decided to build a control system for some home electronics, you know, TV DCR, that kind of stuff. And as we were building it, we sort of discovered that there were some things about standard practice in C programming. Really getting in the way. And it wasn't exactly because we were writing this, all the C code and C++ code that. We couldn't write it to do the right thing, but that one of the things that was weird in the group was that we had A guy who's His sort of top level job was he was a business guy. He was sort of an MBA kind of person, you know, think about business plans and all of that”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“What could go wrong? And, you know. Just figuring out how to nail the bottom bit, how to make sure that if you put a piece of toast in a toaster, it's not going to kill the customer. It's not going to burst into flames and burn the house down.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“They want faster, faster. It breaks a little more often because it's fast. Maybe you run it a little hotter than you should or like the one that always blew my mind was the way that the folks at Cray supercomputers got their division to be really fast was that they did Newton Raphson approximations. And so, you know, the bottom several bits You know, A over B, we're essentially random numbers.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Repeating the disasters of the computer science industry was there. And one of the things we thought was Maybe we could do something useful here Bringing them forward somewhat, but also at the same time. We learned a bunch of things. From these mostly consumer electronics companies. High on the list was that They viewed their relationship with the customer as sacred. They were never, ever. Willing to make trade offs between For safety Right. So, one of the things that Always made me nervous in the computer industry. Was that People were willing to make trade offs in reliability to get performance.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“For me, one of the things that sort of leapt out was that they were doing all the usual computer things that people had been doing like 20 years before. The thing that really leapt out to me was that they were Of reinventing computer networking. And they were making all the mistakes that people in the computer industry had made. And since I had been doing a lot of work in the networking area, you know, we'd go and visit Company X. They'd describe this networking thing that they were doing. And just without any thought, I could tell them like the 25 things that were going to be complete disasters with that thing that they were doing. And I don't know whether that had any impact on any of them. But that particular story of, you know, sort of”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Literal road trips. It's like get on an airplane, go to Japan, visit, you know, Toshiba and Sharp and Mitsubishi and Sony and all of these folks. And, you know, because we worked for Sun, we had folks who were willing to give us introductions. We visited Samsung. Bunch of Korean companies, and we went all over Europe, went to places like Phillips and Siemens and Thompson.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Well, so the need for a revolution was not about the language. It was about as simple and vague as there are things happening. There”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So, long time ago at sun. About 1990, there was a group of us who were kind of worried that There was stuff going on in the universe of computing that the computing industry was missing out on. And so a few of us started this project at Sun. Really got going. I mean, we started talking about it in 1990 and it really got going in 91. And it was all about. You know, what was happening in terms of computing hardware processors and networking and all of that that was outside of the computer industry. And that was everything from the These sort of early glimmers of cell phones that were happening then to, you know, you look at elevators and locomotives and Process control systems in factories All kinds of audio equipment and video equipment. They all had processors in them and they were all doing stuff with them. And it sort of felt like.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“It is absolutely a balance. And, you know, there are a lot of different ways to make the math work out for everybody. And, you know, the very, you know, Unbalanced sort of Like the winner takes all thing that happens in so much of modern commerce. That just doesn't work for me either.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Know so, you know, if you've got a database, you need to pay for support. And so. But there's a difference between You know, the sort of support contracts that the average open source database producer charges and what somebody who is truly rapacious, like Oracle charges.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“And, you know, it's. It's not hard over rapacious capitalism. And it's not hard over in the other direction. And, you know, a lot of the open source movement, they have been managing to find a path to actually making money, right? doing things like service and support works for a lot of people. And there are some ways where it's kind of Some of them are a little perverse, right? So as A part of things like this Sarbanes-Oxley Act and various people's interpretations of all kinds of accounting principles. And this is kind of a worldwide thing. But if you've got a corporation that is depending on some piece of software, often various accounting and reporting standards say if you don't have a support contract This thing that your business is depending on, then that's bad.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“My basic opposition is. You know, when you say information must be free to a really extreme form that turns into, you know, All people whose job is the production of Everything from movies to software. They must all take a vow of poverty. Information must be free, and that doesn't work for me. And I don't. I don't want to be wildly rich. I am not wildly rich. I do okay. But I do actually, you know, I've feed my children.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“That they would make it free for universities and schools and stuff. And they said, sure. And, you know, that upset some people.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Not fun And, you know, when it was not fun and I was, you know, there was no way I could, you know, pay my rent. And I was like, okay, do I carry on as a grad student? I had a research assistantship and I was sort of living off of that and I was trying to do my, you know, I was doing all my RA being grad student work and being Mr. Emacs all at the same time. And I decided to pick one. And one of the things that I did at the time was I went around, you know, all the people I knew on the ARPANET who might. Able to take over looking after Emacs and pretty much everybody said, I got a day job. So I actually found, you know, Two folks and a couple of folks in a garage in New Jersey Complete with a dog. Who are willing to take it over? But they were going to have to charge money But my deal with them was that they would.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“You know, and maybe, you know, I could be fabulously wealthy today if I had become Mr. Emacs and Emacs had mushroomed into a series of text processing applications and all kinds of stuff. And I would have, you know. I have a long history of financially suboptimal decisions. Because Didn't want that life. Right. And, you know, I went to grad school because I wanted to graduate. You know, being Mr. Emacs for a while. Kind of fun, and then it kind of became”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“Well, and part of that was because, you know, in the last couple of years of grad school. It became really clear to me. That I was either going to be Mr. Emacs forever I was going to graduate. I couldn't actually do both.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“There's a slice of me that actually kind of buys into that Because people who make billions of dollars off of like a patent. And the patent came from literally a stroke of lightning that hits you as you lie half awake in bed. That's lucky. Good for you. The way that that sometimes sort of explodes into something that looks to me a lot like exploitation. You know, you see a lot of that in the drug industry. You know, when When you've got medications that cost. Cost you like $100 a day. And it's like.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source
“So, in general, I'm a big fan of open source. The way that it can be used to build communities and promote the development of things and promote collaboration and all of that is really pretty grand. Open source turns into a religion that says all things must be open source I get kind of weird about that because it's sort of like saying some versions of that. End up saying that all software engineers must take a vow of poverty. Right, as though.”
2020-09-24 · Lex Fridman Podcast · #126 – James Gosling: Java, JVM, Emacs, and the Early Days of Computing · IDENTIFIED FROM THE TRANSCRIPT · source