5 ms·

> you have no excuses! > It is in early stage of development > OSX should work too, but it's not tested. > Windows has yet to be configured in build scripts

> you have no excuses! > It is in early stage of development > OSX should work too, but it's not tested. > Windows has yet to be configured in build scripts, but it will be supported in further releases. > There are very few tests developed > This is not yet battle-tested in a real app All that from the official Readme [0] and you're saying there's no reason not to use it? [0] https://github.com/parro-it/libui-node https://github.com/parro-it/libui-node

nikolay 10y ago
This is just one of the wrappers around libui [0], which itself works fine, and is tested on all platforms. Well, it's in alpha stage, true, but so what - wait until it's stable, and then start building? [0]: https://github.com/andlabs/libui https://github.com/andlabs/libui
- ohitsdom 10y ago
  You're criticizing a released project for their technology choice, advocating that they should have waited to build it until some other tech was ready... Maybe take a step back and just appreciate that they built and shipped something. If you hate Electron, move on and don't use it.
  - nikolay 10y ago
    Did you care to read? I meant they should not wait. Electron uses gigabytes of RAM - it's the one reason I switched to weechat from Slack's "desktop" client! Such "desktop" apps are a disgrace and they run way more efficiently in the browser compared to having multiple copies of browsers running in parallel.
    - ohitsdom 10y ago
      Slack is currently using 144 MB on my Windows machine (with a lot of public channels and DMs active). Electron may give up some performance for a lower development effort, but that's the known trade-off. I think you're making it sound a little more bleak than it actually is, current performance of Electron apps is pretty good (if designed properly).
      - nikolay 10y ago
        Send me a screenshot and make sure it includes virtual memory as well. I've never had any embeded browser app to use less than a GB of overall memory (in most cases, Slack uses well over 2GB).

nikolay 10y ago

This is just one of the wrappers around libui [0], which itself works fine, and is tested on all platforms. Well, it's in alpha stage, true, but so what - wait until it's stable, and then start building? [0]: https://github.com/andlabs/libui https://github.com/andlabs/libui

ohitsdom 10y ago
You're criticizing a released project for their technology choice, advocating that they should have waited to build it until some other tech was ready... Maybe take a step back and just appreciate that they built and shipped something. If you hate Electron, move on and don't use it.
- nikolay 10y ago
  Did you care to read? I meant they should not wait. Electron uses gigabytes of RAM - it's the one reason I switched to weechat from Slack's "desktop" client! Such "desktop" apps are a disgrace and they run way more efficiently in the browser compared to having multiple copies of browsers running in parallel.
  - ohitsdom 10y ago
    Slack is currently using 144 MB on my Windows machine (with a lot of public channels and DMs active). Electron may give up some performance for a lower development effort, but that's the known trade-off. I think you're making it sound a little more bleak than it actually is, current performance of Electron apps is pretty good (if designed properly).
    - nikolay 10y ago
      Send me a screenshot and make sure it includes virtual memory as well. I've never had any embeded browser app to use less than a GB of overall memory (in most cases, Slack uses well over 2GB).