Live data from Hacker News

The State of Desktop Applications in Node.js

nodesource.com

71–80 of 115 posts

Re: The State of Desktop Applications in Node.js

#71
post #2

Last time I tried building a 'blank' node-webkit app for OS X (using https://github.com/Dica-Developer/generator-node-webkit ), the resulting .app came to ~100MB. Does anyone know the base size for an atom-shell app?

Seriously, does anybody nowadays care about a 100 MB desktop app? I developed my first app in 1997 with Delphi and it was only 200 KB, so from that perspective I always cringe when I see that an app I've developed is multiple MB. But in all seriousness, do users actually care? Every time I download an OS X app, it's at least 50 MB, but I find that even I don't care anymore because downloading 50 MB nowadays only take…

Of course. The world is bigger than SV :P

http://blog.chriszacharias.com/page-weight-matters

Re: The State of Desktop Applications in Node.js

#73
post #60
post #47

Earlier quoted context omitted.

Just for the delicious pain of Java development?

Java development is pure pleasure when compared with web development.

I assume you once did a project where you were trying to make FactoryModelControllerInitWidgets in js? The fetishization of boilerplate doesn't work as well in js.

Re: The State of Desktop Applications in Node.js

#74
post #60

Earlier quoted context omitted.

Java development is pure pleasure when compared with web development.

Usually said by Java developer not understanding JavaScript.

You see, I barely need to "understand" Java to use it and get decent and performant code but I need to be a javascript expert to be able to do anything not horrible.

Please stop trying to act like the state of web and javascript is good because it's shit. Web development is basically a bunch of people suffering from stockholm syndrome.

Re: The State of Desktop Applications in Node.js

#75
post #54

This article doesn't accurately convey the state of Chrome Applications. There's actually a much richer way to build apps that have a more native look and feel, including their own branded top-level window with fewer of the limitations the author cites. https://developer.chrome.com/apps/about_apps

The article's title is "The State of Desktop Applications in Node.js", and chrome applications do not let you run node.js on the local machine. If you can't run your own userland code on the machine and talk to hardware, then you can hardly call it a desktop app. Google wants to keep you locked in their sandbox.

I don't know, they seem to tout interfacing with network and hardware pretty heavily.

Re: The State of Desktop Applications in Node.js

#76
post #74

Earlier quoted context omitted.

Usually said by Java developer not understanding JavaScript.

You see, I barely need to "understand" Java to use it and get decent and performant code but I need to be a javascript expert to be able to do anything not horrible. Please stop trying to act like the state of web and javascript is good because it's shit. Web development is basically a bunch of people suffering from stockholm syndrome.

You've coded a lot in languages very similar to Java and that is an argument for Java's ease of use?

Re: The State of Desktop Applications in Node.js

#77
post #60

Earlier quoted context omitted.

Java development is pure pleasure when compared with web development.

Usually said by Java developer not understanding JavaScript.

Can't I just take your glib statement and just reverse the roles (JS developer not understanding Java)? What makes JS development more misunderstood than Java development?

Re: The State of Desktop Applications in Node.js

#79
post #76
post #74

Earlier quoted context omitted.

You see, I barely need to "understand" Java to use it and get decent and performant code but I need to be a javascript expert to be able to do anything not horrible. Please stop trying to act like the state of web and javascript is good because it's shit. Web development is basically a bunch of people suffering from stockholm syndrome.

You've coded a lot in languages very similar to Java and that is an argument for Java's ease of use?

My argument was that the idea of having to work on a javascript project with >10,000 lines of code makes me want to vomit while the idea of working on a java project with >1,000,000 lines of code doesn't make me feel anything special.

People that complain about verbosity really don't have their priorities in line

Post reply on HN