paultannenbaum

Did DHH actually agree to do this before you guys built this?

One thing that is not clear from your site, that I think should be, is that the code discussions need to happen over unconventional Rails design patterns. DHH was saying he was willing to ping pong on the original discussion thread over a design pattern in a submitted article that he thought was an unnecessary abstraction.

Looks like it was built with Flash, so that could be it. Its a really cool project if you do get a chance to check it out on another device.

Nice resource. It would be cool if the author added links to the libraries that are being referenced.

Correct me if I am wrong, but this is just guides provided by Github. I think it would be great if we could fork a guide and create our own.

I sympathize with most of this post, but the one thing that I don't get is this line:

"I can’t go much longer without a paycheck. But, I can’t imagine working for somebody else. I wish my wife understood that."

If the author really is as down and out as he claims to be, I think somebody offering him good money to get his life back on track might be something that is welcome. He can always work for himself once things straighten out.

If you actually read her post, she gives all the details there. Rails + Backbone + pg

For content sites, you are correct. But what about an in browser app, like Trello. Obviously in those cases javascript significantly improves the experience. So its just a case by case scenario. But I agree with the general point you are trying to make, and I work as a front-end dev who builds a lot of js heavy web pages/apps for a living.

Just curious, have you guys given bower a chance, and if so why did you guys end up going with component. Component seems to be slightly more opinionated, less adopted, but really nice.

I think they are trying to ramp up their mobile efforts. My friends company was recently acquired by them, and it was for this reason.

I received an email from them with the same content before I opened hacker news, and had the same thoughts as you. So no, I dont think your reading into it too much.

Maybe my understanding is wrong, but closure (and closurescript) are compiled languages. Angular is a UI framework, so comparing them is apples to oranges.

And I think the Angular community would be thrilled if it had even close to the kind of documentation that Rails has. You are correct, no one framework will rule them all, but there are examples of OS projects that have good docs (like jQuery and Rails) that can be used as comparisons when evaluating a framework.

Since we are going off on a tangent, a cool camping hack when you don't have ice is to stuff a beer in a tube sock, dunk it in water, and hang/tie it to a tree branch in the shade. If there is even a touch of wind it will be nice and cold in 10 minutes.

I've used both extensively.

Foundation uses SASS, is more modular in approach, is much easier to re-skin, and has a better grid system.

Bootstrap uses LESS, has much more mind share, more plugin and theme support, and has better default styling.

Both are great frameworks. I tend to use Bootstrap for prototyping, and Foundation for production.

These guys are a recruiting firm, so its in their interest to pump up the numbers. Here is a quora thread I used when I was trying to figure out my current market worth: http://www.quora.com/Salary-Comparisons/Silicon-Valley-Salar...

For anyone that is looking to get better at TDD with javascript, I highly recommend James Shore's webcast site: http://www.letscodejavascript.com/

Webstorm by Jetbrains has some really nice features if you are doing a lot of JS development. It is an IDE, but if you are ok with that it is quite good IMO

One more to add to the list: http://livereload.com/

You can do this with livereload: http://livereload.com/

Grunt has a live reload plugin that is fairly easy to set up

I agree. I used to almost always consider giving at least something to a cause I deemed worthy when I was approached by someone soliciting for donations, but now that I can't walk down market street without being harassed. Now I just tend to just shut everyone out as a result.

This is great! I realy like the audio and how good they sound mixed/matched. This would be a really cool compliment to the awesome chrome extension 'Currently'

To handle the callback pyramid of doom, look into javascript promises.

Another option is using a timeline based tool like Sencha's Animator: http://www.sencha.com/products/animator

I agree if everything in your app follows a perfectly restful pattern, but what about if you want to capture application state that does not belong in a database. For example, what if you have an online store that has many different filters to narrow down selections. And you want to share this url with someone.

How would this be done using a RESTful url path? You have to use url params. If so, this seems to be a nice solution if your using a lot of params.

While I agree with the general idea behind the article (object orient your css), I think the second demonstration involving margins is an example of OOCSS gone wrong.

If you are injecting your markup elements with classes like "mbm mts mrl" (or padding, or anything else that is essentially just a css property), this is not much different than just inlining your styles. If you want this level of reusability in your css, use sass and create these as placeholders. From there give your dom element a some kind of class(es) that can extend several of these placeholder values.

Ian Storm had a very well written article that hits on this more: http://ianstormtaylor.com/oocss-plus-sass-is-the-best-way-to...

How was this done? Is it is as simple as changing the git timestamp?

http://stackoverflow.com/questions/454734/how-can-one-change...

If you guys are using heroku, you might want to scale up your dynos right now. I am getting the application error page when I try to sign up.

The ASCII art in the javascript console is a very nice touch: http://cl.ly/image/3B1d1k1H1902

Very neat. I could definitely use this for some internal documentation. Thanks for the cool tool.

Strange enough, codrops recently published an article with very similar effects and styling: http://tympanus.net/codrops/2013/09/18/creative-loading-effe...

I see the article was published on the 18th, and hubspot created the repo on the 11th, so I wonder if this was just a coincidence. Either way, nice work

I think it looks nice, but I don't think creating one screenshot view can be considered a "design facelift". I would expect to see multiple views through the app, how you handled navigation and user flow, and how your design will be flexible as Watsi moves forward and adds more features.

I love the initiative, but IMO its not very useful in its current form.

Most javascript code is actually synchronous. It is the event loop (xhr requests, timers, timeouts, etc.) that is async. TLDR, some parts of the language are sync, some are async