 So so Winston cover my introduction So so I'll jump into Oh it's not sure Command Command Command F1 Ah okay Ya so basically I'm trying to start this segment where I just create open source issues that I see mainly on rails and some other places then I will share them during Ruby Meetup so maybe people can work on them So my main driving force is actually rails has a lot of issues but there's not enough people working on them so what part of my motivation is I'm trying to inspire more people to work on them Ya so recently on rails so now rails is on developing for rails 5 your action controller parameters is not a hash within different access anymore they change it to something I can't remember what but basically so this is an open issue if you do a comparison between the parameters and the hash it doesn't work so I think it's pretty simple you can just good for beginners basically implementing a method and just writing a test for it so I'll post these slides up later so you can get the link to the issue Ah ya okay so this if you use current page and if your URL has a trailing slash on it your current page will actually not match will actually return false so the method is broken I actually submitted a PR but then there are some issues with how to test it so if anyone wants to take a step at it feel free to do so I basically ran out of ideas so basically someone in your middleware is actually removing the trailing slash from your URL so I have no idea how to test that but I can fix the thing but I don't know how to test it something like that ya so DHH2 has a list on the issues page so there's a ton of them and I think you should look at them if you want to get in touch with DHH you get a talk to him over on GitHub then make sure you're happy so this part is sort of like a self plug for me elections are coming so please raise your hand so basically ya I've been working on Rubybench for quite a while and I really don't have time to work on some issues that I really want to work on so to inspire more people to work on Rubybench so basically in Rails 4.2 actually in 4.1 onwards your scope is actually 3 times slower 3 times slower in 4.2 about 1.5 times slower in 4.1 so yes it's slow so in order to identify I was able to identify these regressions because Rubybench helped me to do so so I'm trying to inspire more people to help me with Rubybench then so we reported this and then one of the core team members in Rails worked on it and then your scopes are 15% faster but they are still somewhat a lot slower than what it was in 4.0 ya so just more inspirational pictures there was a regression with some query that you do you can see the dip and then there was an increase so when I saw the dip I went to look at the commit that caused the dip end up it was my own commit and then I had to revert my own commit so basically I caused the regression and then I fixed the regression ya so this was the thing I was talking about your scope across the Rails version from 4.0 to 4.1 in Rails 3.0 something is actually a lot faster as well ya so that's the end of my presentation pretty short so let me know if this useful like if you guys would like to know some open source issues that someone can curate for you and interesting thing is that if you go to the Rails issues right now I would say about 90% are all active record based so if you'd like to dive into active record just go into the issues page about 90% so that would be interesting ya so that's all for my presentation oh if you'd like to work on Rubybench or find out ways you can help just feel free to reach out to me on Twitter I'll be more than happy to get more get more help with it okay ya that's all Any questions for Oben Sasa? ah ya yes we have a legacy Rails application that we are running on the more Ruby cluster till day 20 so then it's like Rails 2? ya what is it? wow not that Ruby but Ruby 1.7 right now Ruby 1.7 2.7 okay not that Ruby okay so do you recommend to keep Ruby itself or do you recommend JNB? I have no idea because what do you recommend? aha JNB and Ruby Legacy I wouldn't know is it a business decision? ya I think the question is they have a legacy app that's running on Ruby 1.8.7 with Rails 1.9 something so is it better to stay on Ruby or JNB I think we have to look at the application in context and sort of you know I can quickly answer that firstly you have to you have to see wether you have your current JNB what the dependency are because like I have a product with development of series the dependency was on communication with flags and we had the same I had the same problem of whether to go up from go up a version or not and it's now at stay at 1.9 I couldn't go up to 2.0 because it doesn't work it doesn't work it doesn't work so the way to go is to is to go I would say forget about the rule that's my thing test each of the version of the JNB app along the way it is very effective let me add another point that you write to as government tax yeah but that one is date it's not offered anymore but I think the fact that your app is independent in that stage it's difficult to upgrade especially if you don't have a test because our model license so we use needle jam to pass us needle jam which consumes the model so there is a middle way so migration is not that easy just as it died so you write no usually people don't know the power but 30 is the one and one of approximately 1.5 billion emplosif as well and that implementation is the problem okay so the thing is because in terms of Ruby 1.8.7 is not supported some of these versions are not supported already so the fact that I still want it is dangerous even for Rails 1.9.7 is not recommended so in order to move away from all these you probably do a lot of rewrite internally to make sure that you stop using some of the old legacy way of using active record or Rails or whatever so to give some context even GitHub they were started on Rails 2.0 they cannot move to trade even Rails 3.0 even though they are like a company so big but they cannot move to Rails 3.0 Rails 2.0 before they slowly do the upgrade etc so it's going to be a can't move can't move okay what do you think shall I choose? I don't think that's even a question yeah it's not about that I don't think it will help you just maintain it maintain it so GitHub is very gigantic by the way 10 years ago that's been growing until now if it's still money okay so maybe i should compare but actually it's the keep the fall everything else right? yeah okay maybe actually i think it's audience amount okay sorry