The Wu-Tang way

Play the audio to listen along while you enjoy the transcript. 🎧

I am talking you through outer space, which we can discuss as well.

Well, I’m on Starlink.

Yes. It’s amazing.

That is absolutely true. They’re in a lower orbit than the Ka band that the original direct PC Hughes aerospace satellites… Those are actually a lot further away. The Starlink constellations are relatively close. That’s why you can see them with the naked eye… Much to the chagrin of astronomers.

Well, I look up in the sky, and I like to… I also like to see human works flying around in space, just because it inspires me. It makes me think “Hey, the future is actually here.” By that, I mean, I find New York City, or Madrid, or Hong Kong, many places… Los Angeles at night. If you’re flying into Los Angeles at night, that’s the actual LA you want to see. Because you’re flying for an hour over just endless lights, and you’re like “Where does the city begin?”

Something that I find that – all of our human works, there’s a beauty to it. I’m not like “Oh, tear down human civilization.” No, I’m like “Build up human civilization.” Now, I understand the problem of littering space with a bunch of junk. That’s a different –

You could just send up a high altitude balloon and just hook onto one and just “Whoah, there we go…!” [laughter]

Well, actually, one of my next balloon projects, I’m hoping to connect to some satellites, actually.

Oh, well… So last year was my third year in a row of speaking at FOSDEM, the awesome Free and Open Source Conference in Belgium, in Brussels… And it was my third edition of the Go Without Wires saga. First year it was Go Without Wires, about Bluetooth. Second year, Go Further Without Wires, about local area networking with Wi-Fi… Last year it was Go Even Further Without Wires.

Oh, no. Not even close.

So it was about long-distance radio networking using LoRaWAN, which is a standard for using unlicensed spectrum, that’s free to use for anyone in the public.

Yeah, LoRa, like Long Distance Radio…

And then on top of that is a routable protocol called LoRaWAN. Like, wide-area networking. And the real pioneers in this space are the Things Network, which is an open source/commercial open source organization that has a whole network of these routers. Basically, you can connect to these local long-range radio networks, and then it has a backhaul to the internet. That way, you don’t necessarily have to have your own private network, it can just get routed through the Things Network to whatever cloud servers that you want to. So this is, of course, really useful for applications in industrial, or agriculture, or smart cities… They have quite a few of them. There’s a bunch of telcos that are also participating in this.

So the finale of my talk was a high-altitude balloon programmed with TinyGo, using a Raspberry Pi RP-2040 Pico board. Since these tiny balloons are called Pico balloons, so I’m very literal, I thought “Oh, I should build one with a Raspberry Pi Pico.” I mean, obviously… It was in the instructions, as far as I was concerned. It’s in the title.

Yeah. So I have a long distance radio, I had a GPS, I had an accelerometer… It was all hand-wired using a protoboard and wire wrap, just because I got into this retro computing thing. And it happened to be the weekend that everybody was talking about the balloons of Chinese origin.

Yeah. Now, to be fair, all parts are of Chinese origin… So it’s just sort like –

Yeah. I mean, certainly anything that’s in the toy category… So less than 250 grams, you don’t have to file a flight plan, or anything. It’s basically toy balloons, which –

…literally, I had ordered from Amazon and other such places [unintelligible 00:06:42.22] that toy stores. I mean, I only work with toys now generally, and it’s only if you’re gonna let me have anymore.

Yeah. Like, if you just give him toys, it’ll keep them busy, and he won’t get into much trouble.

So this particular balloon - it was on Hackaday; you can get some of the stats. It was called [unintelligible 00:07:01.07] the first one. We released it on Sunday there, and we did a countdown, we released it… It reached an altitude of about - I think somewhere between 6000 and 8000 meters, and it traveled approximately 400 kilometers, from Brussels, South of Orleans, France, before we lost contact.

So I don’t know if it was the French Air Force shut it down, or if the battery died, or something. I haven’t gone back to France since then.

Well, no, it didn’t land. It just kept floating. That was just where we lost contact.

Well, I mean, I imagine it landed somewhere, sometime…

No, no. But it was a very successful first flight. We got telemetry the whole way, every 30 seconds, thanks to the Things Network. It proved that the long-distance radio networking and support in TinyGo actually worked, just because – yeah, it was way out of my hands. So that was very cool.

Then we did a reprise of it at the GopherCon EU in Berlin in the summer. That launch was a little trickier. It traveled just – it was just a little ways north of Dresden when we lost contact. And I’m like “Oh no, not an American balloon going over Dresden. I won’t be able to go back anywhere.”

That was – the wind conditions were a lot more difficult, so… Both of those were battery-powered, and my next one will be solar-powered. That way I can actually circumnavigate the globe, and ideally, connect to some of the new satellite networks that are being built, that will be supporting this same LoRa protocol.

So yeah, I’d like to go around the world in 80 days, with a toy balloon, programmed entirely with TinyGo, that’s sending telemetry data… Just as far as citizen science, and reducing the cost of entry for experimenters, and explorers, and people to find out more of the things that they can really do.

So these are some of my hobbies, and also a great way for proving out some of the technologies. Like, if it works here, it’ll probably work in a more conventional farm vehicle, or something, that’s of terrestrial origin.

Well, like any wise person, I go onto the internets and find out what other people have done before I do anything.

There’s a whole community of Pico balloon enthusiasts who are doing –

Oh, yeah. Oh, yeah. They’re doing amazing things. So I borrowed some of their design ideas. Specifically the balloons are toy balloons made of vinyl. And you have to stretch them out. They’re filled with helium, that you could just get in any baloon-type party store. In fact, that’s where I get my helium, is from party stores. Pay with cash at the party store. No, no… [laughter] So these – they’re transparent, ideally, so that some can get through to charge whatever solar cell…

This one I didn’t have the solar thing set up. I actually had the equipment, but I didn’t try to use it, because I had some software problems actually with the low power mode. So I had it working to charge, but it would discharge in about five minutes, so I couldn’t… You know, the idea with these things is it recharges when it hits the sun, wakes up, send some telemetry data, goes back to sleep, and so on, as long as it’s in sunlight… You know, generally done with a thin film solar panel and some super-capacitors. So I had the design, I built it again from specific parts that I happened to have on hand, and I was able to do with a wire wrap… But these balloons - you stretch them out, and since gas expands when you hit higher altitudes, that’s the reason why there’s four of them, is that each one is only partially filled. You fill them partway, that way when they reach, you know – what I thought was gonna happen was that it was going to go a lot higher, and then pop. What instead happened was it reached apparently an altitude where it was just stretched out enough to not lose any gas, or have any bursting.

Yeah, beginner’s luck on that one. The second, it was a little harder, just because there were a bunch of big trees right there in the venue… So that’s always very exciting.

Oh yeah, there’s no controlling. They’re just release, no catch. They just go. Generally, this type of high-altitude ballooning is done either by people doing this with a toy balloon thing, or people will use latex balloons with a payload with a parachute. With those, you actually file a flight plan, to be responsible, to make sure that you’re not going to interfere with any air traffic, since…

