Interoperability of decent(ralized) platforms should start at being able to operate them side by side. Kudos for peineering this space. Our approach differs in that we seek the shortest path to delivering user value as we are aiimg to bootstrap to co-evolve, meta-design user extensibility and personalizability and interoperability at scale. Being end user/artizan developer focused with https://twitter.com/TrailHub1 rely on https://fission.codes/ as a Configuration Provider for WebNative development to be an Autonomous Capability Facilitator. Hope to see these paths converging in the future.
Personally I prefer binary releases certainly for fission.codes, as building from source tends to be way more brittle say 6 months down the line.
Starter kits that combine starter kits for app development using specific frameworks like Elm, AppRun or React does make perfect sense though.
Or an npm package that adds Fission’s Constellation Provision would make perfect sense.
the way I work on windows is to run fission in WSL and just take a single build directory for any specific app from wherever it is being developed
but moving towards adding it to IPFS and use the CID.
I actually like WSL. I know windows updates can be scary.
I turned off automatic updates a month at a time reset it weekly
You would have to be doing something like that with Ubuntu now.
Check out the horror story reported here https://twitter.com/aphelionz/status/1307055323560239105
I think relying on IPFS pins are way better then checking out git for delivery.
More importantly, unless one wishes to contribute to the project or develop it further themselves, adjust
I’m wondering if using npm as a way to install binaries is something that is used elsewhere. It means that when checking out a github repo, npm install would give you a fission binary and everything else you need.
KAIZEN is an one stop solution for dapp and dweb developer. With KAIZEN, you get to:
Manage multiple decentralized tech in one platform (The Graph/Ethereum/Tron/)