Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Cocoa (OS X)
Cocoa (OS X)

31
33
+ 1
6
Rails
Rails

8.1K
5K
+ 1
5.3K
Add tool

Cocoa (OS X) vs Rails: What are the differences?

Developers describe Cocoa (OS X) as "The Cocoa frameworks consist of libraries, APIs, and runtimes that form the development layer for all of OS X". Much of Cocoa is implemented in Objective-C, an object-oriented language that is compiled to run at incredible speed, yet employs a truly dynamic runtime making it uniquely flexible. Because Objective-C is a superset of C, it is easy to mix C and even C++ into your Cocoa applications. On the other hand, Rails is detailed as "Web development that doesn't hurt". Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Cocoa (OS X) and Rails can be categorized as "Frameworks (Full Stack)" tools.

"Great community " is the primary reason why developers consider Cocoa (OS X) over the competitors, whereas "Rapid development" was stated as the key factor in picking Rails.

Rails is an open source tool with 43.6K GitHub stars and 17.5K GitHub forks. Here's a link to Rails's open source repository on GitHub.

- No public GitHub repository available -

What is Cocoa (OS X)?

Much of Cocoa is implemented in Objective-C, an object-oriented language that is compiled to run at incredible speed, yet employs a truly dynamic runtime making it uniquely flexible. Because Objective-C is a superset of C, it is easy to mix C and even C++ into your Cocoa applications.

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Cocoa (OS X)?
Why do developers choose Rails?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Cocoa (OS X)?
What are the cons of using Rails?
    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use Cocoa (OS X)?
    What companies use Rails?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Cocoa (OS X)?
    What tools integrate with Rails?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Cocoa (OS X) and Rails?
    Node.js
    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
    ASP.NET
    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
    Django
    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
    Laravel
    It is a web application framework with expressive, elegant syntax. It 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.
    Android SDK
    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.
    See all alternatives
    Decisions about Cocoa (OS X) and Rails
    No stack decisions found
    Interest over time
    Reviews of Cocoa (OS X) and Rails
    No reviews found
    How developers use Cocoa (OS X) and Rails
    Avatar of StackShare
    StackShare uses RailsRails

    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.

    Avatar of Karma
    Karma uses RailsRails

    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.

    Avatar of Instacart
    Instacart uses RailsRails

    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.

    Avatar of Tim Lucas
    Tim Lucas uses RailsRails

    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.

    Avatar of Ngakkan Nyaagu
    Ngakkan Nyaagu uses RailsRails

    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.

    How much does Cocoa (OS X) cost?
    How much does Rails cost?
    Pricing unavailable
    Pricing unavailable
    News about Cocoa (OS X)
    More news