Objective Reasons to Use Python or Ruby for the New REST Web Interface

So this thread is definitely NOT a thread for why Python is better than Ruby or vice versa. Instead, this thread is intended to be objectively criticized as to why you chose one over the other to write a RESTful web interface that will be used by many different clients (mobile, web browsers, tablets, etc.).

Again, don't compare Ruby on Rails and Django. This is not a web application dependent on high-level frameworks like RoR or Django. I just wanted to hear why someone could choose one by one to write a RESTful web API that they were supposed to start tomorrow completely from scratch, and the reasons why they could go from one to another.

For me, the syntax and language functions are completely redundant. Both offer many opportunities and, of course, both can achieve the same goals. I think that if someone flips a coin, this is a good enough reason to use one over the other. I just wanted to see some of you web service professionals who are very passionate about their work react to why they will use one on top of the other in a very objective format.

+6
python rest ruby api web-services
source share
7 answers

I know Ruby, I don’t know python ... you can see which path I am heading for, right?

+5
source share

I would say that the important thing is that no matter which one you choose, make sure that your choice does not flow through your REST API. This should not matter to the client of your API that you have selected.

+5
source share

Choose the one with which you are most familiar, and most likely do everything with the fastest.

+4
source share

Yes, flip a coin. The truth is that you will find a minimalist framework in any language. Heroku is a pretty good reason to say Ruby, but there may be other similar hosts for Python. But Heroku makes it stupid to easily deploy your api in the cloud, be it Rails or some other Ruby project that uses Rack. WSGI does not give you this opportunity.

As with the actual implementation, I assume that you will find that they are both fully competent languages ​​and a joy for programming.

+4
source share

I think they are pretty evenly combined in functions. I prefer Python, but I have been using it for more than ten years, so I freely admit that the following follows a completely biased approach.

IMHO Python is more mature - there are more libraries for it (although Ruby can catch up), and libraries that I think are better developed. The process of language evolution is also more mature, since each proposed function is discussed publicly through the PPR until a decision is made to include them in the release. My impression is that the development of the Ruby language is much more ad-hoc.

Python is widely used in many fields besides web development - scientific computing, CGI rendering pipelines, distributed computing, GUI tools for Linux, etc. Ruby paid very little attention before Rails, so I get the impression that most Ruby work is focused on web development. This may not be a problem if that’s all you want to do with the language, but that means Python has a more diverse user base and a more diverse set of libraries.

Python is faster.

+2
source share

Ruby + Sinatra

Very easy to use with / as middleware for the rack - someone already mentioned the hero

+2
source share

Or do an excellent job, and you will get another way from learning something new. Why not spend a couple of days with them? See how far you can get with a simple subset of the problem, and then see how you feel. For bonus points, open here and answer your question!

+1
source share

All Articles