101–110 of 248 posts
Earlier quoted context omitted.
I'm sure things have changed post-acquisition, but for a very long time Github's back-end languages were just Ruby and C.
Turns out C is better at some problems than Ruby after all? This was my point.
sad to see _why the lucky stiff left out, but I suppose it is what he'd have wanted.
Earlier quoted context omitted.
Except when you look at benchmarks it's actually not that much faster than rails. https://www.techempower.com/benchmarks/#section=data-r21&hw=...
I don't know how they measure it, but other measurements have shown different results: https://medium.com/@elviovicosa/phoenix-vs-rails-benchmark-2...
The big difference is the blog post you linked performs a very basic GET request to an endpoint. It mentions it doesn't hit the database or deal with caching. It's basically a non-realistic hello world that is good at isolating performance of a specific library but doesn't show how it fits into the grand scheme of things.
The other link performs multiple database queries as part of the request which goes back to the old saying that for a huge portion of web apps you're I/O bound (AKA waiting for something else such as the database).
I tried to like ruby and rails, but when I tried to grok the language, I found it more difficult to follow than python + js (my daily drivers). Did anyone else feel the same way? I kind of want to give it another chance bc I have some side projects that I want to try out, but I find django/python and next/react easier to grok. Maybe I should try harder? FWIW, I also want to pick up good practices when it comes to eng…
Honestly, if you only are familiar with Python, it’s gonna be pretty tough to learn anything else. I would recommend spending some time learning literally any other language (Ruby is fine). Otherwise, if you just know Python, I think it will hold you back. For example, ending an if statement with semicolon and then having the if block indented below is just not the normal way to do things. I’m not knocking Python, I…
Its not the minor syntax differences that I have trouble with, its that ruby does not "fit my brain like a glove."
I had a lot of fun watching this documentary. The one person framework really comes out in the personal story of Toby from Shopify. "From Hello World to IPO". What I also loved is that he mentioned that if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. Sure that can be true for many apps, but in a world of, for example, APIs and f…
>if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one I've never worked with Rails, but this sounds amazing. One of the things I really hate about the Node.js ecosystem is that there are no clear conventions, the structure is always different even when the same framework is used. It's a mess. The exception is probably Next.js but it's…
I saw it and I don't think it make it any justice, Ruby on Rails changed the paradigm of creating web applications with routes instead of files (like PHP, JSP and Webforms did) with the MVC pattern that now is present in every respectable web framework and the documentary doesn't tell that. It was enjoyable though.
I saw it and I don't think it make it any justice, Ruby on Rails changed the paradigm of creating web applications with routes instead of files (like PHP, JSP and Webforms did) with the MVC pattern that now is present in every respectable web framework and the documentary doesn't tell that. It was enjoyable though.
I kind of feel bad mentioning Struts and Rails in the same sentence, though, as Rails did much more than Struts.
> if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. I used to love this, untill I started to hate it. I am convinced this is a major contributor to why so many Rails apps turn into an unmaintainable mess over years. Who measures onboarding in hours? It's fine if it takes a day or two to understand the domain. And the framework. An…
i’m preparing a talk for either railsconf or railsworld that puts this question/concern to the community. two times i have deviated from the standard apps/{models,controllers,views} layout and i have profited massively, especially in terms of conceptual integrity and abstraction. all my code lives in app/lib under domain-specific directories. this includes the models. the only part worth separating is the web router…
Two figures that inspired me were missing, why the lucky stiff and Ryan Bates from railcasts fame. Otherwise great docu with DHH "f*uk you" slide which does give an insight into successful open source projects.
Earlier quoted context omitted.
Ryan Bates is a legend
Ryan did so much for the rails community and all because of the joy for RoR. Unfortunately iirc Ryan suffered a burnout and had a lengthy break. I hope all that is better now.