4 ms·
Thanks for your input. What you are saying is correct. But basically this project was done to create application using electron, that would actually serve a pur
by edanchenkov 9y ago
Thanks for your input. What you are saying is correct. But basically this project was done to create application using electron, that would actually serve a purpose and be usable.
Also, I think due to nature of MenuTube, it is not consuming lots of memory, especailly compare to some other electron apps :) Don't think it is big overhead in this case.
- Klonoar 9y agoYour logic... makes no sense, I'm sorry. WKWebview would be just as usable. Furthermore, running an entire extra instance of Chrome for a menubar app when you could simply use the built-in Webkit instance is really not cool.
- edanchenkov 9y agoNo worries :) What does exactly makes no sense? Using WKWebview would be much more optimal, it is clear. But I stated specifically that I wanted to try electron. I didn't try to make it perfect. And again, if using chrome instead of WKWebview, does not make sense. Then for what kind of applications would you pick Electron? And how do you measure the line where choosing electron is an overkill that takes to much resources?
- Klonoar 9y agoYou might pick Electron if this was something that'd run on every platform, but this is macOS specific, so using Electron instead of WKWebView just seems really lazy at the cost of system resources for the end user.