James Gary jamesgary

Dissecting Ruby with Ruby

Get into a library
- bundle open wicked
- Make sure you've set your $EDITOR
Forget fancy debuggers
- All you need is puts
- A rubyist's tracer round: puts "================="
Notation

Throw something weird at people to keep their attention. Bored people don't learn anything, so focus on entertainment over being informative.

Go is compiled, garbage collected, strongly typed, OO
Lower level than Ruby, but still aimed at web
Go has an agenda
- Not welcome to a lot of styles of writing code
- Prodded to write code in a certain way
- Ruby doesn't have an agenda, but it does have idioms
What are the design goals here?

Problem: Want users to have "rich client exp" (even though clients don't know what that means)
@dhh and @wycats offer different opinions (document vs json api)
But @noelrap just wants to write an e-commerce site
We tend to split stuff up into client stuff and server stuff between the user and data
@dhh says that the focus is on the server. The app lives on the server
@wycats says that the client is the focus, and the server just does whatever the client can't do (i.e. validation, persistence)
Where does the heart of your application live?

	App = Ember.Application.create();

	App.IndexRoute = Ember.Route.extend({
	model: function() {
	return EmberFire.Array.create({
	ref: new Firebase("https://dp-ember-chat.firebaseio.com/")
	});
	}
	});

	module AwesomeResource
	attr_reader :awesome_attributes

	def initialize(attributes={})
	@awesome_attributes = attributes
	@awesome_attributes.keys.each do \|method_name\|
	create_method(method_name.to_sym) do
	@awesome_attributes[method_name]
	end