I was interviewed by David Weekly recently on 2011-03-19. I copied the interview here in case David's website changes. It was an audio podcast with me and James Halliday.
David Weekly interviews James Halliday and Peter Krumins, the CEO and CTO (respectively) of the newly-established Browserling, a browser testing firm in which David made his first angel investment. (The interview was done a mere hour after closing the round!) James describes his drive down from Alaska to the Bay Area to pursue funding for his startup and Peter describes his childhood with computers and his meeting James on IRC.
Here's a pic we took on the investment day:
Here's the transcription of the interview:
David: Hey, everybody. It's the David Weekly. This is Sunday, March 6, 2011. I'm joined here by the founders of Browserling, a brand new company. Hey guys.
David: Yeah, so you're James and Peter.
David: So how did you guys meet?
Peter: So we are on this IRC network called Freenode. We are both really interested in programming. I'm on channels like C++ and Perl and Node.js, and James was on some of those channels as well. We met like two years ago on Perl channel. I was publishing blog posts on my blog, catonmat.net, about Perl.
David: So your blog is Cat On Mat?
David: Dot net?
David: Okay, so this was like about the same time as maybe some of the funny cat pictures were circulating or?
Peter: I don't really know how I came up with the name.
James: How long have those pictures been circulating? I think an awful long time. Anyhow.
Peter: Yeah, right. So I was doing blog posts about Perl and James noticed them, and he also did some art for them.
James: Yeah, just random projects and things. I've had all these projects for such a long time. I guess ... Well, Peter first got me sort of into blogging to begin with.
David: Uh huh. So you were a reader of his Cat On Mat blog?
James: Yeah, I had read a few of his things.
Peter: Yeah, so I was blogging since 2007.
Peter: And we met with James on IRC like in 2009.
David: Got it.
Peter: Or 2008 maybe.
David: What kind of things were you writing in your Cat On Mat blog?
Peter: Oh, so I write about all kinds of computing, like Perl programming, C programming, and sometimes system administration, like Linux shell tricks, and Perl one-liners.
James: And linear algebra stuff too.
Peter: Oh yeah. Linear algebra and MIT algorithms course.
David: Why did you start blogging?
Peter: Just to get popular on the Internet.
David: And then you're popular now.
Peter: Yes I am.
David: So success!
Peter: Yeah, success!
David: How did you make your blog popular?
Peter: Oh, so I would be submitting my stories anywhere that I can, like Reddit, to Hacker News, to all kinds of Linux forums and like posting the posts on Facebook and on Twitter and Plurk and all the other social networks. I would write a post and spend the next 30 minutes submitting it everywhere. Yeah.
David: Nice. Got it. And then how did you get introduced to computers?
Peter: I was about six.
Peter: And I went my mom's job. She's a journalist, and they had computers for journalism to make the newspapers, glue them together to send for printing. Sometimes people who worked on the computers allowed me to do some stuff like play games and play around.
David: How old were you?
David: Yeah, and then so you started playing around on these computers on journalist's downtime.
Peter: Right, it was like ... Yes. It was like Windows 3.0 at first and then Windows 3.1.
David: At what point did you start programming?
Peter: It was about 12 or 13. At first I actually didn't have a computer at home, so I was programming on paper.
David: Oh, wow.
Peter: So I would program on paper and then go to these faculties and then rewrite them in text editor and compile them and run them.
David: Wow. That's a lot of patience to do that.
Peter: Yeah. Well, it didn't go for too long. Maybe I wrote like 15 programs. Then I would just ... Later I got my own computer, so I could do programming on my own at home.
David: Cool. Cool. What about you James? When did you get started programming?
James: So about the same age, about six years old. I guess there's two big parts of what got me so interested in computing. I guess first of all, my mom was pretty big into computing early on. She had, during high school, this TRX-80 from Radio Shack. I didn't actually see that used at all ever, but we also had a 386 at home. This is like 1993 that we got that. I thought, "Wow this is really fun," 'cause there were all these silly DOS games, like Battle Chess for one.
David: Oh, yeah! That was so awesome. Pieces would slay each other.
James: Exactly, yeah.
David: It made chess exhilarating, yeah.
James: Yeah, and you tried to get the queen, for instance, to kill the bishop or something 'cause it's something you don't really see very often. It's like, "What was that again? Oh, that's awesome."
David: Right. Right.
James: So there was that. I was growing up in Portland, Oregon at the time and there's this awesome museum called, OMSI, the Oregon Museum of Science and Industry. So it was like 1994, and my family had one of those membership passes. We'd go like once a month or something, and there'd be new exhibits and everything, like dinosaurs and awesome mechanical stuff. But then like all the way upstairs on the third floor, there was all of these computers, all of these different types of computers too, which I even haven't seen in modern times really much. But all these different kinds of computers, like NeXT computers with like Unixes and Solaris and old Macs and Windows PCs which was then like when it's 3.1. And later they had Windows 95. Big improvement.
But all of these computers were connected to the Internet, and so they all had different types of web browsers, like Mosaic and Netscape, and I thought it was just really amazing that you could just ... If you could find it, just go to all of this crazy content and you didn't have to thumb through ... Well, I guess before then I was really big into kind of encyclopedias 'cause I really loved just browsing seemingly random facts and just sorts sort of ingesting data.
But then, once I'd used the Internet for the first time, I'm like, "Screw all this book crap. I want to" ...
David: The books are dead.
James: Exactly. You can't GREP a book I guess.
David: Right. Right.
James: So that got me really interested in computing. Later my mom got the Internet at home. This was like 1996 with AOL.
David: And where were you living then?
James: That was still in Portland. Went to Eastern Washington around 5th grade or so. I guess we also had some computer books like this HTML 3 book that I read cover to cover basically.
David: PS. You can write code in your browser.
Peter: I actually learned the whole Visual Basic. Visual Basic 5 and Visual Basic 6.
James: Yeah, I messed with Visual Basic 4 a bit when I was younger too, but then I learned-
David: The first time I was ever paid interesting money for a program was a Visual Basic program. I made $100 which later I worked out was like $2 an hour, but it was a lot of money in high school.
David: When did you guys graduate high school?
Peter: In 2004.
James: Yeah, it was 2006. Oh goodness, by the time I graduated high school I had written so much code and I knew so many languages. It was pretty ridiculous.
David: What was your first experience with the command line?
James: Well, like when I was six with DOS programs.
David: Right, right, right.
James: That was how you used a computer.
David: That's right.
James: It's like-
David: So it seems pretty natural.
James: It didn't phase me at all. That's how you get data into and out of a computer.
Peter: Yeah, same for me.
James: You just have to type it in.
David: Yeah. So do you see a generational difference between people who were first introduced to computers through a command line interface and those who for whom accessing the command line's a special program they need to invoke?
James: I really don't think so. I think it has more to do with basically how old you are because ... So like over winter break ... A few times, I've started to teach all of my ... So I've got two little brothers and a little sister in Alaska.
David: You might be related to some very smart people.
James: Yeah, I don't know.
David: What would you guys recommend for somebody who's interested in getting involved in computer programming, is familiar with computers but has never really tried programming themselves?
James: In fact, it's much easier nowadays because you've got these nice libraries like JQuery that abstract over all of the horrors that live in the DOM.
James: It used to be so much ... Oh, and there's like layer tags in Netscape 4 and ugh.
Peter: Yeah, well ...
James: I think it still continues to be a really important language, and I think that's only getting more so. But other languages are really fun too, like for beginners Python is pretty easy to just dive into and then Perl is also really easy to get into. You just read the Perl doc, Perl intro page, and you're ready to go.
David: Nice. So let's get back to the story of how you guys met. You guys started hanging out on the #Perl channel on freenode.
David: And then at what point did you start working on something together and then start making something that was serious together?
Peter: Yeah, so James had the first prototype last year in January. So it's January of 2010. So he wrote the first prototype of StackVM in Haskell, and he showed it to me. We actually had discussed doing a startup together before. He said, "Let's turn this StackVM into startup."
James: Oh, yeah. Oh goodness. I had all of these crazy harebrained ideas for how I would build a startup. I wanted to build this hackable computer type thing. And geez, what were some of my other projects? I wanted to build like sensor data. I guess I didn't have too many direct software ideas actually except for the StackVM thing. So yeah, over winter break I just built out the simplest possible thing that could work.
It was really just ... It was written in Pascal, but it was really silly. It was just AJAX calls and then you'd get an image back. It was just a really basic VNC decoder.
Peter: Right. So he showed me the project and I liked it, so I jumped in. But yeah, the Pascal was a problem 'cause it was doing the image encoding really slowly. I converted that to Node.js. So I wrote the Node PNG module for doing fast PNG encodings. Yeah, and then James got into Node.js as well. It's around March, April.
David: Got it.
James: Yeah, so I was still in school at the time.
David: Where were you going to school?
James: I was at the University of Alaska Fairbanks.
David: Got it.
James: Actually, also in January I started working on this underwater RV contest project. So I did this in 2008. It was loads of fun. That was down in San Diego. This ... But in 2010 it was gonna be in Hawaii in June, July.
James: Oh goodness, yes. We had a lot of problems, I guess, when I did this contest in 2008 'cause we had an EE guy, but he made it his senior project or something, but then ... So it was a little bit ambitious because of that. Then he didn't work, and then it's like, "Oh no. Okay. So we don't have any electronics." I was just sort of tagging along to do some programming work, do a little bit of mechanical stuff.
We had a good-sized team, like I don't know, five people or something. Well four then. But so I had to kind of pick up the hat of doing circuit boards and electronics.
James: I had about two weeks to get up to speed to build a working prototype for like a driver system for this whole setup.
David: High speed electrical engineering education. Go!
James: Yeah, pretty much. Well, so it's just digital logic, so that helped. And then it also helped that the instructor, a really awesome guy, Ryan Luller, CS professor, has this crazy harebrained scheme to make circuit boards just using household stuff, like you had out here with this balloon experiment. Just hydrochloric acid and you can just etch these copper-plated fiberglass boards in like an afternoon, couple hours.
James: You can just have a prototype really fast.
David: Cool. So take me back to how you were working with Peter to get StackVM out the door and make it into something real.
James: Okay, so yeah. I guess ... On freenode there's like the main channels. They're pretty on-topic. Then there's all of these fun side channels where it's a lot of just kind of seemingly random banter, but it's also a really good place to sort of just throw out ideas like, "Hey here's a link to this GitHub project I'm working on. It's kind of neat huh?"
So I think the collaboration with Peter started sort of that way where it's like, "Hey check out this neat GitHub project. I'm gonna turn this into a startup or something I guess." And then yeah, Peter just, like around March or something or April was it? Just started really adding all of this awesome stuff with Node.js.
Peter: Right, right. So it was ... Yeah, so at first I wrote this Node PNG stuff and then Node JPEG and Node GIF, so you could do animated GIF recordings of the virtual machines. And then I wrote Node Video for recording like C or OGG videos, video streams, from the virtual machines. Yeah, and then I improved the design.
And then James jumped in and wrote dnode.
James: Yeah, so I had a lag after midterms when I had a bit of free time. Well, I didn't really have a bit of free time. I was super busy that whole time, but I decided to make some time. I noticed that our routing stuff was getting kind of complicated so I wrote this crazy RPC system using some of the ideas that I'd gotten during a student job using this thing that Ruby has called DRb. I basically took some of those ideas that I thought were awesome and ignored all of the things that were really annoying and I hated. And like implementing my own thread pool because the requests were synchronous. That's bad news. I just made everything asynchronous.
And yeah, so we used that system, dnode, in all of our back-end communication, but then also I wrote an adapter to make that work on top of socket.io which is this abstraction layer for web sockets for fallbacks. So basically we can use the same interfaces between our back-end systems and with the client, and it just makes programming just so much more fun and just so much easier to get your head around.
David: Cool. So it sounds like you guys had started to develop this really productive collaboration where you're kind of piggy-backing on each other's work. You had this sense of momentum, that something was really being built.
David: This around summer last year or so?
Peter: Yeah, summer and like a bit of autumn as well.
James: Yeah, so-
David: And then what happened?
Peter: So then we decided to apply at Y-Combinator with the StackVM idea. So we sent the application ... Yeah, and-
James: Well, so I guess we had also decided that, "Hey let's just go to the Bay Area just because, whether or not we get accepted. We're doing this thing."
David: And when was that, that you decided to move to the Bay Area?
Peter: James moved in early October.
Peter: And I moved in late October.
David: Got it.
David: So you just drove down from Alaska?
James: Yeah, so-
David: And were like, "I'm gonna live here now."
James: Yeah, so I had this clunky old car. I guess when I first left Fairbanks ... It had this little bit of oil leak, and it got even worse if you just spilled a little bit of oil on the radiator 'cause it was just really hot. As I was driving out of Fairbanks, there's this really steep hill. It's the only hill pretty much the whole way even though there's a mountain range between. But going up this really steep hill. All of a sudden, I look back in my rear view mirror and there's like this cloud following me. Turns out I-
David: At the beginning of your trip from Alaska, you're pulling out of Fairbanks and there's a cloud of this plume behind you.
James: Yeah, coming out of my exhaust pipe.
David: That's no good.
James: So I looked at that. I slowed down. I stopped. I put my blinkers on, and I just kind of looked at it. And then I'm like, "You know what? Screw it. The car's still going forward. Let's just see." And it did. I guess it was just some oil that had spilled, so I filled ... I topped off the oil before I left. I'd spilled a little I guess.
David: Got it.
James: It made a huge-
David: Got it.
David: So driving down from Fairbanks. That's gotta be quite a journey. How long did it take you?
James: Well, so I left Fairbanks and stopped off at my parents' house in Kenai. That takes you a day, maybe like 12 hours or something. I mean it's a pretty long time. I stayed at my parents' house for about a month. Did Node Knockout actually down there which is this fun programming contest. Peter, myself, and one of my friends in Alaska in Fairbanks, Josh. So it was like-
David: So all three of you were competing in this contest remotely?
Peter: Yeah, so this is like Battle Chess [crosstalk 00:19:57].
James: Yeah, it was this web-based real-time chess game, and the cool thing is you could watch everybody else's chess games from the main page. You could click on one to see it in 3D-style.
James: So it was pretty much exactly like Battle Chess with the layout. You could like switch it between top view and then this sort of pseudo trapezoid-projected view.
David: Yeah, yeah, yeah, yeah.
James: Yeah, it was really fun.
James: But then after that, I drove down. I think I left September 30th, and I just slept in my car the whole way. The other thing about my car besides it having plumes behind it sometimes-
James: ... was that it didn't have ... It really needed shocks, but I really didn't have the money to get them replaced.
David: It gave you a real feeling for what was going on with the road.
James: Yeah. Goodness, yes. It wasn't actually that bad for Alaska roads, but as soon as you cross over, like right at the border between Alaska and the Yukon Territory, the roads are just insane. It's just really, really bumpy and there's like potholes everywhere and it's just gravelly. Actually, the gravel parts are the good parts because the paved parts not as good.
I drove down all the way. It took me about four days driving from Kenai, where my parents are, down to ... I've some Godparents in Everette, Washington. So stayed there for a night. Then went down to my grandparents' house in Kelso, Washington. Stayed there for like ... I might have been there for maybe like four or five days, but so ... My grandpa actually helped me get my car into a bit more operable condition.
Because so I thought it would be really awesome to just jet over to Vancouver in Canada. I was headed down the Alaska Highway, and it was like in Dawson Creek and whatever, and like, "Yeah, that seems reasonable."
James: It's not reasonable at all.
James: The road between like Whistler and ... I forget the name of the town. It was like Luluette or something. Is just the windiest most ridiculous road I've ever been on. It's got wooden bridges and they're one lane, and so you have to wait for other cars to pass, not that there were many cars because no sane motorist would take this road. And like speed limits in some places were like 20 kilometers an hour because the turns were just that severe. Going up, going down a hill was just ridiculous.
By the time that I got to Whistler, I noticed, "Hey" ... Well, I noticed this more as I was in the mountains, but, "Hey, my transmission really doesn't work as good as it used to." It became ... All of a sudden, it was an automatic, really hard to shift this thing.
David: Uh oh.
James: It made driving hard and unsafe.
David: But you made it safely.
James: But I did make it down. I took Highway 101 after Washington, and it was really nice.
Peter: I was following all these adventures in IRC. James would jump on some-
James: I would hop on at a coffee shop or whatever, when I get network and be like, "Hey, I'm in Astoria," or, "I'm in," wherever, you know?
David: Nice. So you made it down to the Bay Area ultimately like at the beginning of October?
James: Yeah, October, yeah, 3rd or some such. Actually one thing I should add ... My car, it was really hot. So the whole trip was really cold. There was actually some snow up in Canada for a bit, but as soon as I turned ... As soon as the highway turned inland, it got really hot, and my car didn't like that.
David: Uh oh.
James: By the time I got to Santa Rosa I had to just ... Well, there was really heavy traffic for the first time also in the whole trip, except for Vancouver I guess. But my whole car started smoking out of the blue, so I had to beeline it for an exit.
David: Oh my God.
James: Just had to wait for the thing to cool off because ...
David: Are you still driving this car or?
James: Yeah. No, no, no, no. It got towed away actually 'cause I couldn't move it.
David: Got it. So you made it down here. You got a place in Berkeley where you're living now.
James: Yeah, North Oakland.
David: Yeah, North Oakland.
James: Just 'cause ... Well, Peteris had a friend.
Peter: Yeah, so I had a friend called David, and I told him that James is moving down from Alaska. Do you know any place to stay? I didn't know he was in Oakland. I just knew he was somewhere in the Bay Area, so I told him, "Can you help me out and find a place for James?" And so he contacted the landlady and she had a room in the same apartment house where he lives. Yeah, and it turned out to be Oakland.
James: Yeah, so that's where I just set down.
David: Got it.
James: 'Cause I really wasn't in a position to be moving around too much with that car.
James: Yeah, just landing.
David: Yeah. Cool, so then you've got a place now. You're in the Bay Area, and you start coding full-time and Peter comes and joins you a few weeks later.
David: So the two of you are hacking out in this ... What is it? One bedroom? Two bedroom?
James: Yeah, just a one bedroom even. It's-
David: You guys gotta be ... Was that the first time you had actually met in person?
Peter: Right. Yes.
David: Oh my goodness.
Peter: Well, he sounded like a good guy in our IRC conversations.
James: And some Skype. So we put together some of these videos for StackVM too [crosstalk 00:26:14].
Peter: Oh, yeah. Right. We also did some videos. Yeah, like the demo video for ... Yeah, like [crosstalk 00:26:18].
James: Goodness. So putting together videos remotely is so hard.
Peter: It took us like 16 hours to put the video together.
David: Oh my goodness.
David: So you guys have been living together since the end of October in North Oakland working full-time on StackVM and then also browserling?
James: Yeah, so I just found a couch, really nice couch, and Peteris has been sleeping on it.
Peter: Yeah, I'm sleeping on the couch.
David: Is it a comfortable couch?
Peter: No, it's not.
James: We got an air mattress too, but yeah.
Peter: I don't like the air mattress.
David: Has he been sleeping on an uncomfortable couch for like five months?
David: Have you thought about getting a bed or?
Peter: Well now that we've got funding, it's definitely a possibility.
David: So you guys started ... You had done some interesting work on StackVM, and at what point did the idea of browserling enter into the picture?
Peter: Started it October, mid-October actually.
Peter: So we submitted the application for Y-Combinator and they mentioned that we are doing browserling, but we didn't really have a prototype or anything working for the browserling.
James: Yeah, so I guess-
David: And you didn't get into Y-Combinator.
James: No. Well, we were sort of in the middle of a pivot. I mean that's like the worst time to have [crosstalk 00:27:41].
David: Did they give you any feedback?
David: Okay, so they're just like, "No."
Peter: They don't give feedback.
David: Got it. So they were just like, "No, sorry." And you guys were like, "Okay, well we're gonna do this thing anyhow."
James: Yeah. Well, so I guess the idea for it ... I'd had a kind of vague idea about ... Something like this might be useful at some point. I didn't really know what it was gonna look like though. But I thought more that it was just something that you could do with StackVM. It wasn't really a product in itself in my mind, but then ... So I went to this meetup in Berkeley, this Hackers/Founders meetup. Pretty cool. Just a bunch of random like business and hacker types just all in the same place and just talking about stuff. And I was just showing some people.
And so we'd been posting to Hacker News and Reddit. So some people that I met there had actually heard of us before which I thought was amazing.
David: So cool.
David: "Oh, people know me!"
David: That's got to be a great moment.
James: Uh huh. Yeah, a lot of the people that ... We got a lot of feedback when we did these Hacker News posts. Also, just meeting people in person, it sounded like there was this really hard problem that made perfect sense that everybody has if they're a web developer. It's that, "Hey, you really don't want to have to care about running all of these browsers yourself. You just want to be able to sweep that under the rug."
David: "I bought a Mac and I need to test with IE6. Help."
Peter: Right, yeah.
James: That should be somebody else's problem. I mean it's-
David: And you're the "somebody else" whose problem it is.
James: "Hey, well there's somebody else." Yeah.
David: Very, very cool. Sweet. So then it became clear at that point that there was a real business to be had in doing in-browser testing.
James: Yeah, so I took like $10 or whatever. I didn't have much money left, but I just spent like 20 minutes coming up with names, and landed on browserling. And it's like, "Whatever. I just need a domain for this," because then we're sort of-
David: Then you're launched.
James: Yeah, so we actually launched that really fast.
Peter: Yeah, so-
James: It was surprising how fast we launched that thing.
James: Yeah, I think I started ... I like get git init'd on the October 18th or something for browserling.
Peter: Yeah, and then we launched on November 24th.
James: And did a Hacker's News post. We had this queue thing also which got to be insanely long, like 100 people or something.
David: So you had 100 people who were waiting to start using the product, who were just sitting in front of their browsers twiddling their thumbs.
James: Yeah. We actually had five servers, queued up five desktops with the browsers loaded that you could use for that, but because of a bug in our routing software, I think we were only using one. But that was ... Yeah. Yeah.
David: Cool, so-
James: It's been fixed, but ...
David: Got it. Got it. So then use of your product is continuing to increase. Today, you actually closed your first round of funding.
James: Yeah, thanks for that.
Peter: Right, yeah.
David: Super cool. So what was that like for you guys to try and negotiate the waters of getting other people's money for the first time?
Peter: Yeah, so we have been going to these Hackers/Founders meetups, and we met Jonathan Nelson who is organizing the event. He started introducing us around to other people with a note that we are looking for funding. Yeah, so we met Adam Rifkin also at Hackers/Founders. And then Adam introduced us to you.
Peter: Right. Yeah, that's how we met you.
James: Yeah, of course there were all of these other weeds that-
David: Yeah. Yeah.
James: Oh goodness. So I guess it was a really big shift going from just hacking and doing nothing else pretty much to going out and meeting people and felt like it really sucks your energy-
David: It does.
James: ... to have to wake up ... Well, I guess this is more ... To have to wake up at a semi-regular schedule like normal people. I don't really do that, so it was especially harrowing.
David: What kind of hours do you normally keep?
James: Yeah, I don't even know. They drift and I don't try to fight it 'cause when I try to fight it, I just feel sleepy all day, and yeah.
David: Do you find your days are like 30 hours long then, or like-
James: They're not that long. They're over 24. Maybe 26ish.
James: Yeah. But they drift a lot. It's not like there's any pattern to it.
David: So you just basically ... You go to sleep when you feel tired. You wake up when you're ready to wake up. You work when you work.
David: And you just kind of just roll with it.
James: Yeah, well I think with programming, especially the crazy kinds of programming that we've been doing, you really have to be in the right mindset for that. You really have to have a good motivational drive and it's-
David: Could you explain to a non-programmer why the kind of programming that you're doing is so crazy.
James: Well, so I guess with browserling, we've ... This is sort of a continuation of some of the design choices that we've been doing previously, but like to an even greater degree. But basically how we structure our coding at browserling is we have our core codebase and we ... Every chance that we can get to abstract out some big chunk to make the core nicer, we take that. For instance, I've got like 90 projects on my GitHub right now. And-
Peter: Yeah, I have like 83.
James: Yeah, and I've got like-
David: You've divided up the project into lots of these little sub-projects.
Peter: All of them are already usable.
James: Yeah, so other people can use these things. It's like dnode, our RPC system, is on NPM, the Node package manager, and all of these little projects that other people can use. I think it's really great because, you know, not only are you contributing to the community, which is great, but of course we're running a business. What do we care about altruism? I guess the really bottom line kind of way to think about this is all of the complexity that you can take out of your project and host just completely outside of it is code that you don't have to think about anymore. You can just focus on the parts that are very unique and specific to your application.
Peter: Yeah. Yeah.
James: It makes the motivational picture so much different. So one-
Peter: Yeah, so each time you create a new project, like a new submodule, it's like a new project and you are very enthusiastic about it and just start coding it from start to finish 'cause it's not that large.
James: Yeah, the scope is really limited and manageable, and you get these sorts of iterative feedback right away when you're just taking a small piece of it out. That's what people say a lot when they say, "Oh, modular programming. That's great. How's that any different?" But I mean, when you actually take that piece out of your codebase altogether, like not even in a lib folder or something, it's different because ... Especially if you throw it up on GitHub, and especially if you throw it up on a package manager like NPM.
Peter: Yes, then you have good documentation for it and good tests.
James: Yeah, and there's like this latent implicit social pressure to make it good, to make it reusable, and to not increase the scope beyond what it should do. And I think that's really powerful too.
David: Interesting. How do you decide what to publish out there on GitHub and what to keep as proprietary?
Peter: So we did StackVM. StackVM was originally all opensource, but it's really hard for the users to install 'cause there are all kinds of tricks you have to do.
David: 100 packages for the [crosstalk 00:35:45].
Peter: Right, yeah. [crosstalk 00:35:47] packages and then all kinds of siblings between the libraries.
James: Yeah, and just the setup for this. I don't even know that that problem is going to go away because it's just such an intrinsically hard problem to configure some virtual environment and to get everything that you need to get running well on the servers that you happen to have. It's just really, really hard, and that's something that I think led us to conclude that, "Hey, we should be doing this for our users," with something like browserling.
David: Got it.
Peter: Yeah, but then browserling is closed source, so the core stuff like all the queuing system and the [crosstalk 00:36:27].
James: Yeah, all of our crazy back-end message passing and token passing system. That's all-
Peter: That's all closed sourced. But then we're using all these opensource modules that we wrote.
James: Yeah, and so we just spin them off when we think that they should be open because they're just this reusable piece. I mean, it's good for us, for our bottom line, as I mentioned, with our motivation. It's good for visibility in the community too. I mean this is a product for developers.
James: So it'd be awesome if they've heard of us one way or another.
David: What do you want to do with it? Where do you guys want to go with it? Imagine it's five years from now, not even like 6 months. Where's browserling? Where are you guys?
Peter: So we'll definitely keep building it, browserling, for a few years and then just see what happens. Maybe we have a acquisition offer that we can't just resist, or maybe we'll spin off some more projects based on top of StackVM because we have the StackVM technology. We have had a lot of ideas how we can use StackVM.
James: Yeah, well so I don't know about predicting too far out because I mean this problem seems like a really neglected important problem.
David: That's right.
James: As a result of that, there's so much stuff that people haven't done yet because nobody's even been thinking about it.
David: Got it. No, I mean that totally makes sense. I'm curious about your personal aspirations.
James: Oh, personal aspirations. Well I guess I'd like to get a bit more into robotics. I thought the stuff I did in Hawaii and down in San Diego was just amazingly fun, especially when I had to wear so many hats, etching the boards and designing them in Inkscape of all things 'cause we were using a laser printer to iron on the designs.
James: And doing that, doing mechanical stuff, doing ... So I really-
David: Just continuing to push yourself in lots of different [crosstalk 00:38:29].
James: Yeah, I really like pushing myself into stuff that I really don't know what I'm doing and I just kind of figure it out.
Peter: Well, I'm actually not sure. I haven't figured out. So with browserling and then ... I'm not really sure. Whatever falls, whatever I feel like doing.
David: Cool. Well, I'm really excited to see you guys working on an important problem that nobody else is doing a good job tackling. Just to see a pair of people from such different backgrounds and so passionate about technology and art and helping other people.
David: I'm really excited to have backed you guys.
David: Thanks so much for letting me participate.
David: Cool. All right. Well, thanks guys.
Peter: Yeah, thanks.