HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
KirinDave
fuzed
Erlang2008–2017
KirinDave / fuzed

fuzed

A new revision of Fuzed, the Erlang-based frontend for web apps. Check out the mailing list at http://groups.google.com/group/fuzed

5Distinct people
8Mentions
0Explicit recommenders
276GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A new revision of Fuzed, the Erlang-based frontend for web apps. Check out the mailing list at http://groups.google.com/group/fuzed

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:24:48 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 year8 dated mentions

Observed mentions: 2008-04-23 20:21:11 UTC to 2017-04-03 03:41:09 UTC.

0123452008-01-01 00:00:00 UTC to 2009-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20082009-01-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-01-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 2013-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017

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
20082008-01-01 00:00:00 UTC2009-01-01 00:00:00 UTC514
20092009-01-01 00:00:00 UTC2010-01-01 00:00:00 UTC110
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC101
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC000
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC000
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101

What Hacker News says

1 sources
So, in the interest of full discloser Dave, let's make sure everyone knows you named a web server after me: http://github.com/KirinDave/fuzed You and TPW named it "F U Zed" which to me is damn rude. Based on that, I believe everyone should discount your opinion just from your obvious bias against me personally, but let's review what I actually did anyway. First, I've got a decent laptop that's got 4 CPU cores and does pretty good running multiple processes. I think it'd hold up well enough for a few simple tests to make sure I didn't break anything. If you had read the blog post, I made this clear in numerous places, but obviously you didn't read the whole thing (or you're hoping other people have not read the whole thing). Next, since I'm just testing the code to make sure I didn't break it, I just need to slam an older version and a n
Read the rest
ewer version. Since they'll be tested in the same way, it should give me enough data to know. Even though there could be contention on the machine, with 4 cores it should be good enough to figure out if I screwed something up. Additionally, Mongrel2 does aggressive caching of files, so I'm really narrowing it down to just the poll code by hitting a small file. All that combined with doing multiple runs and looking at the performance between them and for an evening of testing I've done enough to make sure it's not broken. That's it. I'm pretty damn sure you did that when testing your "Homage To Zed named FU" but hey, gotta hold the people you dislike to higher standards then yourself right? Now, when I get Mongrel2 to a state where it's a real web server, that I actually wrote, rather than stole from Yaws and claimed I wrote, I'll let you know. I'll make sure to setup a massive EC2 cluster and test all the possible permutations a guy like you thinks are necessary to prove that it actually serves files. Until then, this will do just fine to make sure that I'm not breaking anything.
In Mongrel2 Superpoll Experiment Step 1

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.