Hacker News, Reddit, Stack Overflow Stats
What is Rails?
Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
What is Laravel?
Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
Pros about this tool
Cons about this tool
2170 Companies Using Rails
663 Companies Using Laravel
What are some alternatives to Rails and Laravel?
Why Laravel Framework
March 18, 2015 05:14
I moved from .NET and Rails to Laravel, and since then never thought to go back. I feel Laravel framework has the capability to overcome all modern frameworks.
At Soft Pyramid we are developing rich business applications using Laravel Framework, and never feel any limitation even for complex reporting.We have written REST apis, complex ERP solutions and found awsome in all areas.
cyrusstoller uses Rails
Gardenbed installs all of the tools that are necessary to deploy a Ruby on Rails application to a VPS.
Instacart uses Rails
Web has always been in Rails from the beginning, so we used Redis for caching our items, which we had, from the beginning. Rails is kind of what we were comfortable with, and we knew we wanted the front end to be really, really snappy, so we de-normalized all the item attributes into Redis, and that's how it got served out.
winkler1 uses Rails
Karma uses Rails
We use Rails for webpages and projects, not for backend services. Actually if you click through our website, you won't notice it but you're clicking though, I think, seven or eight different Rails projects. We tie those all together with a front-end library that we wrote, which basically makes sure that you have a consistent experience over all these different Rails apps.
It's a gem, we call it Karmeleon. It's not a gem that we released. It's an internal gem. Basically what it does is it makes sure that we have a consistent layout across multiple Rails apps. Then we can share stuff like a menu bar or footer or that kind of stuff.
So if we start a new front end project it's always a Rails application. We pull in the Karmeleon gem with all our styling stuff and then basically the application is almost ready to be deployed. That would be an empty page, but you would still have top bar, footer, you have some custom components that you can immediately use. So it kind of bootstraps our entire project to be a front end project.
StackShare uses Rails
The first live version of Leanstack was actually a WordPress site. There wasn’t a whole lot going on at first. We had static pages with static content that needed to be updated manually. Then came the concept of user-generated content and we made the switch to a full on Rails app in November of last year. Nick had a lot of experience with Rails so that made the decision pretty easy. But I had also played around with Rails previously and was comfortable working with it. I also knew I’d need to hire engineers with a lot more experience building web apps than I do, so I wanted to go with a language and framework other people would have experience with. Also, the sheer number of gems and tools available for Rails is pretty amazing (shout to RubyToolbox ).
I don’t see us ever having to move away from Rails really, but I could be wrong. Leanstack was built in Rails 3. For StackShare we decided to upgrade to Rails 4. Biggest issue with that has been caching. DHH decided to remove the standard page and action caching in favor of key-based caching (source)[http://edgeguides.rubyonrails.org/caching_with_rails.html#page-caching]. Probably a good thing from a framework-perspective. But pretty shitty to have to learn about that after testing out your new app and realizing nothing is cached anymore :( We’ll need to spend some more time implementing "Russian Doll Caching", but for now we’ve got a random mixture of fragment and action caching (usually one or the other) based on which pages are most popular.
pludoni GmbH uses Rails
Well-established framework for rapid development of web apps. Huge repository of good integrated 3rd party libraries (Gems)
novarac23 uses Rails
Using Rails as a go to thing for creating API's or full blown web apps. Love writing Ruby, convention over configuration style is great and it has a tons of gems and community behind it :)
SmartLogic uses Rails
Rails makes it easy to build out sophisticated Web apps quickly, without re-inventing the wheel for each of our clients. SmartLogic ♥ Rails!
hpneo uses Rails
Rails is our product's backend app. It handles user registration/logging, product's logic and Inspector communication with our users' devices.
RocketFuel uses Rails
Rails is used for some endpoints of our Frontend API. Though there are talks of deprecating it.
toolmantim uses Rails
Rails 5 (beta 3) provided a nice structure for rendering responses, linking to front-end assets (compiled previously via Webpack), handling sessions w/ tailor made login links via an email button/token, background jobs, and creating an admin behind basic auth to allow managing of users and purchases.
PSESD uses Rails
PRS UI app is built in Rails (originally a proof of concept which has now become the primary tool for interaction with the PRS API).
jflynn33 uses Rails
A Ruby environment that takes on all the heavy lifting. Install Ruby on Rails, and create a working web app with a single command line. No brainer.
Ngakkan Nyaagu uses Rails
For this project rails was ideal due to new features introduced in Rails 5 that allowed us to build a lightweight "API only" project. Developer familiarity and the ability to rapidly iterate, as well as providing an accessible testing framework were additional factors.
Flutter Health Inc. uses Rails
Used for searching for doctors, adding articles, recipes, videos. Filtering by tags and categories.
ahamilton9 uses Laravel
I don't think there's another PHP framework that can even come close to the power of Laravel at this point.
FRKodes uses Laravel
Laravel is my favorite framwork to make PHP stuff in these days, easy to use, a lot of documentation about it, just pretty cool.
BrightMachine uses Laravel
The best PHP framework right now, intuitive and growing up quickly.
We use Laravel in the outer layer of our Clean Architecture codebases, whereby the domain model does not rely on the framework as a whole.
CodeBee uses Laravel
Our PHP framework of choice that greatly speeds up development and provides useful tools.
nalexander21 uses Laravel
An excellent PHP framework employing SOLID principles to rapidly develop web-site systems and connect them to databases. Custom development of admin screens for website management.
romaninsh uses Laravel
We are compatible with some Laravel modules. Also DSQL can be a more powerful replacement to Laravel Query Builder.
AlexanderSix uses Laravel
My go-to PHP backend framework. It's super usable and can be deployed almost anywhere with very little headache.
softwareantelope uses Laravel
MVC Framework for building sophisticated applications around a database with many time saving features.
kfancy uses Laravel
See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.
OdinsHat uses Laravel
A clean, easy to understand, well documented framework with excellent tools and a great community providing every imaginable extension to add functionality to your project.
jakewtaylor uses Laravel
Laravel is the PHP framework we use. It speeds up development and simplifies a lot of PHP. Complicated at first but saves time once you're comfortable with it.
Shirtigo GmbH uses Laravel
seedshirt.de is completely written in Laravel 5.3 following its design patterns closely.