大便黑色的是什么原因

Transcript

Well, it's great to have you. Thank you for being here. Thanks for me to be here. I've heard that your first startup was written in small talk. Please explain. I don't know what there is to explain. It's the best programming language. Well, I had I had worked on Lisp and Lisp dialects and before that and actually I worked on list web frameworks. And when we went to build our first startup, we first wrote it in, we first implemented in Rails. And then I found compared to lists that development process kind of frustrating. And I mean we don't get the full details, but I thought that continuation based web frameworks were really the right way to implement. Of applications, there were no continuations in. There's no continuation based framework in in Ruby and it's kind of searching around, I found that there was a good one that had just been written in small talk. And so I decided to play with it a little bit. And then I found that small talk is actually this extremely interesting development environment that had a lot of the aspects of Lisp that I'd really appreciated there like, you know, and a fully interactive environment with a proper debugger so that you can you can edit the code while. You know, in the middle of some web request or you know, deep in some stack trace or something. And you know, you could, for example, encounter an error with some web request, edit the code to fix the error and then resume higher up in the stack such that the entire web request would just complete. And so rather than this kind of annoying feedback loop of having to add some log statements and like do this binary search, like find the problem and eventually like deploy a fixed version, you know, process that could take an hour, you could just like. Literally inspect the stack frame, see which variable has the wrong value, fix it like, you know, jump back up, hit proceed and have the whole thing works. Anyway, the point is, in the hunt for this continuation based web framework, realized that small talk in general had just a much more powerful development environment as compared to Ruby, as compared to basically every other mainstream programming language. And so we decided to yeah, use it for the company, which in hindsight was. I mean, I don't know if it's a terrible decision or not. The reason I think one would think it would be terrible is that it would be, you know, hard to hire people and hard to scale and you know, whatever. It wasn't hard to hire people, or rather nobody knew it, but it was easy to teach them the company they know before they joined. No, no, but they learned really quickly. And then you have smart people learn languages really quickly. So I don't think that's really a reason not to use a non mainstream language. The company didn't work, I think for unrelated reasons. I think just the idea wasn't that strong. But we also choose Ruby first for Stripes. So I don't know, I think maybe the gains. Not quite as large as I poked.