Live data from Hacker News

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

forum.vuejs.org

111–117 of 117 posts

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

#111
post #104

Earlier quoted context omitted.

I think you're failing to include the firefox memory usage in that second example. the 200+MB memory of electron is because it includes the browser. Your 8MB file also needs firefox to run, so in a naked desktop environment the user first has to spin up 170MB+ of firefox before they can run your 8MB app.

But you do not need to have five full Firefox's running for using five web-app's. Another benefit of web apps, is that with some effort it can run everywhere, where as an app container like electron needs to have separate builds for each platform.

Agreed that's definitely a drawback.

Mozilla had an experimental project called qbrt that was like electron but used the locally installed Firefox, exactly like you're describing. Hasn't been updated in quite a while though

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

#112
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…

> NodeJS-to-Native-GUI

I feel I have to find a better name for libui-node

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

#113

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…

“I want 1 Chrome running” Why? To save a little disk space? There are a lot of downsides to that. Microsoft thought DLLs were a good idea once. I know Chrome has better isolation but it’s still not as idiot proof and most importantly, as cheap to support as having your own totally independent app. If a user contacts you with a bug, you immediate know for a fact it has nothing to do with any new chrome update or possi…

To save RAM usage and preventing constant cache thrashing.

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

#114

Earlier quoted context omitted.

ES6 an typescript are wonderful languages and have little resemblance to the jquery-esque JavaScript era. Think C# rather than jquery.

But you could just use C# instead on the desktop, and be happier.

The world's largest computing markets dont use desktops. India and China are 80% mobile traffic. These people have never seen a desktop or a laptop in their life, but use the web and mobile apps with a lot of comfort.

The JS developer ecosystem is very popular as a consequence of the mobile-first ecosystem. And I think it is a great thing that desktop SDK are evolving to be JS first.

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

#115
post #106

Earlier quoted context omitted.

No, it is something that has been doing "automatic data binding via property get/set interception, for example" since 2008, so it is easy to see it in an language that isn't JavaScript. Additionally, Xamarin is older than VueJS.

It would be a bigger deal if it was not windows only.

Xamarin never was Windows only.

And Mono was a thing before .NET Core came into the scene.

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

#116
post #106
post #96

Earlier quoted context omitted.

Is this something that's had good crossplatform support since 2008 or more recently?

No, it is something that has been doing "automatic data binding via property get/set interception, for example" since 2008, so it is easy to see it in an language that isn't JavaScript. Additionally, Xamarin is older than VueJS.

Yeah, I've worked with XAML and such in .NET-land. DependencyProperties are nowhere near as painless and transparent as the state of things in Vue. Doing computed propeties, trying to use converters in a sane way, setting up templates for repeated items - all quite clunky and arcane. This falls out of doing interception at the library level rather than the language level, I think.
Post reply on HN