Live data from Hacker News

Show HN: Vuido builds desktop apps using Vue.js without Electron

forum.vuejs.org

71–80 of 117 posts

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#71
post #23

Earlier quoted context omitted.

> Great stuff Like what? A chat client that uses 1+ GB of RAM and melts batteries faster than a flamethrower? No thanks! It almost looks like this Electron/JS trend was started by CPU manufacturers who realised that current CPUs have more than enough power for everyday tasks, and needed a way to create demand for even faster CPUs. I’d say Electron (and JS in general) was pretty effective at that.

> manufacturers who realised that current CPUs have more than enough power for everyday tasks, and needed a way to create demand for even faster CPUs Lol. It's a common trend across software. Try comparing office 2003 to office 2013. Office 2003 starts instantly on a modern desktop and uses minimal RAM. Office 2013 takes a good four or five seconds to fire up and uses a few hundred mb memory. And they both do exactly…

> It's a common trend across software.

Not at this scale though. Office 2013 uses maybe 2x or 3x the amount of RAM compared to Office 2003.

A chat client like Slack routinely uses up to 1GB while a native equivalent would use 100MB or less. We’re talking about a 10x increase here - that’s unacceptable.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#72
post #40

Earlier quoted context omitted.

Attendance to hackathons deserves mocking in its own... :)

Can you please explain why? Genuinely curious.

The first two bad things that come to mind: squeezing free time from developers and making hype out of it for peer pressure.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#73
post #71

Earlier quoted context omitted.

> manufacturers who realised that current CPUs have more than enough power for everyday tasks, and needed a way to create demand for even faster CPUs Lol. It's a common trend across software. Try comparing office 2003 to office 2013. Office 2003 starts instantly on a modern desktop and uses minimal RAM. Office 2013 takes a good four or five seconds to fire up and uses a few hundred mb memory. And they both do exactly…

> It's a common trend across software. Not at this scale though. Office 2013 uses maybe 2x or 3x the amount of RAM compared to Office 2003. A chat client like Slack routinely uses up to 1GB while a native equivalent would use 100MB or less. We’re talking about a 10x increase here - that’s unacceptable.

Have you sources for this 10x claim? Do you actually have a native slack client that uses 100mb because I'd love to see it.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#74

So to me, the issue with Electron is that I'm already running Chrome, so I should be able to take advantage of that. In particular, if I have N electron apps, I want 1 Chrome running. I don't want to run certain applications inside the browser, I want the separate app icon, etc. Is there anything that is being done in Chrome/FF to support that kind of thing? That way it's up to the site consumer's preference how they…

Yes, PWAs. That is how it should be.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#75

This is a cool project, although I'm starting to not like the look of native apps anymore. This will hopefully appease the electron haters but I suspect someone will still complain about this being JavaScript

> I'm starting to not like the look of native apps anymore. Can you please explain why? On which platform, specifically?

Speaking just for myself...I like that Slack has the same look and feel no matter what platform I bring it up on. I prefer a unified cross-platform experience over a unified platform experience. I want my OS to disappear. I am probably biased by regularly targeting multi platform myself.

This causes me to favor other lowest common denominator idioms as well, like python 2.7 over 3, unconfigured vim, bash on windows, etc. When this isn’t possible, I favor technologies that allow me to synchronize configurations across platforms quickly and easily.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#76
I think the coolest thing about this is that it's using libui [1], so whether you're trying to work on Proton Native, or Vuido, or any other flavor of NodeJS-to-Native-GUI [2], we'll hopefully end up contributing to a single library. (PS: libui has bindings to other languages as well [3]!)

[1] https://github.com/andlabs/libui

[2] https://github.com/parro-it/libui-node

[3] https://github.com/andlabs/libui#language-bindings

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#77

It's a good shift away from the crap that is Electron.js but once we are using a native toolkit, why not use a native language too? ;-)

I think the whole 'hot-module-reloading' thing is pretty compelling, but its possible to do apart from a JS environment (see flutter for instance). The library that Vuido runs on, libui, has bindings to all kinds of languages:

https://github.com/andlabs/libui#language-bindings

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#79
post #76

I think the coolest thing about this is that it's using libui [1], so whether you're trying to work on Proton Native, or Vuido, or any other flavor of NodeJS-to-Native-GUI [2], we'll hopefully end up contributing to a single library. (PS: libui has bindings to other languages as well [3]!) [1] https://github.com/andlabs/libui [2] https://github.com/parro-it/libui-node [3] https://github.com/andlabs/libui#language-bin…

Yes, libui is starting to look quite interesting.

Re: Show HN: Vuido builds desktop apps using Vue.js without Electron

#80
post #71

Earlier quoted context omitted.

> It's a common trend across software. Not at this scale though. Office 2013 uses maybe 2x or 3x the amount of RAM compared to Office 2003. A chat client like Slack routinely uses up to 1GB while a native equivalent would use 100MB or less. We’re talking about a 10x increase here - that’s unacceptable.

Have you sources for this 10x claim? Do you actually have a native slack client that uses 100mb because I'd love to see it.

Slack is essentially fancy IRC, so we can take any IRC client as a baseline for how much RAM it should really use.

Let’s take HexChat (https://hexchat.github.io/) for example - it does most of what Slack does, plus has advanced features not available on Slack like a Lua, Python & Perl plug-in API. It used less than 100MB or RAM after running for days on a Linux machine.

Slack is usually well into the GB of RAM after running for a few days.

Post reply on HN