Voiden: Released the Voiden Runner so that users can test APIs directly in the terminal. https://github.com/VoidenHQ/voiden

ApyHub: https://apyhub.com/ working to onboard a few more API providers. Working to rationalize the terms for new APIs added in the catalog.

I am also working to streamline how all APIs are certified and monitored.

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 usage 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,

Comments URL: https://news.ycombinator.com/item?id=48020838

Points: 1

# Comments: 2

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

Problem now is that most of the alternatives out there (including the ones you mentioned) do offer some great things but essentially they feel variations of the same concepts - so I see them as "Enshittification on the way". Reason we built voiden is that we wanted something that challenges these ideas. You can try it out and let me know if it resonates: https://github.com/VoidenHQ/voiden.

apologies for the slight promo - but based on your comment I thought it might be relevant.

https://voiden.md/changelog

Today I released the community plugins for Voiden.

This is a big one because one of the things I dont want is the API tool to become bloated with new features - so I want to allow anyone to build plugins to grow the tool.

docs: https://docs.voiden.md/docs/plugins/build-a-plugin

Typing out a few hundred lines of code was never the real bottleneck. What was expensive was everything around it: making it correct, making it maintainable (often underestimated), coordinating across teams and supporting it long term.

You can also overshoot: Testing every possible path, validating across every platform, or routing every change through layers of organizational approval can multiply costs quickly. At some point, process (not code) becomes the dominant expense.

What LLMs clearly reduce is the short-term cost of producing working code. That part is dramatically cheaper.

The long-term effect is less clear. If we generate more code, faster, does that reduce cost or just increase the surface area we need to maintain, test, secure, and reason about later?

Historically, most of software’s cost has lived in maintenance and coordination, not in keystrokes. It will take real longitudinal data to see whether LLMs meaningfully change that, or just shift where the cost shows up.

We recently started working on a tool called Voiden and wanted to share it here to get your thoughts and feedback.

Over the years, we found ourselves managing way too many tools just to work with APIs: one for api specs, another for docs, a third for tests, etc etc. Eventually it starts to feel more like a performance than actual work.

So we built Voiden: A git-native, extensible, and lightweight client that brings everything—specs, docs, tests, mocks—into one place. No bloat, no lock-in, no "platform overhead." Just structured API workflows that don’t fight your tools or your team.

A few things we care about:

-Reusability and composability : APIs as building blocks, not silos.

-Structure over scatter : everything lives together in one workspace.

-No sign-in required : you can use it without creating an account.

Free and open — we are building this with the community in mind.

Just to be clear: The goal is NOT to replace OpenAPI, but to provide a layer around existing specs that feels coherent, hackable, and friendly to real-world dev workflows.

You can check it out here: https://voiden.md/

And if you have feedback, suggestions, or just want to follow along:

https://github.com/VoidenHQ/feedback

We are still early, but would love to hear what you think—what you like, what is missing. Appreciate any time you take to try it out.

Nikolas

Comments URL: https://news.ycombinator.com/item?id=43961565

Points: 6

# Comments: 0