That’s something – I mean, just because there’s no actual law preventing you doesn’t mean you should just go and do something stupid.

A tiny modicum of common sense, perhaps… I mean, you can’t think of every possibility, but it’s certainly a good thing to not release balloons right next to, for example, the US Naval Air Station in San Diego… Which is why I did not do that at GopherCon US… I’m like “You know, this is both stupid, and it’s also very rude. Like, impolite. You should know better, and also, you should just know better.”

Yeah, no, you’re definitely on the wrong people’s radar right away.

Well, I’m a known white hat, which is why they would be so angry.

No, it’d be just a matter of like I actually do know better.

This is also a matter of – like, what is your purpose in doing this? My purpose is to help show young scientists the opportunities they have to do some exploration in a way that costs very little, and that gives them a chance to learn quite a lot… But these are things that are quite important, not just in the future, but really in the present.

A great example of citizen science being a lot better was a cool project a few years ago when the Fukushima incident occurred, called Safecast. And it was basically being able to turn your mobile phone and connect it to turn it into a homemade Geiger counter. And that way, they could get a lot more accurate readings of the type of data, just because the government would go in, they would take their readings of certain meter height, at a certain frequency, and it was a relatively small dataset. So this allowed a bunch of citizens to start collecting data. And one of the things they found, for example, was that there was a lot higher concentration of radiation lower to the ground than at the two or three meter height of these poles. So that was one reason why it tended to affect younger people, pets, and animals, and people who are in wheelchairs, just because they were lower to the ground, and so this higher concentration affected them more than adults. So this is data that they wouldn’t have had if they didn’t have just people who were interested, who cared about this. So it’s a great example of open science, open source technology, working for social good… To me, that’s the sweet spot of why we do this.

Break: [00:16:05.14]

Oh, sure. Sure. And this was using, I believe, some photographic parts that – Safecast. I don’t know all the details. I did not make one of these myself. I’ve got enough problems without ordering parts that could be used [unintelligible 00:18:56.27]

So a Geiger counter is a device whose purpose is to be able to read the ambient level of radiation in a local area. And they’re generally used when you’re working around sources of radiation, whether they’re natural ones, like uranium ores, or artificial ones, the X-ray machine, for example. There’s a reason why when you go in and get X-rays, that the technician - first of all, they leave the room, that way they’re standing on the other side of a lead shield. Lead is a very dense element, and so the X-rays are unable to go through the lead. That’s why they give you a lead apron to put over your sensitive parts when you go in for one of those X-rays, is to protect you from this radiation, just because repeated exposure… This is actually one of the reasons why it’s going to be quite difficult for us to leave the Earth and go to, for example, colonize Mars, is the colonists, by the time they got there, would be barely alive, if alive at all, just because of the radiation in space.

So a Geiger counter is one of the original - it’s a very old device, it’s a very simple device, generally speaking, that is able to measure this ambient radiation. So the Safecast team, they were basically using an Arduino connected to some salvage electronics parts, to be able to then connect this to your mobile phone and take readings that you could then upload to their web-based data store.

No, just even staying in a high orbit.

Yeah, that’s one of several belts in the ionosphere, which protects us from – and it’s a very thin… If you look at the actual atmosphere relative to the planet, it is a thin little tiny piece of transparent… It’s not even aluminum.

It’s like jello. It’s like this tiny little skin, you know…

Yeah, that’s just protecting us from literally getting cooked.

Oh, I think we’re a long way. There’s a great – I can’t remember the name of the couple that wrote this book… It’s about how to colonize Mars, basically. That’s not the actual title. We’ll have to look this up.

So they started out super-optimistic, they’re like “Yeah, we’re gonna see this in our lifetime. And by the time they got to the point where they could actually write the book, the enormous reality check of the distance between the technology we have today and the technologies that we actually would need is quite vast. Just to keep people alive between here to there, let alone –

When you get there, now what, right?

I mean, if you live in a modern city, you’re already drinking the refined – the water system in your city is already purifying people’s urine, and you’re drinking it today, okay?

This is the municipal water supply in most major cities. But it’s also got other sources, right? On Mars, this is it.

This is the only water we’ve got.

So I think that it’s a great thing for the human exploration of space… But the reality of where we’d actually need to be to get there is a long way from this… You know, Spaceship Earth is the spaceship. This is the place. We have to maintain, preserve, and improve this one, because it’s going to take quite a few more generations before there’s any reality of being able to send humans to survive, even one generation. It’s going to take an incredible collective effort just to do that little tiny bit. And Spaceship Earth is the place, so…

We have one, it was called biosphere.

Yeah, Biodome – that was probably one of his better movies… Which is really frightening.

But that was actually based on the true story… I know, hard to believe. So they built it in, I think, the Arizona desert. The idea was to have a totally self-contained system, where - I forget how many people, like seven people entered it, or something…

No, they all left, but they really hated each other by then. They didn’t actually speak to each other for several months, one group and another…

[00:26:08.04] It was kind of an amazing experiment.

Oh yeah, that’s even more real.

Yeah, they’d still be doing it if that existed at the time.

Maybe somebody should pitch that.

But I mean, they did learn quite a lot. One thing they learned was having so many different environments was very impractical. That having a smaller number of environments was more practical for being able to try to maintain continuous ecosystems… Because they had to do a lot of maintenance. I mean, it was full-time maintenance work.

Yeah, it was like some ‘70s movie… It was Kumbaya, and “Hey, we’re hippies in space.” And then the reality is like “Yeah, but I mean, man, we’ve got to do weeding in space. All the plants are trying to grow, or dying, and the ones we don’t want are taking over… And we’re in space. What do we do now?”

But the worst thing about it though is they didn’t keep going. They stopped. They did one run, they were like “Wow, that was really crazy”, and they shut it down. They needed to keep doing that for 20-30 more years to really learn something as far as science. There’s a big difference between R&D for scientists and R&D for businesses. Scientists, they go in and they do a bunch of research, they spend a bunch of time, they come back and they say “After spending my entire life, I’ve discovered that the answer to that question is no.” And everyone’s like “Oh, Nobel Prize. Amazing.”

Now, you try to do that when you’re working for some company; forget all your whole life’s work. Two months later your boss’s boss comes in “Oh, how’s it going?” “Oh, I’m starting to think we can’t do this.” Like, “What?! This program’s canceled. You’re fired. Everyone.”

If the answer was Yes - we were paying you to figure out how. This is not science.

This segues perfectly to the conversation about machine learning, I think, but… [laughs]

Just because yes, if your discovery is that something isn’t going to work, this is an enormous contribution to the community knowledge of humankind… Because you figured out “Oh, let’s try this other direction.” But this is not something that’s commercially exploitable, generally speaking, and we need quick results. And this is one of the big problems with fundamental research and for things like machine learning, and commercialization of things, which must be privatized now… Whether they work or not, we just need monthly recurring revenues. You’ve got to do whatever is going to take to get me there, and if you don’t - again, you’re quite fired.

