A little bit. It was more with the people — I forget the names; I’m getting old, and it’s been a long time. I worked with [unintelligible 00:03:06.25] Jeff Lang was involved in the early days of this. This was really [unintelligible 00:03:10.24] and this whole IronPython, or the dynamic language runtime for .NET, basically. [unintelligible 00:03:22.19] was the team lead at the time, and then there was Jim Deville involved, and a few more people.
I worked with IronRuby by writing a book for Manning which never got published, because Microsoft canceled the project before the book was finished, or at the same time that the book was finished, really.
[00:03:50.19] So then from there I also started a startup at that point, where I was gonna do real-time social media filtering. You can look at today — it would probably be the most similar to IFTTT, because you could set up some query parameters, and if a Twitter feed or a Facebook feed or whatever social media feed would raise an event that matches those created parameters, it would trigger yet another webhook or some other event that you could then react to.
To do so, I had to analyze the Twitter Firehose and so on, and Ruby didn’t get me far enough, so I started looking for something else and I found Scala. Scala at that time only had Lift as a web framework. People said it was very interesting, but from my point of view it was a web framework that conflated all kinds of responsibilities, and so I started looking for something that looked like Sinatra, because Sinatra was as concise as I could think of for developing web apps — or API’s.
There was a proof of concept at the time which had just been renamed to Scalatra, so I started contributing, and after a while I was one of the main contributors on that open source project. It was fairly successful, but Scala itself has problems. The language is good, but the community is very divided. If you work with it on a team it’s not very conducive, in my opinion, to have people with very different backgrounds come together and get up to speed very quickly, so I started looking at Go to find out — or I wanted to know if Go would actually deliver on that promise that you can have a team, you can get your team to expand fairly quickly, and people shouldn’t have to have weeks of ramp-up time just to learn how to leverage the language to their advantage. So far, it’s been delivering. So that got me here.
In the meantime, through Scalatra I got into Swagger, because we have to document the API’s. The company that invented Swagger hired me, so that’s how I got deeper and deeper into that entire Swagger and OpenAPI story. When I switched to Go there was nothing there, so I figured people in Go also write lots of API’s, so they should have a way to document them and use them, so that other people can generate clients for it in whatever language… So that’s how I got to write in Go Swagger.