GopherCon 2014

De NodeJS a Go, razones para cambiar y buenas prácticas para hacerlo

Kelsey Falter  · 

Transcripción

Extracto de la transcripción automática del vídeo realizada por YouTube.

before we get started how many of you guys are from New York City yes ok but I happen to be the new york city co-leader of the go meet up so I just have to shout out um thanks for coming I'm calcium the CEO and founder of pop tip and I'm going to talk

a little bit about our experience with go and node and the learnings along the way so it's from one shiny object to the other before I start let me give you a little bit of background obviously I kohli the go meet up in New York City have an incredible

team but pop tip is a product that helps provide companies with a statistical breakdown of what the crowds public opinion is we help our customers understand public consensus and we do that by analyzing conversation from online our problems rain from handling

streaming data NLP machine learning topic modeling basically everything sexy that you hear that's what we do um and basically our customers range from CNN to ESPN to Spotify to L'Oreal so these guys are folks that really demand you know the highest

level of performance and I think that to kind of frame the discussion I used to write a little bit more code than I do today but now I let the let the other group members on our team do the heavy lifting so I have to give them credit y know Jas so when we

first started a little little under two years ago we chose note as our primary language not because it was the top post on hacker news but because of a few different things so you know I wrote JavaScript and I felt like I could take that transition into node

but a little bit more background from a speed of development standpoint you know we gave it an a for our specific situation it was a for a small codebase c- for a big codebase we're talking callback soup it thing we have seen it modern features we were

all real time and so having the ability to use web sockets super easily was incredible runtime speed all right cost of purchase was free so that was great and the cost to administer you know it was also pretty chief comparatively speaking to.net momentum a

so if you know JavaScript we had guys who could just quickly get up and running right away the talent pool you know you did have a few kids who were self-taught no chasers it wasn't you know it wasn't the Ruby community it wasn't the Python community

but we did get a lot of folks in there that were good people and we actually had someone on our team who has contributed to nodejs core so that was helpful active community i give it a be at the time honestly because it's super it was super active a little

a little under two years ago but not mature in any way shape or form the framework wars were just i mean i'm not even going to get into it but it's like we already have a framework there's no need but you know you neither here nor there so language

homogeneity you know j s all over it was kind of cool looking at github and just seeing like what percentage of your code base was JavaScript um large code base support not a lot of it you know there is I think that almost every single talk that was out at

the time was about how to get up and running with node and hello world was about the only thing that was out in terms of what you could do and yeah it's great that you can get a web server up and running but it wasn't super helpful from a large code

base standpoint but it was important for us from a you know NBP let's just get some prototype out there into the world from a coolness factor yes there's an A+ at the time evil empire j/s fanboys flocked and so i think from a recruiting standpoint

[ ... ]

Nota: se han omitido las otras 1.760 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.