STstevewilhelm·Oct 31, 2013Submission
Generic interface to multiple Ruby template engines
2 points · Open discussionrtomayko
tilt
Ruby2011–2013
rtomayko / tilt
tilt
Generic interface to multiple Ruby template engines
4Distinct people
4Mentions
0Explicit recommenders
1.9KGitHub stars
What to know before exploring
What it is
Generic interface to multiple Ruby template engines
GitHub
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 year4 dated mentions
Observed mentions: 2011-02-05 13:01:42 UTC to 2013-10-31 07:00:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
4 sourcesIt's pretty easy for language authors to integrate with Sprockets in Ruby on Rails. They just need to write an interface for Tilt (http://github.com/rtomayko/tilt) . Though that interface needs to be written in Ruby, not JS.
In RedScript – like CoffeeScript, in Ruby#113: Hi We cleaned up your code for you by GunioRobot
4 points · Open discussionWhat I find most annoying is that in GitHub's world, a pull request is an issue (e.g. see here: https://github.com/rtomayko/tilt/issues). That's totally backwards to me. A pull request is a solution to an issue.
This workflow is natural to me:
1. Someone reports an issue
2. A patch is provided
If you follow this workflow today, you'll end up with two issues in the issue tracker. Confusing! It should be one issue and one fix for that issue.
And if someone sends a pull request (without opening a ticket first), what should I do if I agree with the feature/bugfix, but not with the way it was solved? The issue isn't fixed yet, so it's wrong to close it, but it feels weird to keep the pull request open (since I've actually rejected it). I want to close the pull request only!
In Pull requests are not conversations