Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
all right I see family or faces so this is what it must feel like performing in like high school theater like having parents around so I've been giving a lot of talks this year and I didn't give any talk until this year and my most recent one was that
actually had to go go Rico where I made two like huge mistakes well it's my live demo so de Voort and it's actually worse than like totally not working because like you're almost there right the other one is my presentation crashed towards the
end so I actually have a fix for both of them so this time I there's no live demo so you guys don't have to worry or get nervous I'm certainly less nervous the other is I had the wrong operating system presentation to the combination I was using
a Mac but I had Microsoft PowerPoint which apparently is not a good combination so this time I'm on keynote but I'm on Yosemite so that might be an issue all right so a quick show of hands how many of you have heard of fluidy yeah cuz I cheat ago they
just gave away stickers so some of you just got stickers and if you want stickers they're more stickers here how many of you use for indie in like dev or production excellent like there are two people who are brave enough to admit so I'm gonna give
a quick overview of what flinty is today with the use cases and hopefully talk about internal architecture a little bit as well as like war we're sort of headed in the next year or so so Who am I I am Kyoto Tamara that's my that's how you can harass
me publicly and I work for this company called treasure data where I work as developer relations person and what that means is I get to come to a cool event like this and listen to other really smart people about open-source and I also happen to be a flying
the maintainer but staying true to my Japanese heritage and like I'm gonna start with a bit of self-deprecation except my self deprecation is actually just true so first of all nube I didn't know that it will be hat lambda like this morning lots talked
about static typing I like that as an idea but I think that would make it would be a little too hard for me to program it so we'll see the other thing is I'm a Flynn D new booty that's the contributor graph and the top six people and I'm not
the SEC and the natural question to ask at this point is why is it the sixth guy it was six person giving a talk and not the other five people who clearly did more work right well I asked them and they have like all these excuses thank you and actually the
guy to my right or left is my boss he's CEO because he's like a CTO he's actually busy young like me and I was like you know like San Diego sounds really cool I come from this like really expensive city with a lot of rain called San Francisco and
it's it's really nice to be here it's my first time and also the first Ruby car actually who's the first time I hear all right I feel less lonely now keep clapping so I didn't mean literally but that works too because then I have to talk
and you guys can just clap for the next 45 minutes right so what's flu indeed we tried you and this is like probably the most straightforward a way of describing it and I'm gonna try to unpack because this sounds like you know just like another distributed
software so it is first and foremost a data collection tool I give you have blogs or any kind of event data think think about flu Andy and when I say event collection or data collection usually like you have a system like this and you know there are a lot
of scripts some were written by people who are no longer with you some are like really brittle and this is not really anyone's fault because logging is not anyone's a priority and when you're shipping a version on one but eventually it becomes
really painful and Flenory tries to clearly I didn't practice this if flinty tries to solve this problem by unifying it and of course this is like a highly highly optimistic picture it takes actually months to get there but it does help you get here the
second point is it's extensible and there's this guy called Satoru Hoshi who wrote the first version of flew Indy and the core philosophy of flow Indy is that the core program should be reasonably small and should only do the most important things
that nobody wants to like deal with but important so the idea is like I'm gonna touch a bit more about each one but error handling message routing making sure that you use up all the CPUs that you have stuff like that and delegate the rest to the users
who actually have very specific use cases right like reading data from particular data sources and parsing some like gnarly custom formats buffering the data in the way that you really want it and you have control over that and write out data to where you
care because frankly like the logging software is pretty backyard without having a destination that you want to to use and care and deal with and finally formatting the data so I'll deal with those two so I want to think is the core concerns just about
[ ... ]
Nota: se han omitido las otras 2.448 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.