chadhietala

This is pretty much the same thing that Ember ListView does. http://emberjs.com/list-view/

You can use this https://github.com/Jakobo/redefine

You might want to look at http://www.venusjs.org/ to get some ideas for supporting multiple testing frameworks. It uses an annotation approach kind of how you include files for tests. The automatic mocking is pretty awesome though.

Thank you for this!

Not trying to be tangental, but I believe this is true with EmberJS which was originally modeled off of Coaco. You inherit from Ember's base Objects (ArrayController, ObjectController, etc) and rarely find yourself extend classes that you write. Here is a hierarchy of the "base" classes. http://emberjs.jsbin.com/bahetoka/1

Glad that problem is solved. -_-

I have no use for this, but it's awesome.

This man suffers from a case of what I now call "CK Syndrome". Everything is awesome and he's still complaining.

JavaScript for sure. Stay away from frameworks/libraries in the beginning and learn the ins and outs of the language first.

There are plans to have a "cookbook" section on the EmberJS site that will be one of the go to places to answer the question of "How do I do X in Ember?". It's currently on the master branch for the site, so expect that soon. In the mean time here are some other video resources http://www.embercasts.com/ and http://ember101.com/. They may be slightly out of date but they are still relevant. Make sure to look in the console for warnings about deprecations.

I stopped using CS because it's going to have some issues when ES6 becomes more of a real thing. For instance, how is CS going to handle for/of loops when ES6 has it's own for/of loops that is slightly different. The same goes for class and super.

There will have to be CS2 that introduces new semantics and old apps will have to be migrated.

Was going to say the same thing.

I had to do this for an interview... in clojure. https://github.com/chadhietala/smuggler

As someone that just went through a whole slew of interviews I would say I agree with this to some extent. I'm a frontend developer and while CS principals are important, asking questions that are not practical to everyday development, are counter-productive and do not give you a view into how that person tackles a real problem.

Things like "write a function that performs merge sort", are bullshit because you would never do this in real life, largely because languages have sort methods that are already extremely performant. Plus a lot of languages will already be using some variant of merge sort and exposing it as a "sort" method.

If you are given a problem like "create a tabbed news component" or you're asked to do a small project (nothing longer than an hour), I think you can still get a good understanding of how people solve problems. This is less stressful, less "gotcha" mentality, and a fair approach.

Been using Tomorrow Eighties for the past 6 months or so. I like it a lot.

I support this message as a Marketing/Finance major turned software engineer.

Using push state and using non-hash banged urls is the right move. Twitter is pretty much unusable without javascript, and it doesn't look like they ever got around to implementing a non-js fallback for the site. Best solution is to have both (JSON and static) representations or use something like pjax https://github.com/defunkt/jquery-pjax.

Another 1st world problem solved.

Billion dollar valuation. Thats how heard it works I heard.

We just launched a new marketing site for http://www.wanttt.com. We used Bootstrap as a starting place. You can see the Want button on newest merchant's site, Wiz Khalifa's Merch Shop, http://store.wizkhalifa.com/apparel-1/black-yellow-mens-stan...

We recently have been working on http://www.wanttechnologies.com which uses bootstrap. But you can't really tell. Only really used the "scaffolding" and buttons.

Are they using pjax or something like it for the marketing site. I know you had mentioned that's how the application works. Just wondering if there are any plans of open sourcing that.

This looks good. I've messed around with Railways http://railwayjs.com/ but some parts are funky and the docs haven't been updated since they opened the project. Also looked at Matador http://obvious.github.com/matador/ and actually was re-writing it in coffeescript to use CS' classes instead of the Klass plugin, but lacked docs. Zappa http://zappajs.org/ is written CS but really isn't an MVC. This looks well documented and it's in CS which I like. +1

Want (the startup I work for) is just like Pinterest and we are allowing a community discover and share things that want or like. The difference is that we are solely products. We just rolled out a feature this week that auto-generates store fronts for merchants based upon things that community likes from that store.

http://wanttt.com/

http://wanttt.com/w/merchant/store/298/?products

We recently have switched over to using CoffeeScript in production and haven't looked back. One thing we found out real fast was to not compile the CS until you go to staging or QA. The way we get around this is using RequireJS (http://requirejs.org/) and the CoffeeScript Plugin(https://github.com/jrburke/require-cs). This buys you the ability to compile at runtime in the browser, so you don't have this mess of CoffeeScript files and compiled JS files in your source. When you are ready to build for production or QA you use RequireJS' optimization tools to concatenate, minify, obfuscate and compile the code. Hope that helps.