HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nim-lang
nimforum
Nim2016–2023
nim-lang / nimforum

nimforum

Lightweight alternative to Discourse written in Nim

13Distinct people
27Mentions
0Explicit recommenders
787GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Lightweight alternative to Discourse written in Nim

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 year27 dated mentions

Observed mentions: 2016-01-09 12:57:27 UTC to 2023-02-06 13:44:41 UTC.

024682016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

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
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC826
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC514
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

27 sources
Open source Vanilla seems to not be doing well: https://open.vanillaforums.com/discussion/39204/where-do-we-.... It's a shame. I thought it had a nice UI: mobile-friendly, not very flashy, around 300K per page (less if assets are cached), rendered on the server. I wanted to migrate my FluxBB forum to Vanilla, since FluxBB is effectively discontinued in favor of Flarum. If I migrate my forum now, it will probably be to Flarum. https://www.unitedbsd.com/ runs it, and I seem to like the experience of browsing it more than Discourse forums (edit: but I still prefer paginated forums without infinite scrolling). It also helps that Flarum has lower system requirements than Discourse. The forum migration tool https://github.com/linc/nitro-porter targets both Vanilla and Flarum, though I haven't actually attempted a migration with it, so I don't k
Read the rest
now how useful it really is. I rejected NodeBB because MongoDB is no longer developed under a free license. I'll list some other forum software I have considered in case you find it useful: Fossil Forums (https://fossil-scm.org/home/doc/trunk/www/forum.wiki), nimforum (https://github.com/nim-lang/nimforum), Talkyard (https://github.com/debiki/talkyard), Misago (https://github.com/rafalp/Misago), FlaskBB (https://github.com/flaskbb/flaskbb). All of these have less momentum behind them than Flarum. Most are lightweight. I found it very appropriate that nimforum's name is inconsistently capitalized. :-) I am still kind of amazed that Fossil has integrated a forum and a chatroom. During my research I also found an interesting fork of SMF: https://github.com/elkarte/Elkarte.
In PhpBB 3.3.10
I don’t know about other web-guides. Nim’s official website is made with Nim and available at Github[0], but it has become at bit more complicated after they switched to Karax[1]. Jester’s tests gives a good view on the routing procedures[2]. The official tutorials[3] are pretty good, when you get the grab on how to ”decode” them. For web development with websockets and microservices I would suggest you to have a look at the Redis package[4], and @treeform’s Websocket[5] and JsonParsing-packet[6]. [0] https://github.com/nim-lang/nimforum/ [1] https://github.com/karaxnim/karax [2] https://github.com/dom96/jester/blob/master/tests/alltest.ni... [3] https://nim-lang.org/docs/tut1.html [4] https://github.com/nim-lang/redis [5] https://github.com/treeform/ws [6] https://github.com/treeform/jsony
In Set up a website with Nim (2019)
Oh, thought you were same poster. Well, that other person mentioned it in a context which doesn't appear to be related to systems programming. Just checked Github for some of the top Nim projects. Forum software: https://github.com/nim-lang/nimforum/search?q=nil&unscoped_q... Web framework: https://github.com/planety/prologue/search?q=nil&unscoped_q=... Twitter front-end: https://github.com/zedeus/nitter/search?q=nil&type=Code These uses of "nil" don't appear to have anything to do with systems programming.
In NimConf 2020 Videos
I have used Nim extensively and done a lot of metaprogramming in it. The biggest risk to metaprogramming is that it allows crazy syntax that you have to learn separately. Nim does very well here to enforce limitations which work well in reducing this risk. Comparing Nim's metaprogramming to Rust's shows what I mean. In Rust you can write macros that act on token streams, so as long as the token stream is valid it can be used. This allows libraries like the typed-html package[1]. In Nim you cannot do this unless you put the HTML in a string literal. This limitation created a syntax that is far more idiomatic, admittedly at the expense of familiarity for users of HTML: buildHTML(): html(): head(): title: text "My webpage" body: p(class="red"): text "Hello World" In my experience this works quite we
Read the rest
ll, you can see a larger example in our Forum's code which is written using a SPA framework called Karax[2]. Please don't let style insensitivity discourage you from using this wonderful language. 1 - https://docs.rs/typed-html/0.2.0/typed_html/ 2 - https://github.com/nim-lang/nimforum/blob/master/src/fronten...
In Ask HN: What metaprogrammable language do you/would like to use?

Showing the 15 most recent of 27 sources. Enable JavaScript to search and browse every indexed mention.

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.