But do not look at the man behind the curtain. And it’s a classic case of Roy Amara. Roy Amara was the guy who said we have a tendency to overestimate the short-term benefits of technology, and underestimate the long-term ones. I’m gonna make an unpopular prediction… 90% of the companies that are trying to do machine learning will fail, and the reason they’ll fail is because they won’t actually produce anything of value whatsoever. Perhaps of negative value. The other 10% will survive, not because they’re actually doing anything worthwhile, but because they’ll figure out how to do something. And this is just –

Right, that’s part of the process. It just gets distorted a bit by large sums of money. There is a great video… Every entrepreneur’s putting “machine learning” in their investor deck, whether or not it makes sense.

And this is kind of throwing away the baby with the bathwater as far as, okay, a bunch of this is sort of nonsense… But that doesn’t mean we shouldn’t be trying to learn something from it. But with so much noise and so little signal, it makes it quite difficult to sort it out. I did a talk in Spanish called “That machine always lies.” I haven’t ever done it in English. Hopefully, I’ll get the chance to do it at some point. But it was a take-off on that my brother always lies, the logic puzzle.

So it’s one of these –

It’s more of an example of exclusive or. So you are a traveler; in some versions of the story you’re a soldier, trying to go home from the wars, others you’re a traveling merchant… You come to a crossroads. And standing at the crossroads are two identical twins. So one of them – there’s a sign, it says, “One of these brothers only tells the truth, and the other one always lies.”

You can only ask one question of one of them, and you have to figure out which way to go. So it’s one of these classic logic puzzles that - I think it’s been around since maybe the 1600s, or maybe longer… It probably was around longer, they just they never got around to writing it down.

So think about it this way… One brother will always tell the truth, the other one will always lie. You’re only allowed one question. The question is quite simple. “Which way would your brother tell me to go?”, you asked one of them.

It doesn’t matter which one.

Exactly. So this way the one that always tells the truth will tell you about the lie of the brother who always lies. The one that will always lie will simply lie. So you go the opposite way of the way that either one of them tell you, and that’s the correct way.

You don’t know which one is which.

Well, no, it’s perfectly consistent in this example. Something like exclusive or. Maybe a better example would be Zeno’s paradox.

Zeno’s paradox is the oldest paradox I know of. So Zeno is from Crete. And Zeno says, “All Cretans (people from the island Crete) are liars.” So now, here’s the paradox. If he is telling the truth, and he is from Crete, then it is impossible that all of the people from Crete are liars, because he simply told you the truth. On the other hand, if he did not tell you the truth. So you see, this is known as Zeno’s paradox, and we’re just touching upon the paradoxes which exist in human thought. It’s not perfectly rational. So how to encapsulate that and reduce it down to any form of quantitative calculation is something which we actually don’t really know how to do. So calling it artificial intelligence is out of the gate “My brother always lies.” That does not mean these things are not useful potentially, and that we should not learn from them. But pretty much everything you’ve been told is not actually true.

[00:34:18.11] And a great example of this – I mean, let’s say you have a company, and your company does some database sorting. Don’t you want people to think like “This database sorting is so powerful that it could literally destroy human civilization as we know it. If you buy this database sort, index sorting, this query engine, it literally could destroy society as we know it.” You as a CEO would be like “How do I get my hands on that thing? I want that baby.” You wouldn’t be like “Oh my God, we could do a database query that could destroy our entire planet.” You’d think like “Man, I’ve gotta get that before the other guys.” If you’re selling this database engine, you literally want people to think it’s as if you have nuclear fuel inside the database engine.

Now, just substitute machine learning for database engine, and I believe we have a pretty good view of the distance between hype and reality, and how that is a great marketing… Like, everybody wants to get this thing on their side, get it away from their competitor. And before we go into some other area… I think it’s great to read the paper that really started the whole controversy from Timnit Gebru, the researcher at Google. The paper’s named “On the danger of stochastic parrots.” And I don’t read a lot of academic papers; I’m not an academic. I’m on the technology side. I’m the person who’s looking for other people’s research to turn it into my development… Because I have to go to the money people and say “Yes, this is going to work. These people proved it.” Not “Well, we don’t know.” So I’m looking for research that I can turn into something.

Because I’m a technologist. That’s my thing. So I don’t read a lot of academic papers, but I’ve read a few. This one’s quite short… And as academic papers go, it’s quite concise, and quite clear. And by the way, it’s the paper that got her fired from Google, with much controversy. And this is before the whole Open AI thing came along and sucked all the oxygen out of the air as far as the conversation about machine learning… But I read this paper about maybe a year ago, a year and a half ago… And the first thing I thought was “Yeah, okay, cool.” But the next I’m like “Wait, they got fired for this?” There’s nothing in there which could possibly be objectionable. The ostensible reason was for lack of academic rigor.

Essentially, it was saying that these large language models - because that was the generative AI that the researchers were concerned with - they need to be looked at as far as what is the source of the training data, what are the implications for its use as far as on society as a whole, and on specific working groups, and people affected by it… And that we also need to look at the economic and carbon cost of the computation necessary to train and use of them. That was it. It just said “We need to look at these things.” So nothing really controversial.

[00:38:07.17] Okay, I thought I summarized a few of those… But that’s a good summary.

My bad. But it was not saying “We should not do this because of these things.” It was saying “We need to analyze on these axes. Here’s a framework for analyzing the impact of this particular technology set.”

There’s nothing to disagree with. I’ve read this paper twice. First, just because I knew of it, and then the second time, just because I couldn’t put my head around why this was such a big deal. But then it made me think… You know, it’s very hard to get a person to understand the thing when their job depends on not understanding that thing.

Right. “Nothing to see. Nothing to see here. Move along.”

And this is where the open source machine learning to me is such an important, genuine open source. So when Meta AI’s Llama first leaked, I found it absolutely fascinating. Because first of all, these things don’t leak. If you ever signed a nondisclosure with one of the really big companies… I mean, let’s keep in mind that one time, one guy had an iPhone that he had at a bar, and literally the San Jose Police came with guns [unintelligible 00:39:42.20] dragged off to the jail, like this guy was some type of bioterrorist, right?

Right.

That’s very extreme, but just dial it back only the tiniest little bit. There’s more lawyers than they have people in your whole social network.

Right, exactly.

No, no, no. I was using this as an example.

Right. But the big hyperscalers have not gotten more friendly and nice since then. So when Llama, the model first leaked – ostensibly, it was given to some researchers on their specific agreements to not publish anything from it. Within 72 hours or something it was on torrents, and people were downloading it… And all of a sudden, it was everywhere. Now, I don’t know anything, but it just seems to me, like, there is no human being brave enough to say “Oh yeah, no problem. They won’t catch me with these watermark things.” So I have a slightly different theory, which is a bit more… You know, when you’re losing a game of chess, or you think you are, or poker or whatever, and you just flip over the board… Just like “Ah, we’ve got to start over.” Right?

Adam, you asked me about conspiracy theories. I’m trying to give you one here, man. Come on, I’m giving you what you asked for…

