Kinsomicrote's Posts
Nairaland Forum › Kinsomicrote's Profile › Kinsomicrote's Posts
1 (of 1 pages)
Introduction: Good evening folks, trust your week has been superb. The Ruby community is an active one with tons of new stuffs being unleashed daily. Surprisingly, there is no Ruby community in this part of the world (Nigeria). The aim of this post is to see how a community, or preferably, a group of Ruby devotee can be created. Core Ideology The top aim of this group is to be actively involved in the development of (1) information technology in Nigeria as a country, Africa as a continent and (2) the Ruby Language which we would do dearly love. This is WHY this group exists. HOW To achieve our core ideology we would do the following: * Commit to open source projects; by participating in old projects and creating new ones where necessary. * Provide innovative solution(s) to problems we discover in our country and Africa at large. * Collaborate with other organization in actualizing our core ideology where necessary. * Ensure the development of every member of the team as its important in fulfilling our aim. The Team It promises to be fun. We have a serious task at hand; one that must not be taken lightly. To join, one must meet these requirements: * Ruby Devotee: you don't have to be a full stack ruby developer. You just have to love Ruby and MUST have started learning. * Student: No one knows it all. We are committed to ensuring everyone on the team upgrades continuously, thus you must be ever ready to learn. Its going to be rigorous! * Location: Preferred location is Lagos. Entry To come on board: * Send a mail to: lagosruby[at]gmail[dot]com with the title: Ruby Developer Group. * Suggest a name for the team * Tell us a little about yourself and why you are a great fit. All the best. |
I hope this does not start a Rails vs Sinatra battle Ok...I use Rails and am yet to use Sinatra, so my talk would be short and based on what I've read. Rails has a upper hand above Sinatra when we look at the community built round both frameworks. The Rails community and resources are both super active when compared to rails. Thus a beginner to Rails has tons of resources if he wants to venture into Rails. Sinatra is useful when building a light application but when scaling comes into view you surely would start having issues. Rails is robust is handling such issues. No wonder its used for Github, Basecamp and the likes. If you want to make a light application and you want it to be fast then Sinatra is good to go. The error messages in Sinatra is quiet descriptive. Personally, I'll choose Rails over Sinatra, no hating ![]() |
Brilliant idea! I think most of what Tresz said should be considered. There also needs to be a way to determine when power is no more available in a particular location that has been updated to have power. I believe searching for power would be inorder of 'closest location'; so someone in Surulere doesn't get updated of available power location in Badagry. For security purposes, users should be given the right to share their location. I do Ruby, else I would have signed up for this...nevertheless, I'll do well to follow closely. Kudos! |
leumas2009:Hello, still got projects? |
Is this thread dead? I do RoR |
stynhaq:Boom...this would be cool using scripting language. Good thing am on Ruby. Would give this a shot. Gracias ![]() |
What do you really need? |
Borwe:. Lulz....not true bro. |
It depends on what you intend to achieve or build. I played a little with C then PHP but never liked it. Now am settled with Ruby. |
Please, will it work for Nokia C2-03? |
Btw, brilliant idea you got there. |
1 (of 1 pages)
Ok...I use Rails and am yet to use Sinatra, so my talk would be short and based on what I've read. Rails has a upper hand above Sinatra when we look at the community built round both frameworks. The Rails community and resources are both super active when compared to rails. Thus a beginner to Rails has tons of resources if he wants to venture into Rails. Sinatra is useful when building a light application but when scaling comes into view you surely would start having issues. Rails is robust is handling such issues. No wonder its used for Github, Basecamp and the likes. If you want to make a light application and you want it to be fast then Sinatra is good to go. The error messages in Sinatra is quiet descriptive. Personally, I'll choose Rails over Sinatra, no hating