为什么 Voiden 选择 Electron？
Voiden 团队选择 Electron 作为其开发框架并非轻率之举，而是经过深思熟虑的结果。
他们认为 Electron 带来的权衡取舍在构建 Voiden 这类 API 开发 IDE 时是合理的，能够保证跨 macOS、Windows 和 Linux 平台的稳定性和一致性。
虽然 Electron 框架有时会被批评为体积庞大，但 Voiden 团队认为很多负面评价源于产品设计不佳，而非框架本身的问题。
他们更注重平台的成熟度、兼容性和可靠性，并承诺保持透明度，让用户了解应用的资源占用情况并积极优化。
Electron 允许开发者结合 Web 技术和原生代码，从而提供更灵活的开发方式，Voiden 团队认为这非常符合产品的需求。
查看原文开头（英文 · 仅前 3 段）
We chose Electron for Voiden very intentionally.
Not because footprint does not matter. It does. And not because Electron is free of tradeoffs. It is not. But based on the discussions we have had with the community, one line stuck with us: too much of this debate is often about “vibes, not reality.” The real question is not whether a framework has tradeoffs. Every framework does. The real question is whether those tradeoffs make sense for the kind of product you are trying to build.
For us, Voiden is not just a wrapper around a webpage, and not just another form based API client. We are building something much closer to an IDE for APIs with richer editing, local workflows, desktop behavior, extensibility, and a broader product surface than a simple request sender. That pushed us toward a stack that let us move fast, build deeply customized interfaces, and ship consistently across macOS, Windows, and Linux.
※ 出于版权考虑，仅引用前 3 段。完整内容请阅读原文。