Plus, it’s a PR thing. I mean, you’re losing the mindshare. I mean, these are a bunch of really serious researchers who’ve done a lot of good work over like many, many years. These are not just randos like myself. These are actual people, who know things.

And all of a sudden, everyone’s like “Oh, Open AI, Open AI…” And if you’re on that team, you’re probably not too happy about this.

I mean, research is very competitive. Whether it should be or it should not be is – I’m not an actual researcher.

So Llama leaks out, and that really sets off the Cambrian explosion of suddenly new things popping up day after day after day. People take this model and quantize it, and then Alpaca is a smaller, lighter version of Llama… And then - I mean, every two days something new is coming out. So one guy, just on the internet, says “I wonder if I could run this on my MacBook M1.” And like any of us, he decided to devote his weekend to it. Sure enough, kind of got something to work. Because usually you’d be like “Oh, I’m gonna stand up some type of cluster of machines, with a bunch of GPUs.” You know, it’s a big person’s game, with lots of hard-earned money to throw at it… So this person’s like “No, actually, I could run this on my laptop.” Gets it to work. All of a sudden, it changes the game yet again. So “I made a few early contributions to that project, just because this is very near and dear to my heart. Take the fire and give it to all the humans, and damn the consequences, because if we don’t, it’s going to be so much worse than if we do.”

Now, I’m no Prometheus, I’m gonna be running like hell. Plus, I wasn’t the one that actually stole the fire initially. I just passed it out to a couple people along the way. Don’t blame me.

I’m just the of the crew, man… [laughter] You want the big boss over there. But I mean, it really is setting off – it was the beginning of a whole… You know, now there’s oh so many, and there’s so many things happening in so many areas… And the vast majority of the interesting work is happening in the open. And I think this is a very good thing, because it means that the means of computation – seize the means of computation, as Cory Doctorow says. I don’t think it’s good to, on the one hand, limit this to only big companies that have the money to do something with it, or on the other to have governments that are regulating it in the way that favor those big companies to the exclusion of independent and interesting and innovative things that are happening out here at the ground level.

Break: [00:44:45.02]

Well, I mean, I can’t really comment specifically on Meta’s particular take, just because I don’t know anyone there… But I think it’s part of a larger trend, saying “Oh, the end of corporate open source.” I think we’re nowhere near the end of corporate open source. But we need to compare open source as an asset category – I mean, Meta throwing money at open source is because they’re looking for relevance in the world that they’re losing relevance in. I think this is very similar to what Google’s doing, in a lot of ways, struggling to try to figure out “Oh, how do we keep our revenues going? What’s the next thing?” But I don’t think they know what that is. I think that open source is a strategy now, because it’s a way to try to win the hearts and minds of people, and to have them invest their time and their energy. But they also think that the rug pull is kind of the number one strategy in corporate open source now, private equity open source…

No, I think it’s a very bad strategy.

I think if you say it upfront, “Look, we’re a business, we’re in here to make money. This is the line. This is the free part. This is the paid part. Join us if you like that, if not, don’t.” You know the rules getting in, you could decide “Do I want to play or not?” These are the table stakes.

Changing the rules partway - it’s very much Darth Vader telling Lando Calrissian. [unintelligible 00:50:21.15] This is like “You should have had your plan to get out of Cloud City a while ago.”

When they first arrived, you should have been like “Yeah, yeah. The meeting is when? Oh yeah, I’ll be there. I’ll be there”, and you’re like “Okay, we’re out.” Don’t even take the meeting; run for your lives. And I’m not judging anybody, because the money changes them. If I had a bunch of money, then I’d be changed, too. You’d be like “Oh, man, that guy Ron used to be so cool. Wow.” I feel like the Grateful Dead… When they were asked “Aren’t you selling out?”, they’re like “We’ve been trying to sell out for years, it was just no one was buying.”

But then I think it’s the change of the rules of the game midway. Or not even midway, late in the day. But also, let’s define some new categories. Corporate open source actually now is either directly – like a project that’s a pet project of one of the hyperscalars, or it’s one of the big Linux Foundation type groups, where it’s basically not something you get to join as an individual. Like “Hey, can I get in the club?” “Uhm, yeah, sure. You’ve just got to pay our annual dues of this many bazillion credits, and you’re in. No problem.”

So I mean, that’s a way of making sure that it’s sort of a cartel; like, they control the narrative in a way that doesn’t generally threaten anything… Just because something generally new and open source that destabilizes a bunch of existing companies is quite dangerous to them, and they don’t want that to happen without some way to control it. I mean, it’s just a way to perform your fiduciary responsibility to your shareholders.

Buy that company, and make them go away.

Oh, man… Yeah, no…

I have a slightly different attitude… But I’ll get to that in one second, because I want to talk about the second kind. So you’ve corporate open source, then we have we call private equity open source… Private equity open source is what happens when a company gets bought by a big company, and then their whole purpose is to basically extract all the value out of it with whatever’s left. There are some big companies that do this; you probably have seen them. Some of them, their strategy is go after mid-cap companies, buy them… This has happened to a number of companies. Travis was a particularly sad example, just because a lot of us depended on Travis CI.

They got bought by private equity, and then squeezed all the juice out. I would say IBM’s strategy, with what happened with Red Hat, was very much an example of that same sort of “Let’s just get all that we can out of whatever we’ve got in this company left.” And again, I don’t judge these people.

Yeah. It sort of indicates – the general pattern for these companies when it’s closed source, and it’s mid-cap companies acquired by PE, it generally means the game is over; now it’s just cut it up for parts, and get as much as they can. And that just means it’s kind of over. Like, the dream has ended, and I think - is that the case with HashiCorp? I don’t know the answer to that. But it is interesting. If the cycle of time – like, the time it takes from founding of a major important piece of open source that is relied upon as key infrastructure, the time of creation to the time where it’s basically like – it’s not leaving, nor is it going anywhere; like, it’s not going to expand, nor is it going to contract easily, so now it’s just like squeeze the value out… We see this with a lot of other private equity investments, into other categories, and looking at open source as an asset category is somewhat interesting. It’s hard to evaluate exactly. There’s a lot more value created by open source than captured. Right? And that’s a good thing. That makes it a public good. It doesn’t cost me anything for you to use my open source. It costs me something to create it.

