Los Angeles Ruby Conference 2013

Razones para utilizar JRuby en tus aplicaciones Ruby

Fiona Tay  · 

Transcripción

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

okay so next up is Fiona Tay she's a ruby and JavaScript developer for pivotal labs based out of San Francisco and she's going to be talking to us about why jruby oh wait no this works right you guys can hear me yeah all right so I'm really excited

to be here because I actually used to live in the Inland Empire so anyone else here from the Inland Empire yeah alright so the first thing I want to say about my talk is that originally on the schedule says why I like jruby and you should like it too but that's

not actually what my talk is about my talks actually about why is used a ruby sometimes and not other times all right so just for a quick introduction JRuby is an implementation of Ruby on top of the JVM so now you know what today ruby is and there will be

the day stands for java so in this presentation I'm going to be telling you why you should be using JRuby and this is from the perspective of somebody like me who just wants to make web apps I'm not going to tell you anything about compiler internals

hopefully you don't care about that and this is about the good the bad and the ugly just like that movie so a little about me I'm a rubios I've been doing Ruby for about three years and I also I mainly do rails yay rail so I'm also jay rubios

for the last six months I've been working on this product called open chorus it's an open source initiative it's basically a collaborative platform for data analysis think of it as google docs for data scientists and as far as i know we are one

of the biggest jewelry projects out there we have over 10,000 test that's a lot alright so now i'm going to tell you a little bit more about jruby so Jo is a ruby implementation so to switch your project over from Ruby to jruby it's basically step

one installed a ruby and step to write movie Cohen so here's a code sample if you're using our vm all right yeah so if you guys are using our vm to manage your rubies then it's as simple as typing rvm use and if you're not using our vm you

should consider using it our rbm to manage your rubies and it's a same as a normal movie so yeah they are interchangeable to an extent hopefully one plus one is the same under all Ruby implementations if you find that that's not true let me know and

i hope you report about so the most popular implementation is MRI otherwise known as matt's ruby implementation and it's basically the default Ruby so if you don't know what Ruby are using you're probably using MRI so I guess most of you are

using mi then the next most popular one is jruby which is what I'm talking about and then there are also a couple of other redheaded stepchildren no offense meant so another with how the hell this Ruby implementations work well you're right Ruby code

and it's interpreted by the interpreter yes not rocket science but in JRuby the implementation of the Imperator is written using the Java Virtual Machine and that's basically your secret sauce because a lot of the benefits of using jruby come from

how awesome this implementation is shout out to the JV team so as I said earlier these implementations should be interchangeable but that's not really true because some implementations are different and you could say that some implementation some more

equal than others so some of the important differences that occur even though one plus one equals two is speed of execution well how good is the implementation support for external libraries and implementation bugs sadly the Ruby spec is not really well laid

out and MRI is popularly known as a reference implementation so a history of jruby it's been around since 2002 which makes it kind of odd now it's actually newer then it's actually older than the latest 1.1 1.9 Ruby interpreter and it has had traction

[ ... ]

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