Very likely - but details/license TBA.
* Will you have a freemium model? (Free for opensource apps.)
Yes, there will always be a free way of using Fuse and Uno.
* Will you change the name like others have suggested?
No :)
* Will you consider a no-JS model to develop?
Yup. We have that already. You can use Fuse with just Uno if you like, JS is an optional component. However, our main focus is on creating a very rapid and streamlined development workflow with UX+JS.
Best regards, Anders from Fuse
If I had to choose, I would release the whole platform (not only Uno and your libraries, but your whole toolkit/IDE) under dual license: RPL and proprietary. This way, if people choose the RPL way, they're forced to publish the sources (even if they distribute the app internally), unless they buy you a license. And this way you allow contributions from outside too.
Good on you :)
I doubt it will make a real difference to anyone that wants to use it. If Google can name a language Go, then you can name your product Fuse.
I'm sure the people behind FUSE file system library might have some comments to add. I would never name my product after a major open source project. Like as if I created something and called it Blender or Pencil.
The worst they could do is to blog about it and if they're lucky and get coverage with their article, it could be settled in the court of public opinion.
* Will you open-source Uno?
* Will you have a freemium model? (Free for opensource apps.)
* Will you change the name like others have suggested?
* Will you consider a no-JS model to develop?
If all of the answers are YES to the above, then please sign me up for the beta.