[00:56:26.23] So this goes kind of to the third model. So we’ve got the corporate open source model, we’ve got the PE open source, which is like “Okay, rug pull, extract the value, damn the torpedoes.” Obviously, there’s little tiny individuals… But then there’s this other category, which I like to think of as the volunteer fire department model of open source, or the federation of open source. So what is this? If you are doing something with open source that benefits you, and I am doing something with that same open source that benefits me, and our interests are aligned, then we’ll work on it together. Like, we’re going on an adventure; we’re in the same dungeon party, because we’re trying to do the same basic thing. And TinyGo is a great example of – you know, TinyGo is a Go compiler written in Go, licensed with the same BSD license that Go is, on purpose, because the idea is that nobody really owns TinyGo. And nobody really can. The idea’s that you use TinyGo to make something of value; use it to build your business. Take TinyGo, use it, make money, be successful, and contribute back. Put in time, put in money… We haven’t had as much of that. But people are very welcome to hire Hybrid Group to help them, or - you know, we’re probably going to introduce some paid support offerings; not as an exclusive thing… I mean, I’d like to see a dozen consultancies that have consulting practices based specifically around TinyGo implementation. Not just, “Oh, come to Hybrid Group for these things.” Because it’s about letting 1,000 flowers bloom, and it’s also about – like, if you look at the people who actually work on TinyGo as their full-time activity - for example, there’s some people at Fastly. Damian Gryski and Dan Kegel in particular, who - why are they doing that? Because Fastly’s compute platform, which is a WebAssembly system interface running WebAssembly in the cloud - it’s really a cornerstone of their technology platform that they charge customers for. So it’s in their interest to put people to work on TinyGo, because it benefits them. We don’t need a foundation; it’s more of a federation of like-minded interests, and it’s a model that is a bit more sustainable, only because - let’s say that tomorrow I decide “I don’t want to do TinyGo anymore”, which, I want to keep doing TinyGo, by the way…

Or I just decide “That’s it, delete all the repos.” It’d be the same as OpenTofu. You know, the internet is designed to route around blockages. And no human institution lasts forever, since they’re made of people. No one’s perfectly incorruptible. Some people get tired, they have to retire, do something else, do a paid job, whatever. The purpose is to make it so that these things are as anti-fragile as possible, so that they can withstand whatever changes occur, and the core idea can keep moving on if it’s a real value. But the only way to make this work is to be like the Wu Tang Clan, where each one of the members of the clan can go do their own recording, sign to a different record label, get whatever deal they can to get paid… They don’t have to go through this centralized hierarchy, “Oh, everyone’s got a–”

[01:00:05.09] Generally speaking, if you and I have a band, and we’ve recorded, and we would go to some record label… So we would sign a record deal. And then if we had a side band, we would have to sign with the same record label with that other band. We couldn’t just go and do our own thing. Oh, no, no, no. If we just did a side project of just recording some music on the film, they would want a piece of that as well.

The Wu Tang Clan’s big innovation to the music industry, in part, was anybody who’s in the crew can go and sign with whatever record label they want, you can bring in whatever guest star it is you want, you can do whatever deal you want, do any deal you can. And this is sort of the same thinking that we have with the TinyGo crew. Anybody is free to go and take TinyGo and use it to make something of value and to make money. And that’s how it’s able to be sustained, is because then those same companies and people put time back into it.

So it’s a little different than the swing for the fences VC mentality. Why we haven’t taken investors - we’re happy to take grants, where you give money and we don’t promise you anything, and we don’t have to give it back.

But we’re not looking – TinyGo itself is not a thing that… You can only invest in it by actually rolling up your sleeves and doing the hard work, or paying the people to do it.

It’s highly informal. Part of that is because I’ve seen a lot of obsession with governance, that has taken a lot of time and energy and not really yielded substantial benefits. They still had massive drama, and they forked the project, and went off on their own, and everyone hated each other and was all mad. And they had all kinds of governance documents. We can’t get around, nor do we wish to get around the fact that open source collaboration is first to human activity, and only second does it have to do with code and technology. It really has to do with the attitude about how you wish to approach it. I think of it – you know, because the big dictator implies a certain centralized command and control, which has worked really well for certain projects… Sometimes despite that, not because of, I think.

I look at it more like I’m the park ranger, the game warden, the curator of the museum, not the owner of the park, not the owner of the museum. Because it belongs to everyone. I’m just the steward of it to try to – like me, personally, that’s my attitude.

And there’s always the opportunities, if somebody genuinely is like “We want to take it in this way”, there’s not a consensus for doing that; we’re taking it in our own way. They should do that, that’s not a bad thing. Like, we don’t have to all – if we reach a fork in the road, it’s not two brothers. This time, it’s actually a business decision about something or another.

[01:04:08.10] And I mean, TinyGo has grown into a very big thing in WebAssembly. It wasn’t originally created to do that. That was an emergent property of the ecosystem. And one I’m very glad for, and I’m very involved with now myself. But the original vision with TinyGo was very specifically for small embedded devices, and bringing Go to the microcontroller. And then it just so happened “Oh, we could actually compile this to WebAssembly.” There was some very nascent support in GigGo for WebAssembly at the time, and that’s something that the LLVM toolchain that TinyGo was based on - not BigGo, but that TinyGo is based on. So it’s like “Oh, this would be a cool feature to add. We should do that. No real specific, more just like “Oh, it’s like a low-hanging fruit. Some people seem really interested in this. We should do it.” Next thing you know, “Oh, wow… TinyGo is so much better for WebAssembly than BigGo.” And we’re like “Wow, it is? How interesting! Why is it better? What does it do?” Like, we didn’t even know ourselves some of it. We were just genuinely interested. It was an emergent property of the community, of a problem that they wanted to solve, that BigGo was not solving for them… So a bunch of people started devoting time and energy to improving that Web Assembly support in TinyGo. And then the Web Assembly system interface, which is Web Assembly on servers, and serverless… The Web Assembly not in the browser. You know, part of the fact that we were interested in it ourselves, that also we move a lot faster than BigGo. We can. We can innovate a lot more quickly. We haven’t given a 1.0 guarantee yet, so we can change things… We’re not – even though largely, I would say the Road to 1.0 for TinyGo is more about the hardware interfaces than it is about compatibility with Go itself. Because we’ve had pretty good compatibility for a while. But it was very much an emergent property of the community.

And as more and more of us said “Oh, wow, WebAssembly… That’s really a very interesting thing. We have some problems we wanna solve with that”, and Go being a really good language, for whatever, that this has been an aspect of TinyGo which was not something that was part of any master plan. It’s something that the community wanted, that the community is, and does, and is not at all – there’s no need for it to be a zero-sum game. Oh, it can either be for embedded or it can be for Web Assembly, or it could be for Linux, or for Windows, or for macOS - that’s a false dichotomy. It could be for whatever we collectively want it to be for. But again, with that sort of curation in mind - like, you can share the park, but you can’t just like go in and start digging it up to build your own little thing, when that’s disturbing the flora and fauna of the ecosystem. And so that’s in a compassionate, kind way… But also looking at like the why. Why is this person asking for this thing? Usually, it’s because they either have some need, or they can’t figure out how to get the thing you have right now to do the thing that they want. Either way, that’s kind of on you. If it’s a need they could solve some other way, you could recommend that. If it’s a thing that your software doesn’t do yet, but that it could, you could mention that, and say “Oh, maybe you can help.” Sometimes they’re like “Oh, I don’t know enough programming.” Yeah, but they already took the project in a better direction just by saying “Hmm, here’s this thing that somebody might need.”

[01:08:19.28] WebAssembly again - a really great example. There’s a lot of people who are very involved in blockchain applications. I’m not really one of them. I don’t judge people for what they choose to do with their computational power. My currency is render graphics, play games, churn through large language models… This is on you, not on me. I’m just trying to create technologies that are useful.

