Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: 99e8c8ebc1
Fetching contributors…

Cannot retrieve contributors at this time

file 98 lines (81 sloc) 4.784 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
<!DOCTYPE html />

<html lang="en">
  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="description" content="Personal Website of Steven Davie">
    <meta name="author" content="Steven Davie">

    <title>Ember.js - inital thoughts</title>

    <link rel="stylesheet" href="/css/styles.css">
  </head>
  <body>
    <div class="brand header">
      <img src="http://www.gravatar.com/avatar/68398d7dbc1525103e6dd421beff013d" class="image" />

      <div class="container">
        <h2><a href="/">steven davie</a></h2>
        <p class="tagline">I do web stuff.</p>
        <ul class="social-networks inline">
          <li class="sn-icon">
            <a href="http://www.linkedin.com/pub/steven-davie/21/67a/88a/" title="linkedin"><img src="/images/linkedin.png"/></a>
          </li>
          <li class="sn-icon">
            <a href="https://github.com/stvn" title="github"><img src="/images/github.png"/></a>
          </li>
          <li class="sn-icon">
            <a href="http://www.facebook.com/steve.davie.121" title="facebook"><img src="/images/facebook.png"/></a>
          </li>
          <li class="sn-icon">
            <a href="http://twitter.com/stevendavie" title="twitter"><img src="/images/twitter.png"/></a>
          </li>
          <li class="sn-icon">
            <a href="https://plus.google.com/105282344983798554188/posts" title="google+"><img src="/images/google-plus.png"/></a>
          </li>
          <li class="sn-icon">
            <a href="http://www.flickr.com/photos/stevendavie" title="flickr"><img src="/images/flickr.png"/></a>
          </li>
        </ul>
      </div>
      <div class="clear-fix"></div>
    </div>

    <div class="content">
        <div class="post">
  <h4 class="post-title"><a href="/tech/2012/12/17/second-post.html">Ember.js - inital thoughts</a></h4>
  <p class="post-info">
    <span class="category">tech</span>
    <span class="date">December 17, 2012</span>
  </p>

  <div class="post-content">
    <p>
      I started using <a href="http://www.emberjs.com" target="_blank" class="inline-link">ember.js</a> for a couple different projects recently and I'm not exactly sure how I feel about it. On one hand, it's AWESOME! On the other hand, it seems needlessly complicated and is such a paradigm shift from traditional front-end development that it makes it difficult to get anything done (the first time).
    </p>

    <p class="section-title">
      Documentation
    </p>

    <p>
      The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll accept this is due to the framework's heavily opiniated ways (which I like btw).
    </p>

    <p class="section-title">
      Templating
    </p>

    <p>
      Out of the box, ember uses <a href="http://handlebarsjs.com/" target="_blank" class="inline-link">handlebars.js</a> for templating. This is great, because I LOVE handlebars! What's not great, is that it seems to disrupt everything I thought I knew about handlebars. You can't just go write a handlebar helper like you used to. Now, you need to know that ember passes a <a href="http://stackoverflow.com/questions/12184696/handlebars-helpers-in-ember-js" target="_blank" class="inline-link">context variable that must be interrogated within the helper</a>. Oh, yes, it is easy -- once you know there is this a context!
    </p>

    <p class="section-title">
      Boilerplate
    </p>

    <p>
      The advantage of ember over other frameworks is that it's supposed to reduce the amount of boilerplate code to handle tasks that are common across most (if not all) applications. In this regard, ember does an excellent job. Once you get the framework up and running and have your <strong>V</strong> plugged into your <strong>C</strong> and your <strong>C</strong> plugged into your <strong>M</strong>, buidling out an applicaiton becomes relatively simple and separation of responsibility is barely a consideration for the developer.
    </p>

    <p class="section-title">
      Overall
    </p>

    <p>
      Overall, I don't hate it. I think I actually like it. I'm going to keep plugging away on it and see how it goes. Who knows, it might just be me that's needlessly complicated.
    </p>

  </div>
</div>

    </div>

    <div class="footer">
      &copy; 2012 stevendavie.com
    </div>
  </body>
</html>
Something went wrong with that request. Please try again.