tower

UNMAINTAINED - Small components for building apps, manipulating data, and automating a distributed infrastructure.

4Distinct people

5Mentions

0Explicit recommenders

1.8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

UNMAINTAINED - Small components for building apps, manipulating data, and automating a distributed infrastructure.

GitHub

No documented product use has been verified yet.

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.

No other repository is repeatedly linked in the same discussions.

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

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

HN mentions by week5 dated mentions

Observed mentions: 2012-02-27 18:42:07 UTC to 2012-07-26 20:55:22 UTC. Weeks start Monday, 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

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Feb 27	2012-02-27 00:00:00 UTC	2012-03-05 00:00:00 UTC	3	0	3
Mar 5	2012-03-05 00:00:00 UTC	2012-03-12 00:00:00 UTC	0	0	0
Mar 12	2012-03-12 00:00:00 UTC	2012-03-19 00:00:00 UTC	0	0	0
Mar 19	2012-03-19 00:00:00 UTC	2012-03-26 00:00:00 UTC	0	0	0
Mar 26	2012-03-26 00:00:00 UTC	2012-04-02 00:00:00 UTC	0	0	0
Apr 2	2012-04-02 00:00:00 UTC	2012-04-09 00:00:00 UTC	0	0	0
Apr 9	2012-04-09 00:00:00 UTC	2012-04-16 00:00:00 UTC	0	0	0
Apr 16	2012-04-16 00:00:00 UTC	2012-04-23 00:00:00 UTC	0	0	0
Apr 23	2012-04-23 00:00:00 UTC	2012-04-30 00:00:00 UTC	0	0	0
Apr 30	2012-04-30 00:00:00 UTC	2012-05-07 00:00:00 UTC	0	0	0
May 7	2012-05-07 00:00:00 UTC	2012-05-14 00:00:00 UTC	0	0	0
May 14	2012-05-14 00:00:00 UTC	2012-05-21 00:00:00 UTC	0	0	0
May 21	2012-05-21 00:00:00 UTC	2012-05-28 00:00:00 UTC	0	0	0
May 28	2012-05-28 00:00:00 UTC	2012-06-04 00:00:00 UTC	0	0	0
Jun 4	2012-06-04 00:00:00 UTC	2012-06-11 00:00:00 UTC	0	0	0
Jun 11	2012-06-11 00:00:00 UTC	2012-06-18 00:00:00 UTC	0	0	0
Jun 18	2012-06-18 00:00:00 UTC	2012-06-25 00:00:00 UTC	0	0	0
Jun 25	2012-06-25 00:00:00 UTC	2012-07-02 00:00:00 UTC	0	0	0
Jul 2	2012-07-02 00:00:00 UTC	2012-07-09 00:00:00 UTC	0	0	0
Jul 9	2012-07-09 00:00:00 UTC	2012-07-16 00:00:00 UTC	0	0	0
Jul 16	2012-07-16 00:00:00 UTC	2012-07-23 00:00:00 UTC	0	0	0
Jul 23	2012-07-23 00:00:00 UTC	2012-07-30 00:00:00 UTC	2	1	1

5 sources

To see it formatted nicely, but in line with the rest of the readme, see: https://github.com/viatropos/tower/tree/development

So, with something like Tower.js the code is written in coffee to start with (https://github.com/viatropos/tower/tree/master/src), but in the repo (and in npm) you'll actually get the resulting JavaScript as well (https://github.com/viatropos/tower/tree/master/lib and https://github.com/viatropos/tower/tree/master/dist). This is generally true of most CS projects. I can't speak specifically to whether or not you can use Tower.js without coffee, just saying don't discount a project because the author wrote it in CS. Spine.js (http://spinejs.com) is a great example of what I'm talking about.

Why don't you put the link to the source code[1] on the website? I have to actually search it via google. [1] https://github.com/viatropos/tower