So there’s a bunch of people who are using TinyGo specifically because they wanted to use Web Assembly as part of their engine for doing their processing… And so they were looking for basically what we call Web Assembly unknown, Wasm unknown, which is sort of a naked Web Assembly. It’s web assembly with no expectations of what the running environment would be.

So for the listener, if you haven’t checked out WebAssembly, first of all, do. There’s lots of interesting things happening. You can run it in your browser, you can run it on serverless applications like fermion spin, you could use it to build plugins for your current software, like Extism, or you could use it to actually run on microcontrollers and embedded devices with TinyGo and Meccanoid. So there’s all sorts of different, interesting areas to do this in.

So this group of blockchain enthusiasts said “We really want to run TinyGo with Wasm, with no external dependencies.” And the people who are doing Wasi are like “Oh, that doesn’t sound very useful”, just because it doesn’t have any ability to call any specific thing. And these folks were like “Oh, that’s okay. We don’t care. We have our own APIs.” So it took a while before it actually turned into something which landed in TinyGo, just because it had to build a little bit of a critical mass. Just one person wants it, just one or two, they’re not willing to do any programming work on it, but they’d like to have this feature… Okay, that’s a signal of intent. There’s maybe other people. Is it useful for other things as well? Well, yes, as it turns out. That same pattern of Wasm unknown is exactly the pattern that’s being used for Meccanoid, for running WebAssembly on embedded devices, like microcontrollers.

So if it was not for the blockchain community sort of priming the pump of starting to think about this, then those of us who are actually interested in using that same pattern for something completely different would not have maybe worked on it and adding it to TinyGo. So again, the community is defining what the thing is, because the purpose of TinyGo is to serve the community’s needs. It’s a means to their ends, whatever those happen to be.

And you can still record the desk that only one person has, that’s like $6 million or something…

And you could use TinyGo to do it.

I’m sure I read it somewhere.

Well, first of all, you know, you’ve gotta have some flow. I mean… [laughter]

Most likely you don’t, okay? I mean, you know… Like, not every one of my songs was actually any good. Luckily, I didn’t play it for too many people. They were like “Oh, wow. That’s a really bad idea.” I’m like “Oh, yeah? Cool…”

But it comes to like the thing that it is… Like, you’re not gonna make money off your programming language, man. I’m sorry, okay? You’re probably not. It’s just not going to happen.

I know. All these people are like “I’m gonna make my own language, and I’m gonna be retired, with a mansion and a yacht.” It’s like, “No, you’re probably gonna make – not only are you not gonna make any money, it’s gonna cost you a great deal of money just to even do this thing.” Now, lots of money is made off of programming languages, but it’s not the language.

Like, nobody’s going like “Oh yeah, we sold Python.” No, it’s like “Yeah, we made this thing with Python, and we sold it for a bunch of money, and…” Well, Python’s really cool. I mean, pick a language: Go, Rust… Any language. The money is not there. The value creation is. It’s creating enormous value. I mean, probably it’s the most… I mean, I will take a giant leap and say the single most valuable asset on Earth, which is consistently undervalued, is the collective all of open source. Like, how much is that worth? It is worth a lot. I know there was a study some university did, trying to figure out “Okay, if there was no open source, how much would it cost to write it all?” It was like a bunch of trillions. Not to mention like “Okay, we’d better get started, because we’ve got – okay, we’ve got a $3 trillion budget, but how are we going to spend it? Like, it took years. It’s not like we’re gonna like “Okay, we know exactly what to do now.” Right? So it’s an emergent phenomenon.

So that does not mean that there’s not ways to do it. But I think it’s not – like, a project which is clearly part of core infrastructure for a bunch of companies is that they’re not planning on selling the cloud-enabled version of themselves in order to make money… Because that’s a lot of – oh, yeah, it’s this cool server that does some thing. You can work on it, and you can stand it up yourself… Or you can use our cloud service. And then the next week somebody’s like “Oh yeah, we could stand up a cloud service.” And they already told people like “Wait, no, not like that…!”

I think about it more like “Hey, if they could do the same thing we’re doing, but cheaper, we should just buy it from them and resell it ourselves if we’re trying to make money.” You have to think about - do you care about it being from you? Do you care about it existing? Or are you trying to use it to make a living? There may be some overlap in those things, but it’s not – this is not a strategy that’s going to work for every open source project, especially if it’s a thing where the cloud-enabled version is the thing you’re going to sell… Unless you’re perfectly cool with the fact that your own direct competitors are your collaborators in the project.

Now, if you’ve got some secret sauce that you can add, that you think is gonna make it better, but that can’t be copied… Like, “Oh, our UI is so much further.” Well, yeah, they can look at your UI, like “Oh, we should do that.” Like, okay, that’s not enough. Like, you have to have some differentiator. Either that, or it needs to be very verticalized, like it’s for a particular industry. Go for industrial computing. Go for automotive. Go for entertainment. Go for whatever – like, verticalized, as opposed to horizontalized.

Oh, I can keep going. I’ve got a pitch deck, too.

Uh-oh, I might’ve said too much.

[01:15:58.28] Yeah, no, I don’t sign – I mean, I’ll sign them if pressed, but I’ve never asked anyone else to sign them. Like, I respect the customs of others, so I’ll be like “Yeah, I’ll sign your NDA.” But I wouldn’t ask me to sign mine. I’m like “Are you kidding?” If hearing my idea’s enough to just go do it, please hire me. [laughs]

Well, yeah, that’s also quite hilarious. Like, come on…

Exactly. Like, they’re missing – but again, it’s more opportunistic using like “Oh, open source. Yeah, we’re gonna totally wrap ourselves in the open source flag.” It’s like, there is none. Like, “Yeah, we just want to talk to like the open source community.” Like, there’s no single open source community; there’s many. In fact, one could splinter into two, or three, or ten, at any point. I mean, you actually can’t – it’s an algorithm, it’s not a formula. You don’t just substitute the numbers and out comes open source at the other end. You turn the crank, and you don’t really know what’s gonna happen. Anything could happen at any point. It could be magic, or it could just be like we spent a bunch of time to – we redid the wheel, but our wheel is square, and made of wood. And then all of a sudden, one day we saw round, rubber wheels and we’re like “Hey, our project is now archived…” [laughter]

Right. “That’s it. We’re done. Thank you. Thank you, good night.”

Well, again, it’s like, do you want the ego gratification of “Oh, my name’s on it”? Or do you want to solve the actual problem, and do something else? Actually, Dr. Nick Williams, he was a person who really instructed me… He gave a talk about this, about retiring open s– this was many years ago, back when we were all involved in Ruby. I think he’s still in Ruby. I still love Ruby, but I haven’t actually used it in years. But hugs and kisses to everyone at Ruby, because I think it’s a really cool language, and a cool world. He did a talk, and he was mentioning about letting go of projects. And his metaphor was “My kids-”, he has a bunch of kids, “I don’t just have them living at home forever. I mean, eventually, they have to leave. And either they go off and they do their thing, or whatever.” I was like “Whatever?” You know… [laughs] But maybe the kids metaphor - that was too extreme. But it was more that, you know, you don’t have to maintain the project forever. Either other people will rise to the occasion, or the thing will be replaced by something else… But it’s not on you. Like, there’s nobody – and if there’s something generally better that you could actually use yourself to solve the problem you started out to use… Well, you learned something, and it was cool, and now - yeah, move on to the next thing; jump on another project and help them.

