<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Javascript on UberMongoose</title>
		<link>http://localhost:1313/tags/javascript/</link>
		<description>Recent content in Javascript on UberMongoose</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 13 Jul 2014 11:03:43 +0530</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Emulating Classical Inheritance in Javascript</title>
				<link>http://localhost:1313/post/javascript-classical-inheritance/</link>
				<pubDate>Sun, 13 Jul 2014 11:03:43 +0530</pubDate>
				<guid>http://localhost:1313/post/javascript-classical-inheritance/</guid>
				<description>&lt;p&gt;Javascript isn’t a classical language. &lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/JavaScript/Inheritance_and_the_prototype_chain&#34;&gt;It’s prototypal&lt;/a&gt;, which is a bit like every object being a class in waiting. You can create graphs of objects where one object inherits from another, but the idea of classes doesn’t really exist.&lt;/p&gt;&#xA;&lt;p&gt;This can be a drawback, specially with code encapsulation. It becomes difficult to hide private implementation details from public interfaces to the object because Javascript provides no native access modifiers. There is however a number of methods for simulating classical inheritance and encapsulation in Javascript while things nice and clean&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
