HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
VoidenHQ
voiden
TypeScript2025–2026
VoidenHQ / voiden

voiden

Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.

4Distinct people
25Mentions
1Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.

GitHub

Where it is used

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

What people are saying

I love how you have used markdown here ! We kind of have used the exact philosophy in https://voiden.md/ - offline-first, file based and support for git. This is exactly the…

dhruv3006 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM 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 month25 dated mentions

Observed mentions: 2025-05-12 10:42:44 UTC to 2026-10-02 12:52:30 UTC.

024682025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

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
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC110
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC101
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC817
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC303
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC413
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC404
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

4 sources
Hello, Wanted to get some opinions from folks here that have actually built and shipped with Electron. Background: Building an API IDE on Electron. Designing this to not be “just an API client”or a thin wrapper around a webapp. It’s a pretty original desktop tool with a lot of editor/IDE-like behavior: local workflows, richer interactions, and some things that I think would have been much harder to build and maintain in a more constrained setup. So yeah, thats why we went for Electron. this is the tool: github.com/voidenhq/voiden :) Now, as adoption is growing, we are starting to get the usual questions about memory footprint and app size. The (slightly) frustrating part is that when the app is actually being used, the app-side memory is often pretty reasonable. In many normal cases we are seeing something like 50–60 MB for the actual usa
Read the rest
ge we care about (even added it in the app itself for people to check it out). But then people open Activity Monitor, see all the Chromium/Electron-related processes, and the conversation immediately becomes: “yeah but Tauri would use way less” And then, without realizing, I suddenly end up talking and philosophizing about Electron, instead of discussing the tool itself (which is what I am passionate about :) Of course Electron also has overhead. Pretending otherwise would be foolish. So we are constantly optimizing what we can, and we will keep doing so… At the same time, I do feel that a lot of these comparisons feel weirdly flattened. For example people often compare: full Electron process footprint VS the smallest possible Tauri/native mental model …without always accounting for development speed, cross-platform consistency, ecosystem maturity, plugin/runtime complexity, UI flexibility, and the fact that some apps are doing much more than others. Which is by the way the reason that we went with Electron. So all this context to get to my real question, which is: How do you explain this tradeoff to users in a way that feels honest and understandable, without sounding like you are making excuses for Electron? And also, for those of you who have had this conversation a hundred times already: What do you say when people reduce the whole discussion to “Electron bad, Tauri good”? Have you found a good way to explain footprint in practical terms? Mostly trying to learn how others think about this , especially those who have built more serious desktop products and had to answer these questions in the wild. Would love your thoughts and advice,
In How do you defend electron in the memory footprint discussion?
built and open sourced a postman alternative, and decided to do it on Electron. what has been funny is indeed when having to "defend" electron when it comes to memory footprint etc. One thing that I always thought was interesting is that people make the argument by comparing the full Electron process footprint VS the smallest possible Tauri/native mental model and all without thinking about all the advantages of electron like development speed, cross platform consistency etc. we have now optimized it a lot and we even show the actual usage inside the app for folks to monitor. here is the repo in case you wanna have a look: https://github.com/VoidenHQ/voiden
In Making Postman load 60% Faster

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.