Some of the contributions I’m most proud of are a single pull request I made on someone else’s project, where I was able to solve a problem… And I’m really proud of a project that I maintain, GoCV, which is the Go wrappers around OpenCV, for the same reason that there’s a lot of people who’ve made one pull request. It was missing one thing, and they were able to figure out how to find that thing was missing, what they had to do to add it, and it was successfully added. And their problem was solved, and they moved on, because they were trying to do a thing, not be an open source contributor. They were just trying – to me, that’s a massive success as a collective. We’ve made it possible for you to solve your problem, and to help the next person along the way. And yeah, it took a lot of work to do that. It’s much easier to just do things directly.

But you have to be in the long game if you want to create this sort of sustainable… You know, maybe I’ll call it sustainable open source. It’s what VCs would call a lifestyle open source.

[01:20:01.15] And for them it’s like an insult.

For me that’s like “Okay, cool. That means – maybe I want to be in, because I don’t want to shoot for the stars and crash into a mountain. I don’t want to actually crash.” Plus, we can actually get up that mountain so many other ways that don’t involve rocket fuel, and half destroying the village that the other half of the rocket lands on… Like, we could just hike up there, and with our camera, and get the shot, and we’re done.

You make money off of the thing you make with it, not off of the thing itself.

Or even hang it up. Like, that’s okay, too. Like, thank you for your service. You’ve done a lot, you got us this far. We’ll take it from here. You know what I mean? That’s – I really respect and admire the people who know when to do that… And usually, we don’t as a community – we don’t have the sensitivity. A lot of people don’t have the – we don’t talk about mental well being. I don’t wanna say mental health, because mental health sounds like illness. I’m gonna use the term well being, only because it makes it sound more like that sustainable. Mental illness - “Okay, you’re better now. Back to the salt mines.” Versus well being, like “I’m sorry to inform you, I’ll be unable to come to work this week, because I’m feeling too well. I’m feeling too good this week to come to work.”

Not like “What?!” If we were athletes, we would have like personal trainers, and team physicians, and they’d be like “Oh, you know…”

Right. So we’re doing Olympic-level cognition, and it’s like “Here’s a coffee and a doughnut. Go! What, feeling burnout? No, you’ll be fine. We’ve just got to make it through this next sprint.” You don’t want to talk about it…

Right. And you don’t want to talk about “Oh, I’m feeling stressed”, because that’s you as a professional athlete saying, “Yeah, I’m not sure about my ankle.” Like “Oh yeah, we’re not sure about your contract then… Good luck selling cars.” I was a hero last week, and this week I literally have no job… This is I think, in people’s minds, and I think it’s in their minds for good reason. Because saying “Oh, don’t worry, the industry will take care of you.” No, the industry will fire you in a heartbeat. Just because a bunch of investors said “We have to let go of 7%.” “Why 7%?” “Because everyone’s doing 7%. Because 7%.” [unintelligible 01:23:34.28] It’s what plants crave.

[01:23:42.04] And you’re like “No, it can’t be a documentary from the future”, but I’m afraid it is. So yeah, don’t tell your boss about you’re not feeling good, because it’s too risky. This is what I think is on a lot of people’s minds. And I can’t tell them “That’s not true. Don’t worry”, because I think circumstances have shown that maybe isn’t necessarily true.

So what do we need to do? We need to find mutual support. You have to have peers that you can communicate these things to, and we have to build a vocabulary around it in order to, first of all, not tell the suits what’s going on… Because they’re gonna be like all freaked out. Like, “You’re trying to tell me my star player can’t play?” Like, “No, no, don’t worry. Don’t worry.” Like, they’re worried, because they don’t even know, is this a soccer ball? A football? Like, “Well, actually, that’s the same thing, sir, in this country.”

So this is a fundamental dichotomy between the creators, many of us who – we like to create. We’re going to create. We want to be of use. That’s our purpose for being. And yeah, we need to thrive and survive, but we’re not doing it for the sole purpose of exploitation. We’re doing it because we get satisfaction out of improving the human conditions. And we’re human, so we can be improved along the way, right? We’re not just a resource to be exploited… Just like “The brain machine, it’s [unintelligible 01:25:15.02] Oh, I’ll get some more brains.”

How many times have you heard literally something that is the equivalent of that in management meetings? I’ve heard that a lot over the course of my career, and I don’t generally try to single it out, because that’s not very effective. But it is a thing that – I mean, anyone who’s feeling extreme burnout, definitely do seek help outside of your workplace. There are people that you can talk to about mental well being. And we as a technology profession need to be able to talk about this in a way that doesn’t threaten our employment. So that’s my hot take.

I’ve been through times in the past where I had all those feelings. And I don’t tell people, usually… I’m telling everyone in the world on this podcast, because I think it’s important that we talk about it… And it’s been a long time since I had that feeling. Because I learned to recognize the signs. Because I did seek some professional assistance to figure out what was it that I – what was wrong with me, and what could I do about it to be healthier and happier and better for it? So I’m a resource, reach out to me privately if you need to, fellow human. I care.

So that’s what keeps me doing it… Just because I’m an idealist, and I think “Alright, in the end this is going to be better than all the other alternatives”, which is closeness, which is, you know, how much I can get just for me… And maybe sugarcoat it with some philanthropy. But when the act itself is a form of philanthropy, then it’s a sustainable way to live. And ultimately, what is the technology for? I think we were talking about this the last time we were in Portland, at OSCON, actually.

Yeah. It was “The purpose of technology is to improve the human condition.”

So that’s what keeps me going.

Break: [01:27:30.05]

Well, that hasn’t happened yet.

I saw that episode, and I was like “This is crazy. Who is this guy? This guy looks just like me.” But…

Well, this is the reason why I’m making this call. I’m using all of the battery energy that I’ve saved for several years in order to make this transmission, to send you a warning from the future. You see, I am the last Go programmer alive in 2053.

Whaat?! No, don’t say that…

And it’s terrible. All I do is maintenance programming. I haven’t added a new feature in over 20 years.

Alright, director’s commentary. So Matt sends me a message, “Hey, do you want to come on Go Time today?” Or it was tomorrow maybe. I don’t know. It’s like your typical “Oh man, we’re out of guests.”

Like, “Geez, who could I think of who’s like always available?”, you know… [laughter] And the idea originally was “What if we were the product managers of Go in the future?” Kind of a meh idea; not that great. I mean, it was an idea… Well, so I’m like “Alright, hmm… Alright, I’m gonna go over to the studio.” I have a collaborative workplace called [unintelligible 01:29:29.29] which is where the local creative technology community get together. It’s not a co-working, it’s more like a collaborative space. Really amazing spot. A lot of cool things happening. So we have a studio there that’s set up for music recording, for streaming… All my [unintelligible 01:29:52.08]

