3 ms·

goal posts fly overhead

by Vanit 10y ago

StavrosK 10y ago
The original post was comparing Flash's authoring experience to Electron's authoring experience. The fact that you can use the former in the latter wasn't relevant. It was about what would happen to animation if Flash were to go away versus it Electron were to go away.
- derefr 9y ago
  I'm confused—what, precisely, is the "Electron authoring experience", when used in this sense? If you program an Electron app using HTML5, then isn't anything that outputs HTML5 part of the "Electron authoring experience"?
  - StavrosK 9y ago
    No, you're conflating writing something with running it. These are different in the same way that editing a photo in Photoshop isn't part of the "MS paint experience" just because MS paint can open the file. By "authoring experience" we mean making something purely in that platform, i.e. Electron vs Flash, i.e. writing it by hand vs using Flash's rich tooling.
    - derefr 9y ago
      Oh, okay. But, in that sense, there is no "Electron authoring experience," then. It no more "has" a text-editor you can use to "write Electron by hand" than it has an authoring app you can use to "create Electron in a WYSIWYG style." Electron is not even MS Paint; Electron is Preview.app. It doesn't assist you in making anything. It's a viewer. Do you blame Preview.app for not making it easy to make PSD files? Do you expect it to help you with that? Electron is, morally, a transpiler. It's a thing you shove a completed application through, and get a completed application for a different platform out the other side. The only necessary "Electron" part of an "Electron project" are the Electron-specific configuration fields in the package.json file. And that's effectively just a release/distribution spec file, much like the debian/ dir for projects that ship .debs. Which is all to say: there is no such thing as an "Electron project." There's just "web projects" that happen to ship Electron releases. (And, yes, there are projects that never bother to test in any other configuration, so they lock themselves into their code only working on Electron. But this is no different than locking your web project into only rendering on a particular browser.)
      - StavrosK 9y ago
        Yes, exactly, that's the original argument. Electron doesn't help you make anything, so making an animation if Flash (an alternative to Electron) were to go away would be much, much harder.

goal posts fly overhead

by Vanit 10y ago

goal posts fly overhead

The original post was comparing Flash's authoring experience to Electron's authoring experience. The fact that you can use the former in the latter wasn't relevant. It was about what would happen to animation if Flash were to go away versus it Electron were to go away.

derefr 9y ago
I'm confused—what, precisely, is the "Electron authoring experience", when used in this sense? If you program an Electron app using HTML5, then isn't anything that outputs HTML5 part of the "Electron authoring experience"?
- StavrosK 9y ago
  No, you're conflating writing something with running it. These are different in the same way that editing a photo in Photoshop isn't part of the "MS paint experience" just because MS paint can open the file. By "authoring experience" we mean making something purely in that platform, i.e. Electron vs Flash, i.e. writing it by hand vs using Flash's rich tooling.
  - derefr 9y ago
    Oh, okay. But, in that sense, there is no "Electron authoring experience," then. It no more "has" a text-editor you can use to "write Electron by hand" than it has an authoring app you can use to "create Electron in a WYSIWYG style." Electron is not even MS Paint; Electron is Preview.app. It doesn't assist you in making anything. It's a viewer. Do you blame Preview.app for not making it easy to make PSD files? Do you expect it to help you with that? Electron is, morally, a transpiler. It's a thing you shove a completed application through, and get a completed application for a different platform out the other side. The only necessary "Electron" part of an "Electron project" are the Electron-specific configuration fields in the package.json file. And that's effectively just a release/distribution spec file, much like the debian/ dir for projects that ship .debs. Which is all to say: there is no such thing as an "Electron project." There's just "web projects" that happen to ship Electron releases. (And, yes, there are projects that never bother to test in any other configuration, so they lock themselves into their code only working on Electron. But this is no different than locking your web project into only rendering on a particular browser.)
    - StavrosK 9y ago
      Yes, exactly, that's the original argument. Electron doesn't help you make anything, so making an animation if Flash (an alternative to Electron) were to go away would be much, much harder.