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's what we were doing: the app loaded its JavaScript bundle, unpacked it, then made the API calls needed to fetch data.
Just curious, what sort of API calls it make at boot time? What data you fetch?
I mean yes the use of electron is definitely a bad thing in terms of cold-start time and memory at idle
could be done more efficiently with things like tauri
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
have you ever worked with tauri? it's a nightmare on mac. dont even ASK about linux