12 Jun '14, 3pm

Shared Terminology Yet Different Concepts Between Ember.js and Rails

Shared Terminology Yet Different Concepts Between Ember.js and Rails Posted by croaky on June 12, 2014 — 0 comments Developers who are well versed in Ruby on Rails (or other MVC implementations) and start learning Ember.js may find it surprising that, even though there’s shared vocabulary, denoted concepts are sometimes very different. The first and obvious difference comes from the fact both are web frameworks. Rails facilitates the creation of web apps that offer mainly an HTTP interface to interact with. On the other hand, Ember helps creating web apps that interface directly with humans (through clicks, taps, key presses, etc). They are both web application frameworks, but the former is server side and the latter client side. A look into their workflows will shed light over the main differences.

Full article: http://www.rubyflow.com/items/11155-shared-terminology-ye...

Tweets

Shared Terminology Yet Different Concepts Between Ember.js and Rails

Shared Terminology Yet Different Concepts Betwe...

robots.thoughtbot.com 12 Jun '14, 3pm

Developers who are well versed in Ruby on Rails (or other MVC implementations) and start learning Ember.js may find it sur...

If you missed @peterc's RubyWeekly, you missed QLer @mjezzi's video tutorial: Building Complex Domains in Rails.

If you missed @peterc's RubyWeekly, you missed ...

rubyweekly.com 13 Jun '14, 3pm

Modelling large, complex domains ‘the Rails way’ can be painful. The goal is to allow your Rails application to express th...

Search Engine Basic Concepts

Search Engine Basic Concepts

searchenginewatch.com 16 Jun '14, 11am

Personalization: If a search engine knows that you have been to a particular page before (in particular, recently), it cou...

80% Off LimTime Learn Ruby on Rails from Scratc...

udemy.com 19 Jun '14, 4pm

This course teaches you the amazing and powerful technology of Ruby on Rails. This technology forms the backend of amazing...