4 ms·

Even a Java based gui written using the Swing toolkit (which I believe is considered ancient tech that most have moved on from although I haven't built a gui in

by avl999 5y ago

Even a Java based gui written using the Swing toolkit (which I believe is considered ancient tech that most have moved on from although I haven't built a gui in java in ages so don't take my word for it) would be an improvement on these electron apps just because it will prevent the cancer that is Javascript, node, npm and the entire JS ecosystem from invading the desktop. We deal with JS/Node on the frontend because we have no choice, that tech invading the server and the desktop is just sad to watch.

xwolfi 5y ago
I found that we have the choice and successfully migrated an enormous bloatware of thousands of binding setinterval functions (Angular 1) full of node dependencies, npm breakages, impossible to understand grunt builds into a simple, 10 files pure javascript + some jquery approximately well compatmentalised set of bespoke business services. The only critic I ever faced with this was that it was not classical nor "the proper way", but the fact it loaded instantly and worked exactly the same way albeit infinitely faster managed to convince we may not need all that jazz. You always have a choice but you'll face more resistance and worry not to go with everyone else towards suicide by a thousand dependencies.
dragonwriter 5y ago
> Even a Java based gui written using the Swing toolkit (which I believe is considered ancient tech that most have moved on from although I haven't built a gui in java in ages so don't take my word for it) would be an improvement on these electron apps just because it will prevent the cancer that is Javascript, node, npm and the entire JS ecosystem from invading the desktop. I remember a very similar complaint being made about Eclipse, Java, and Swing as you make about Electron, JS, and Node as a cancer on the desktop.
makeitdouble 5y ago
From my Java days, backend work looked like creating plugins to auto-generate XML, which would be parsed by the build system to auto-generate classes...on a philosophy level, I can't remember people preaching simplicity and pragmatism outside of the Eclipse people (who had to deal with real hard complexity issues day in and day out...) An alternative history where Java would have been huge on the desktop doesn't look to me like we'd have a heaven of well-though lightweight apps TBH. I personnally think npm is something inevitable, and am not sure Maven for instance is fundamentally better in the grand scheme of things (I'd argue as a dev it's way more of a PITA without any specific upside, but it might be my own incompetence).

by avl999 5y ago

xwolfi 5y ago

I found that we have the choice and successfully migrated an enormous bloatware of thousands of binding setinterval functions (Angular 1) full of node dependencies, npm breakages, impossible to understand grunt builds into a simple, 10 files pure javascript + some jquery approximately well compatmentalised set of bespoke business services. The only critic I ever faced with this was that it was not classical nor "the proper way", but the fact it loaded instantly and worked exactly the same way albeit infinitely faster managed to convince we may not need all that jazz. You always have a choice but you'll face more resistance and worry not to go with everyone else towards suicide by a thousand dependencies.

dragonwriter 5y ago

> Even a Java based gui written using the Swing toolkit (which I believe is considered ancient tech that most have moved on from although I haven't built a gui in java in ages so don't take my word for it) would be an improvement on these electron apps just because it will prevent the cancer that is Javascript, node, npm and the entire JS ecosystem from invading the desktop. I remember a very similar complaint being made about Eclipse, Java, and Swing as you make about Electron, JS, and Node as a cancer on the desktop.

makeitdouble 5y ago

From my Java days, backend work looked like creating plugins to auto-generate XML, which would be parsed by the build system to auto-generate classes...on a philosophy level, I can't remember people preaching simplicity and pragmatism outside of the Eclipse people (who had to deal with real hard complexity issues day in and day out...) An alternative history where Java would have been huge on the desktop doesn't look to me like we'd have a heaven of well-though lightweight apps TBH. I personnally think npm is something inevitable, and am not sure Maven for instance is fundamentally better in the grand scheme of things (I'd argue as a dev it's way more of a PITA without any specific upside, but it might be my own incompetence).