HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jacksonh
manos
C#2010–2012
jacksonh / manos

manos

Manos is an easy to use, easy to test, high performance web application framework that stays out of your way and makes your life ridiculously simple.

5Distinct people
7Mentions
0Explicit recommenders
453GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Manos is an easy to use, easy to test, high performance web application framework that stays out of your way and makes your life ridiculously simple.

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:56:07 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 month7 dated mentions

Observed mentions: 2010-10-07 01:35:30 UTC to 2012-10-11 12:52:26 UTC.

01232010-10-01 00:00:00 UTC to 2010-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 20102010-11-01 00:00:00 UTC to 2010-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2010-12-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2011-01-01 00:00:00 UTC to 2011-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-01 00:00:00 UTC to 2011-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-03-01 00:00:00 UTC to 2011-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-04-01 00:00:00 UTC to 2011-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-05-01 00:00:00 UTC to 2011-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-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): 0 mentions; 0 submissions, 0 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 comments2011-10-01 00:00:00 UTC to 2011-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 20112011-11-01 00:00:00 UTC to 2011-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-01-01 00:00:00 UTC to 2012-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-02-01 00:00:00 UTC to 2012-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-03-01 00:00:00 UTC to 2012-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2012-04-01 00:00:00 UTC to 2012-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-05-01 00:00:00 UTC to 2012-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-06-01 00:00:00 UTC to 2012-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-07-01 00:00:00 UTC to 2012-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-08-01 00:00:00 UTC to 2012-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-09-01 00:00:00 UTC to 2012-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-10-01 00:00:00 UTC to 2012-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 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
Oct 20102010-10-01 00:00:00 UTC2010-11-01 00:00:00 UTC101
Nov 20102010-11-01 00:00:00 UTC2010-12-01 00:00:00 UTC101
Dec 20102010-12-01 00:00:00 UTC2011-01-01 00:00:00 UTC303
Jan 20112011-01-01 00:00:00 UTC2011-02-01 00:00:00 UTC000
Feb 20112011-02-01 00:00:00 UTC2011-03-01 00:00:00 UTC000
Mar 20112011-03-01 00:00:00 UTC2011-04-01 00:00:00 UTC000
Apr 20112011-04-01 00:00:00 UTC2011-05-01 00:00:00 UTC000
May 20112011-05-01 00:00:00 UTC2011-06-01 00:00:00 UTC000
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 UTC000
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 UTC000
Dec 20112011-12-01 00:00:00 UTC2012-01-01 00:00:00 UTC000
Jan 20122012-01-01 00:00:00 UTC2012-02-01 00:00:00 UTC000
Feb 20122012-02-01 00:00:00 UTC2012-03-01 00:00:00 UTC000
Mar 20122012-03-01 00:00:00 UTC2012-04-01 00:00:00 UTC101
Apr 20122012-04-01 00:00:00 UTC2012-05-01 00:00:00 UTC000
May 20122012-05-01 00:00:00 UTC2012-06-01 00:00:00 UTC000
Jun 20122012-06-01 00:00:00 UTC2012-07-01 00:00:00 UTC000
Jul 20122012-07-01 00:00:00 UTC2012-08-01 00:00:00 UTC000
Aug 20122012-08-01 00:00:00 UTC2012-09-01 00:00:00 UTC000
Sep 20122012-09-01 00:00:00 UTC2012-10-01 00:00:00 UTC000
Oct 20122012-10-01 00:00:00 UTC2012-11-01 00:00:00 UTC101

What Hacker News says

7 sources
That's a pretty fair question. In my opinion, the only reason to go with ASP.NET anything is if you already know C# (or any other .Net language). Otherwise, Rails, Django, Flask, Cake, etc are going to be significantly easier to get up to speed with, have better communities, have less murky IP situations and are generally going to be less expensive to develop for and to hire developers for. There are advantages to the CLR world - Tooling is top notch (Mono's tools are lacking right now but seem to be improving quickly), there is a reasonable amount of documentation, even though some of it is of questionable quality. C# performs well, both on Mono and .Net. There are many libraries available (although the quality of the libraries can sometimes be lacking). Many of the higher quality libraries are closed-source commercial libraries. Some of
Read the rest
the worst ones are also closed-source commercial packages, so it pays to do research prior to purchasing anything. The community has been warming to open source - in my opinion this is largely due to the efforts of Miguel de Icaza and everyone working on the Mono Project. (As an aside, if you don't like asp but you do like C#, you should consider checking out and contributing to Manos de Mono, a Mono based web framework which is still in its infancy - https://github.com/jacksonh/manos .) Microsoft is, and always will be a for-profit company that makes money from selling its software. It has a vested interest in creating platform lock-in, but developers don't have to stick to the Microsoft way of doing things if they choose not to, thanks to the strength of Mono today. Either way, Microsoft is pretty up-front about what the cost of doing business is with them; and they have proven to be pretty consistent with their pricing. Politics and profits aside, C# is an enjoyable language to use. I haven't spent time with F# yet, but I understand it's quite enjoyable as well. The C# team has done an excellent job of paying attention to programming trends and adopting techniques from other languages. The transition from 1.1 to 2.0 was kind of clunky, but since then they've shown a great deal of good taste in what they've implemented as well as how it's been implemented. Of course, the downside is that C# is a large and complex language. I think the most recent "C# in Nutshell" book is well over a thousand pages. I have production code deployed in Python, PHP and Clojure, but I'm currently migrating back to .Net for my personal projects. C# developers get an excellent cross-platform deployment story thanks to Mono (MonoTouch, MonoDroid, MonoMac). Honestly, I think Mono runs on pretty much everything from PC, Mac & Linux to WP7, iPhone and Android; as well as game consoles, embedded hardware, etc. Additionally, many of the new to .Net technologies coming out of Microsoft right now such as F#, C# 5's async framework, MVC3 and Entity Framework 4 are very compelling. Microsoft is kind of a dorky company, but in my opinion they are producing pretty good software right now.
In ASP.NET MVC 3 Release Candidate
Here is the "official" compatibility chart: http://www.mono-project.com/Compatibility The chart is based on 2.6, the stuff that was added today falls under the "Current Mono Trunk" section. I'm not sure if the DLR (dynamic language runtime) is fully functional on Mono yet. The DLR is what's used to make IronPython and IronRuby run on the .Net stack. It's embedded into Silverlight, which allows developers to run Python and Ruby in the browser (assuming their users have the Silverlight plugin). Mono has Moonlight, but again, I'm not sure if the DLR is in there. I personally see C# as an evolutionary next step from Java. That being said, languages like Scala, Clojure, JRuby (which I guess is technically a language implementation) let you get the benefits of Java without all the sucky language parts. C# is a solid server-side language. I'm no
Read the rest
t terribly impressed with it for the web, although MVC makes it much better than it used to be (blah, webforms). There's an interesting project that was posted here recently called "Manos de Mono" that offers some variety in the web space [1] It's also turned out to be a pretty decent mobile development language. You can develop iPhone and Android apps using Mono [2][3], as well as cross-platform games [4][5]. You can use Mono in client-side applications, but I'm not sure how well it works or everything that's involved with using it that way. One of the nice things about Mono is that it lets you write C# on Unix and Unix-like platforms. For those of us that use C# during the day, it's liberating to be able to use the same language on our Macs at home, or deployed on Linux servers next to our other software. [1] http://github.com/jacksonh/manos [2] http://monotouch.net/ [3] http://monodroid.net/ [4] http://code.google.com/p/monoxna/ [5] http://unity3d.com/
In Mono 2.8 has been released

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.