You rewrite the file to remove the Etch-related things (the import statement, the
jsx comment, and any calls you make to
etch) and replace them with the respective React-specific code. Etch components use the same syntax and have the same lifestyle methods. There might be some methods that are Atom-specific in a component (
deserialize, for example), and those should be taken out.
Is there an example or docs for using Etch in a stand alone node app?
You could check out
brightwheel, which is aimed at Electron apps.
Is there any any sort of example for using Etch for plugin development at all?
Just look at the packages that depend on it.
atom-select-list is a straightforward example.
installExtension() snippet to init.js caused a bunch of console errors
Those might be solvable.
What is a realistic expectation with regard to the lifespan of Etch given the rather short life of space-pen-views?
space-pen-views and Etch were created was to provide a default library that just spits out and updates HTML components. The devs aren’t constantly tinkering with that part of Atom, and the lack of examples you have found is because they’re focused on other things like more performant highlighting, not because they’re coming up with a new view framework every two years.
And finally, why would you?
You use Etch because you don’t want to use direct DOM manipulation and you are familiar with React syntax.
Can you prove it’s faster with something other than micro benchmarks?
How about a thought experiment? React includes routing, which is not required for Atom.
It seams like Etch is subset of React features.
This is exactly the point of Etch. It’s React without all the extra stuff. It works the same when it comes to writing components, and includes nothing else.