HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
9elements
haml-coffee
HISTORICAL RECORD2011–2012
9elements / haml-coffee · Not publicly available

haml-coffee

Discover this repository through its Hacker News conversations.

6Distinct people
6Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month6 dated mentions

Observed mentions: 2011-05-09 18:52:03 UTC to 2012-01-30 16:08:34 UTC.

0122011-05-01 00:00:00 UTC to 2011-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 20112011-06-01 00:00:00 UTC to 2011-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-07-01 00:00:00 UTC to 2011-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-08-01 00:00:00 UTC to 2011-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-09-01 00:00:00 UTC to 2011-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20112011-10-01 00:00:00 UTC to 2011-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-11-01 00:00:00 UTC to 2011-12-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2011-12-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2012-01-01 00:00:00 UTC to 2012-02-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJan 2012

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20112011-05-01 00:00:00 UTC2011-06-01 00:00:00 UTC110
Jun 20112011-06-01 00:00:00 UTC2011-07-01 00:00:00 UTC000
Jul 20112011-07-01 00:00:00 UTC2011-08-01 00:00:00 UTC101
Aug 20112011-08-01 00:00:00 UTC2011-09-01 00:00:00 UTC000
Sep 20112011-09-01 00:00:00 UTC2011-10-01 00:00:00 UTC000
Oct 20112011-10-01 00:00:00 UTC2011-11-01 00:00:00 UTC000
Nov 20112011-11-01 00:00:00 UTC2011-12-01 00:00:00 UTC110
Dec 20112011-12-01 00:00:00 UTC2012-01-01 00:00:00 UTC101
Jan 20122012-01-01 00:00:00 UTC2012-02-01 00:00:00 UTC211

What Hacker News says

6 sources
sippndipp·Jan 9, 2012Submission

Node PR, you can do better

Today I've read this article http://venturebeat.com/2012/01/07/building-consumer-apps-with-node/ and i find it a little disturbing. Node.js is a totally cool piece of technology and I'm loving it, but in this article node is embraced for the wrong reasons - let me be the advocatus diaboli: It’s JavaScript! Yes it's JavaScript, and as he said every developer knows a little JavaScript. But JavaScript has some bad parts http://www.youtube.com/watch?v=hQVTIJBZook and as a newbie JavaScript developer you can easily shoot yourself in the foot http://wtfjs.com/ Code re-use at every level: browser, back end & database We at 9elements dream of all tier code re-usages for several years https://github.com/janv/kupo but in the wild I actually don't see it. Also, do you really want your super secret business logic shared with the client? Code re-use a
Read the rest
in't easy, but someone has to do it. There are some great concepts like http://nowjs.com/ but I guess the status quo of JavaScript is not there yet. We need ES5+ in the browser to do the really good stuff. Strong, responsive and enthusiastic community Big part of the community is great! Some really brilliant minds out there! But there is also a part of not so skilled dudes who hated rails and now just hopping on the node bandwagon for the wrong reasons (and leaving behind a trail of unmaintained github repos w/o tests). Large productivity gains in HTML & CSS using Jade & Stylus Well, switching from HTML/CSS to HAML/SASS was a large productivity gain. Switching to Jade and Stylus was just felt "ok". The real performance boost at SASS dev came from Compass, which didn't existed for Stylus for a long time. Now there is Nib http://visionmedia.github.com/nib/ but it's still a pretty young project compared to Compass. Btw: For those who do a lot of Rails + Node.js development check out https://github.com/9elements/haml-coffee it's HAML married with CoffeeScript. Performance and scalability I buy the performance, kudos to the V8 team and @ryah. But scalability does not come from using a certain tech (unless it embraces scalability per default). Scalability comes from crafting a system that has no single point of failure (http://en.wikipedia.org/wiki/Single_Point_of_Failure). So please don't compare apples to pines. Wealth of hosting options: No.de, Joyent’s SmartMachine, Heroku, Nodejitsu True, I would just add homebrew hosting and deployment with capistrano and forever: https://github.com/nodejitsu/forever Make your developers famous Don't be foolish. Doing Open Source (right) is one of the hardest disciplines out there. Just releasing some written code into a new ecosystem does not automatically uplift you to the rockstar developer olymp. You have to maintain your code, deal with issues, deliver support etc... Doing Open Source work is very important. You take - you give - but more important you'll learn. But you don't need node for that there is plenty of room in this Internetz thingy, look at https://github.com/codejoust/session.js Developer happiness I know the feeling: Staying on the bleeding edge looking into the space where no man has gone before feels great. But be carefull, if things don't go well they can easily switch to developer tears. It almost took the node ecosystem a year to mimic typical "getting things done modules" like EveryAuth https://github.com/bnoguchi/everyauth which derives from https://github.com/intridea/omniauth/ in the rails world. OH: If you seeking for something like rails in the node.js world... then just use rails. Bottom Line When you read this you may get the feeling that I don't like node - I'm loving node http://node.9elements.com/ and it definitely has it's use cases: - if you do something in realtime - if you are developing an API - if you need high performance but for other use cases I wouldn't bet my life on it... yet. If you're interested in node, then go for it, play with it, never stop exploring - start small and grow with the ecosystem. One day it may replaces technology X with framework Y, but until then I would lower my expectations a little. So... enough ranting, let's engage the discussion - I hope you enjoyed this article: http://twitter.com/sippndipp
4 points · Open discussion
Cool! I use a version of haml-js that's been modified to work well in the browser. (https://github.com/wintondeshong/haml-js). Jammit allowed me to set the template function as Haml and it just worked, by passing the content of the jst files to the Haml() function. Is there an equivalent in sprockets? UPDATE: As much as I like Haml, I think I'll just switch to eco, since it seems better integrated for now, and... CoffeeScript! Now all I need is haml-coffeescript / eco-haml. Well it turns out this does exist: https://github.com/9elements/haml-coffee. But I don't know how much work I'd need to do to get it working with the sprockets asset pipeline?
In Sam Stephenson on Pow, CoffeeScript, and the Rails 3.1 Asset Pipeline

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.