3 ms·

But... We need our app to be accessible on essentially 4 different platforms. Even if we had the resources to code and maintain four native applications, getti

But... We need our app to be accessible on essentially 4 different platforms. Even if we had the resources to code and maintain four native applications, getting users to update is like pulling teeth. Full page loads are out, because we don't want to rerender to things like reordering a list. Theres a whole bunch of UX quality of life things that go away if you remove javascript... Honestly, I'd prefer that our internal business app DIDN'T appear in google...

colejohnson66 6y ago
I wish there was a better alternative to Electron’s method of giving each app its own copy of the browser. It makes sense for compatibility reasons (your code may only be tested on one version of Chrome and later ones may break it), but most apps don’t need that. Using the built in Chrome copy in a “frameless” mode would be nice. JavaScript (through TypeScript) is a very nice programming language, but it gets a horrible rap from bad or lazy programmers. It’s kind of like how PHP 5 was. Everyone still rags on JS for things that ES6 fixed just like how people rag on PHP for things that have been fixed since PHP 7.
- pwdisswordfish0 6y ago
  People also blame JS (the language) for things that are the fault of NodeJS (a runtime by one group that implements an incompatible fork of JS) and NPM (which is a community at the very least, and arguably a design and development methodology). Neither of these are "JS", but loads of people (both those who spend their days steeped in GitHub issues related to NodeJS development and those looking to heap scorn upon it) will argue as if they're inseparable or synonymous, even though that's not the case at all. Imagine if people conflated Android development with programming in Java. (This might be a more appropriate metaphor than intended, since most of the time the people who strike me as being out for blood regarding JS tend to exhibit the arrogance and nuance of someone coming straight from their university's second year Java course.)

colejohnson66 6y ago

I wish there was a better alternative to Electron’s method of giving each app its own copy of the browser. It makes sense for compatibility reasons (your code may only be tested on one version of Chrome and later ones may break it), but most apps don’t need that. Using the built in Chrome copy in a “frameless” mode would be nice. JavaScript (through TypeScript) is a very nice programming language, but it gets a horrible rap from bad or lazy programmers. It’s kind of like how PHP 5 was. Everyone still rags on JS for things that ES6 fixed just like how people rag on PHP for things that have been fixed since PHP 7.

pwdisswordfish0 6y ago
People also blame JS (the language) for things that are the fault of NodeJS (a runtime by one group that implements an incompatible fork of JS) and NPM (which is a community at the very least, and arguably a design and development methodology). Neither of these are "JS", but loads of people (both those who spend their days steeped in GitHub issues related to NodeJS development and those looking to heap scorn upon it) will argue as if they're inseparable or synonymous, even though that's not the case at all. Imagine if people conflated Android development with programming in Java. (This might be a more appropriate metaphor than intended, since most of the time the people who strike me as being out for blood regarding JS tend to exhibit the arrogance and nuance of someone coming straight from their university's second year Java course.)