forked from stantona/stantona.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
293 lines (213 loc) · 25.2 KB
/
Copy pathatom.xml
File metadata and controls
293 lines (213 loc) · 25.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Adam Stanton]]></title>
<link href="http://stantona.github.com/atom.xml" rel="self"/>
<link href="http://stantona.github.com/"/>
<updated>2012-12-16T22:55:04-08:00</updated>
<id>http://stantona.github.com/</id>
<author>
<name><![CDATA[Adam Stanton]]></name>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[A tale of two object models: Javascript and Ruby (Part 1)]]></title>
<link href="http://stantona.github.com/blog/2012/12/12/a-tale-of-two-object-models-javascript-and-ruby/"/>
<updated>2012-12-12T23:22:00-08:00</updated>
<id>http://stantona.github.com/blog/2012/12/12/a-tale-of-two-object-models-javascript-and-ruby</id>
<content type="html"><![CDATA[<p>This past year I’ve been developing a web application with Ruby on Rails and javascript, and although javascript
is not a new language for me, I’ve had an amazing time learning Ruby and its powerful metaprogramming capabilities.
As I regularly switch between the two languages (as you do buidling web applications) I’ve recently found myself comparing the two
object models. I thought I would give my own personal take on the object models of
both languages, cementing the fundamental differences while demonstrating the similarities</p>
<p>This is a loaded topic, so I thought I would start with the fundamentals and talk about what objects are exactly in these two languages.</p>
<h2>What are javascript objects?</h2>
<p>Javascript objects are composite data structures comprised of properties.
You can create simple objects and write to properties like so:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="kd">var</span> <span class="nx">obj</span> <span class="o">=</span> <span class="p">{};</span>
</span><span class='line'><span class="nx">obj</span><span class="p">.</span><span class="nx">name</span> <span class="o">=</span> <span class="s2">"Adam"</span>
</span></code></pre></td></tr></table></div></figure>
<p>is the same as:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="kd">var</span> <span class="nx">obj</span> <span class="o">=</span> <span class="p">{</span>
</span><span class='line'> <span class="nx">name</span><span class="o">:</span> <span class="s2">"Adam"</span>
</span><span class='line'><span class="p">};</span>
</span></code></pre></td></tr></table></div></figure>
<p>which is the same as:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="kd">var</span> <span class="nx">obj</span> <span class="o">=</span> <span class="p">{};</span>
</span><span class='line'><span class="nx">obj</span><span class="p">[</span><span class="s2">"name"</span><span class="p">]</span> <span class="o">=</span> <span class="s2">"Adam"</span><span class="p">;</span>
</span></code></pre></td></tr></table></div></figure>
<p>The above examples demonstrate how objects are created using the literal technique (you can also create javascript objects using constructor functions, but we’ll get to that in part two).
Literal objects are simple objects that you mold to your liking by setting properties. Since functions are also objects, you can define a property as a function
and execute it:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="kd">var</span> <span class="nx">obj</span> <span class="o">=</span> <span class="p">{};</span>
</span><span class='line'><span class="nx">obj</span><span class="p">.</span><span class="nx">sayHi</span> <span class="o">=</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
</span><span class='line'> <span class="k">return</span> <span class="s2">"hi"</span><span class="p">;</span>
</span><span class='line'><span class="p">}</span>
</span><span class='line'><span class="nx">obj</span><span class="p">.</span><span class="nx">sayHi</span><span class="p">();</span> <span class="c1">// returns hi</span>
</span></code></pre></td></tr></table></div></figure>
<p>Note the familiar <code>()</code> syntax after the function call: this means execute me like I’m a function. If you leave that out, you return the function
as if you’re calling the name property shown above.</p>
<p>It’s reasonable to think that javascript objects look a lot like Hashes, and if you were to compare JS objects to Ruby hash objects, they look syntactically similar.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="nb">hash</span> <span class="o">=</span> <span class="p">{</span> <span class="nb">name</span><span class="p">:</span> <span class="s2">"Adam"</span> <span class="p">}</span> <span class="c1">#ruby hash</span>
</span><span class='line'><span class="nb">puts</span> <span class="nb">hash</span><span class="o">[</span><span class="ss">:name</span><span class="o">]</span> <span class="c1">#prints "Adam"</span>
</span></code></pre></td></tr></table></div></figure>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='javascript'><span class='line'><span class="kd">var</span> <span class="nx">obj</span> <span class="o">=</span> <span class="p">{</span> <span class="nx">name</span><span class="o">:</span> <span class="s2">"Adam"</span> <span class="p">}</span> <span class="c1">// js object</span>
</span><span class='line'><span class="nx">console</span><span class="p">.</span><span class="nx">log</span><span class="p">(</span><span class="nx">obj</span><span class="p">[</span><span class="s2">"name"</span><span class="p">])</span> <span class="c1">//prints "Adam"</span>
</span></code></pre></td></tr></table></div></figure>
<p>As you can see, JS objects appear like simple dictionaries, a repository of properties that reference other objects and you can access these properties directly on the object.
As a side note, various JS engines do not necessarily implement objects as hash tables under the hood. Check out the way <a href="https://developers.google.com/v8/design?hl=sv#prop_access">V8</a>
implements property access.</p>
<h2>What are Ruby objects?</h2>
<p>Where a JS object <em>is a collection</em> of properties that reference other objects, a ruby object <em>contains a hash</em> of instance variables that reference other objects. You can not access these
instance variables in the same way that you can access (read or write to) JS properties. Ruby enforces a level of data encapsulation which protects these variables.
Only when you are within the context of an object, which occurs during a method call, you can create or alter instance variables.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
<span class='line-number'>6</span>
<span class='line-number'>7</span>
<span class='line-number'>8</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="k">class</span> <span class="nc">Simple</span>
</span><span class='line'> <span class="k">def</span> <span class="nf">var</span>
</span><span class='line'> <span class="vi">@var</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'> <span class="k">def</span> <span class="nf">var</span><span class="o">=</span><span class="p">(</span><span class="n">val</span><span class="p">)</span>
</span><span class='line'> <span class="vi">@var</span> <span class="o">=</span> <span class="n">val</span>
</span><span class='line'> <span class="k">end</span>
</span><span class='line'><span class="n">simple_obj</span> <span class="o">=</span> <span class="no">Simple</span><span class="o">.</span><span class="n">new</span>
</span></code></pre></td></tr></table></div></figure>
<p>Before we talk about the instance variable <code>@var</code>, it’s a good time to discuss the <code>Simple</code> class above, because Ruby objects can not exist without classes.</p>
<h3>A (very) brief intro to Ruby classes</h3>
<p>Ruby is a class based language, whereas JS is not (although you can achieve level of class like behaviour). In Ruby, every object has an associated class:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="mi">2</span><span class="o">.</span><span class="n">class</span>
</span><span class='line'><span class="o">=></span> <span class="no">Fixnum</span>
</span><span class='line'><span class="o">[</span><span class="mi">2</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">class</span>
</span><span class='line'><span class="o">=></span> <span class="no">Simple</span>
</span></code></pre></td></tr></table></div></figure>
<p>You could say that the JS equivalent to this method is the <code>__proto__</code> property, even though this represents the prototype object from which the JS object was created.
This will be discussed in the length in part two.</p>
<p>Ruby classes are a place to define methods, which give objects their behaviour:</p>
<figure class='code'><figcaption><span>Passing false excludes instance methods from ancestor classes</span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="no">Simple</span><span class="o">.</span><span class="n">instance_methods</span><span class="p">(</span><span class="kp">false</span><span class="p">)</span>
</span><span class='line'><span class="o">=></span> <span class="o">[</span><span class="ss">:var</span><span class="p">,</span> <span class="ss">:var</span><span class="o">=]</span>
</span></code></pre></td></tr></table></div></figure>
<p>Notice that the methods returned above are defined in our Simple class These are the proverbial getters and setters that are familiar if you have used Java or C#. They provide
access to the <code>@var</code> instance variable that we can not access otherwise. In Ruby, we can simplify the Simple class code by calling the class method <code>attr_accessor</code> to define these
getters and setters for us:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="k">class</span> <span class="nc">Simple</span>
</span><span class='line'> <span class="kp">attr_accessor</span> <span class="ss">:var</span>
</span><span class='line'><span class="k">end</span>
</span></code></pre></td></tr></table></div></figure>
<p>If you repeat the <code>instance_methods</code> call on our new implementation:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="no">Simple</span><span class="o">.</span><span class="n">instance_methods</span><span class="p">(</span><span class="kp">false</span><span class="p">)</span>
</span><span class='line'><span class="o">=></span> <span class="o">[</span><span class="ss">:var</span><span class="p">,</span> <span class="ss">:var</span><span class="o">=]</span>
</span></code></pre></td></tr></table></div></figure>
<p>the results are the same as the original implementation. <code>attr_accessor</code> wrote these methods for us. This is a little bit of <em>metaprogramming</em> magic (which we will talk about in a future part).</p>
<p>In JS, there would be no need to create functions to do this, since properties on JS objects are publicly accessible.</p>
<p>In Ruby, classes (like almost everything) are objects and so we can call methods directly on them:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="no">Simple</span><span class="o">.</span><span class="n">is_a?</span> <span class="no">Object</span>
</span><span class='line'><span class="o">=></span> <span class="kp">true</span>
</span><span class='line'><span class="o">[</span><span class="mi">2</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="no">Simple</span><span class="o">.</span><span class="n">class</span>
</span><span class='line'><span class="o">=></span> <span class="no">Class</span>
</span></code></pre></td></tr></table></div></figure>
<p>Notice that the class of Simple is Class. If you peek at the instance methods of Class:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="no">Class</span><span class="o">.</span><span class="n">instance_methods</span><span class="p">(</span><span class="kp">false</span><span class="p">)</span>
</span><span class='line'><span class="o">=></span> <span class="o">[</span><span class="ss">:allocate</span><span class="p">,</span> <span class="ss">:new</span><span class="p">,</span> <span class="ss">:duplicate</span><span class="o">]</span>
</span></code></pre></td></tr></table></div></figure>
<p>you will find the <code>new</code> method. This method is the mechanism to create a new object (covered in part two).</p>
<p>Classes are responsible for a lot of magic in Ruby, and we will cover Ruby classes extensively in future parts.</p>
<h3>Instance variables</h3>
<p>So getting back to the <code>@var</code> instance variable. In the sample above, <code>@var</code> is accessible through the getters and setters:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
<span class='line-number'>4</span>
<span class='line-number'>5</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">4</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">var</span>
</span><span class='line'><span class="o">=></span> <span class="kp">nil</span>
</span><span class='line'><span class="o">[</span><span class="mi">5</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">var</span> <span class="o">=</span> <span class="mi">4</span>
</span><span class='line'><span class="o">[</span><span class="mi">6</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">var</span>
</span><span class='line'><span class="o">=></span> <span class="mi">4</span>
</span></code></pre></td></tr></table></div></figure>
<p>Note that this appears similar to JS access to properties, but in fact, <code>var</code> is a method call on <code>simple_obj</code>, which is the method <em>receiver</em>. In the JS equivalent, var would be a property, not a method (function) call.</p>
<p>The @ notation basically means: <em>access this instance variable in the scope of the current context.</em>
The current context is the object referenced by <code>simple_obj</code>. The current context is an important concept in both JS and Ruby (which is where the <code>this</code> and <code>self</code> keywords come into play),
and we will cover this in part two when we look at object creation.</p>
<p>Remember when I said that instance variables are private to the object? Well this is not quite true. Ruby gives you a lot of power and has some interesting methods that allow you to peek inside the object:</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">1</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span> <span class="o">=</span> <span class="no">Simple</span><span class="o">.</span><span class="n">new</span>
</span><span class='line'><span class="o">[</span><span class="mi">2</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">instance_variables</span>
</span><span class='line'><span class="o">=></span> <span class="o">[]</span>
</span></code></pre></td></tr></table></div></figure>
<p>At this point, no instance variables have been assigned to the object.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">3</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">instance_variable_set</span><span class="o">[</span><span class="ss">:@var</span><span class="o">]</span> <span class="o">=</span> <span class="s2">"hi!"</span>
</span><span class='line'><span class="o">[</span><span class="mi">4</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">instance_variables</span>
</span><span class='line'><span class="o">=></span> <span class="o">[</span><span class="ss">:@var</span><span class="o">]</span>
</span></code></pre></td></tr></table></div></figure>
<p>Now that ‘@var’ is assigned, see it in the second call.</p>
<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='ruby'><span class='line'><span class="o">[</span><span class="mi">5</span><span class="o">]</span> <span class="n">pry</span><span class="p">(</span><span class="n">main</span><span class="p">)</span><span class="o">></span> <span class="n">simple_obj</span><span class="o">.</span><span class="n">instance_variable_get</span><span class="o">[</span><span class="ss">:@var</span><span class="o">]</span>
</span><span class='line'><span class="o">=></span> <span class="s2">"hi!"</span>
</span></code></pre></td></tr></table></div></figure>
<h2>Summary</h2>
<p>At their very core objects in JS and Ruby are simply repositories of references to other objects.</p>
<p>The essential difference is that JS does not restrict access to properties. The language itself does not support any data encapsulation on objects directly. That does not mean you can
not achieve this in other ways however through function scopes acting as modules.</p>
<p>Ruby on the other hand enforces a certain level of data encapsulation by not providing a simple way to access its internal instance variables. You have to enter the object’s context through a method call
to operate on instance variables. However, we just demonstrated above that there are methods that allow you to peek into, change or get individual instance variables which break
this data encapsulation.</p>
<p>Javascript objects are quite simple especially when created using the literal method.
It’s not until we look at object
creation in the next part that we see that JS objects can also be created via constructor functions. This opens up the concept of <em>prototypal inheritance</em>, which is javascript’s inheritance mechanism. This is where the JS
object model starts to get a little more involved.</p>
<p>Ruby objects are more involved since objects contain a reference to the class that created it. The object relies heavily on this relationship throughout its lifetime, since whenever a method is called, the object refers to its class (and potentially ancestor classes) to find and execute the method.
Classes (and it’s parent class, Module) are what make metaprogramming possible.</p>
<p>There is obviously <em>a lot</em> more to the object models of both languages, so I hope you will tune in to part two when I look at how objects are created in both languages.</p>
<h3>Further Resources</h3>
<ul>
<li><a href="http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742/ref=sr_1_1?ie=UTF8&qid=1355669318&sr=8-1&keywords=javascript+the+good+parts">Javascript: The Good Parts (Douglas Crockford)</a></li>
<li>Chapter 1 of <a href="http://pragprog.com/book/ppmetr/metaprogramming-ruby">Metaprogramming Ruby (Paulo Perotta)</a></li>
<li>Episode 1 of <a href="http://pragprog.com/screencasts/v-dtrubyom/the-ruby-object-model-and-metaprogramming">The Ruby Object Model and Metaprogramming (Dave Thomas)</a></li>
</ul>
]]></content>
</entry>
</feed>