So I’m driving over and all of a sudden it hits me. I’m like “Oh, I know what I need to do.” It was just – you know, I don’t spend a lot of time alone. When you leave me alone for a few minutes, it’s really dangerous. I start thinking. By the time I get to my destination, who knows what’s coming on? So I call my collaborators over at the studio, I’m like “Look, I’m doing this thing… It’s a streaming from the future. I need some lasers, and… Do you have any tinfoil?”

Now, you have to understand, we’ve collaborated a lot together… And [unintelligible 01:30:32.18] streaming, he’s a brilliant guy. English/Spanish. He totally gets it. He’s like “Alright, no problem. I’m coming in hot”, because we’ve got to do this show. So I get there, and they got the lasers set up, and the smoke machine, just because lasers and smoke machine, future - d’oh… So I tell Mat, “Look, new plan.” [laughter] “I’m gonna call in from the future, and you’re gonna ask me some questions. And that’s it.”

Now, Mat is the straight man in the comedy act; he’s always interesting… He gets it. So it just – it started going. And I had some ideas that I thought about on the way over, just because it was not – it was very comedic, but I also had some very serious things to say. And if you kind of parse it and listen to it with that eye, it’s a cautionary tale, and it’s a genuine, heartfelt outreach to a lot of different communities about some things that I think were going on with Go in the world at the time.

[01:32:02.08] But my idols - you know, Robin Williams, or Eddie Murphy, people who were… I mean, I’m no Robin Williams. I’d like to be. Because more lucid human being, more present, more quick-witted… It’d be hard to find another human being with that type of rapidity of thought. So these were my – somewhere between that and the old Jewish comedians… “Take my computer, please”, you know… [laughs] And definite hat tip to Back to the Future, and some of these other tropes that are formed us.

These are the things that made us who we are, because we were them in part, and they were us. And Matt was amazing, Natalie - they were amazing. It was a great moment of inspiration, and I really appreciated that everybody could go with so little information about what I was going to do, and that it came out so fantastically. I really am very grateful to all of the sources from the past and the future that I stole from, and all my collaborators that put it together… It keeps getting views. Look, until 2053, that thing is still – like “Let’s see…”

“We’ve still got two more years before NostraRonmus is wrong”, you know? [laughs]

Well, I will – when is this show coming out? This show is coming out sometime in the future…

So if I were you, humans of the internets, I would go to Chicago in July to the GopherCon US, and I would make sure – well, first of all, go there for the community day before the whole thing starts, for the hardware hack session. That is always amazing. We’ll have drones, hardware… All sorts of cool stuff.

That’s during the community day. That’s before – it’s totally free, by the way, to go to the hardware hack session. You don’t have to pay extra. You just have to have a ticket. We’re not even checking your tickets, actually. You know.

Maybe somebody is. So do get the conference ticket. But definitely be there day one of the conference, because there may be, there may be a chance that something from the future may appear in the present. Well, that’s still in the future.

It will be the present when the future comes, then.

Yes.

Well, the day before the conference, come to my hack session.

The day of the conference, make sure you’re there for the opening talk.

The official announcement hasn’t come out yet, so I may well have just scooped…

But yes, it’s going to be outrageous.

[01:35:50.07] Like many of the things I do, it will be a spectacle. Whether it’s the spectacle I intend or some other spectacle is not important. I promise a spectacle, and spectacle I will deliver. [laughter[

No. want to check that out though.

I haven’t. I don’t usually use that word, actually…

I’m in California, I usually say awesome, just because like everything’s awesome.

But this is one that – it’s the 10-year of GopherCon, so something special has to happen… And - well, I will do my best.

I miss you guys.

The real world… I mean, the internet are all well and good, but I haven’t left for another planet yet. I’m still here. Not as often as I was, but I’ll definitely be – I’ll be at GopherCon, I’ll probably be at some other stuff this year… I’m going to try to make more of an effort. I do a lot of the European conferences. I live in Spain, so it’s very quick and easy, inside the European Union.

Oh, more than that. Actually, this was my seventh year in a row giving a talk at FOSDEM…

Which is kind of amazing, just because, you know –

It is February. It takes place at the campus of the University of [unintelligible 01:38:34.01] in Brussels. It’s kind of an anarchist conference, by which I mean there’s no registration. You just show up. So the organizers, the way they organize it is each room of the campus - you pitch. They take pitches for subject areas. Like, there’s a Go dev room, there’s a Rust dev room… And once they choose the subject areas, each one of those sub-organizers is 100% responsible for choosing the speakers, organizing them, making sure they do their thing… It’s 100% on them. The campus - they have streaming A/V. They just provide that, running throughout the day, from volunteers. There’s no corporate sponsors… It’s like a social anarchist conference, and it’s really quite amazing.

A lot of people who are maintainers just show up there and hang out. The hallway track is incredible. I’ve never even made it in the Rust room, but I’ve had the most amazing conversations with people waiting to try to get in. So I highly recommend FOSDEM. Also, the night before it begins – it takes place over the weekend, Saturday and Sunday. Friday night, traditionally they have an opening party at the Delirium Brewery, which is a classic Belgian trappist brewery, famous for the Delirium Tremens ale. So there’s people I would only see at that beer event. Like Charles Nutter.

Maintainer of JRuby.

An amazing guy, super-smart. Didn’t expect that JRuby would be so successful and would take over his entire life and career… And since I’m not too involved in Ruby, the only time we would bump into each other is at the beer event the night before FOSDEM. And a great chance to catch up on things, just because he’s a great guy. Our paths just don’t cross because of, you know, life. So yeah, please come to FOSDEM.

Mr. Mush - yeah, thank you. Thank you, Mr. Musk, for my bandwidth. Please don’t cut it off again after those last things I said. [laughter] I mean, I meant them, but please don’t listen.

You’ll notice I love those pre-parties before the conference kicks off. It’s almost guaranteed, if there’s a conference and there’s a pre-party, you’ll find me there.

R2.

That was the first GopherCon. Yeah, that was actually pretty amazing… I had a bunch of hardware, not just because I had just given this talk, but because I was actually going to Berlin for another conference right from there, and to do a workshop. So I had all these flight cases full of robots from Sphero, and drones, all this different stuff… And we had a day in between of travel, and it was just – there was this room for the community activities, which was like nothing planned. There was nothing planned, it was just a bunch of people hanging out. So –

So I was just like opening my flight cases, let people play with my toys… And the next year was like “Yeah, so you’re coming for the community day, for the hardware hacking?” And it’s like “Oh, is that a thing now? Because yes…” [laughter] The answer was yes. I mean, you don’t even have to – you had me at hardware hack. [laughter]

Well, thanks. Thanks for having me. I really appreciate all of the great guests that you have, all the interesting things… I learned a lot from listening, and it’s really fun to – it’s fun to chat with you, and fun to share, and I really appreciate the work that you’re doing, and thanks for having me on.

Our transcripts are open source on GitHub. Improvements are welcome. 💚