node-webkit as «system-wide framework»

[dangreen]

Installing node-webkit as «system-wide framework» (like Wineskin engines for OS X or Qt).
For example, we installed node-webkit as framework, after that node-webkit-based application won't contain the node and WebKit itself.

[pauliusuza]

That would complicate the deployment for non technically savvy people amongst other things.

[dangreen]

@pauliusuza, do simple installer or package?

[zhchbin]

I totally agree with @dangreen . This is what I am thinking from long long ago.(Haha, just several months ago.)

[pauliusuza]

I believe this would limit use of node-webkit for publishing apps on app stores, since it would require some higher level permissions and a more complicated install process. Look at Java or Adobe AIR and you can clearly see where a similar path would lead. I like the fact that it's self contained, and I would support if it would stay this way.

[dangreen]

@pauliusuza, i agree with you, but not all apps are developed to App Store

[pauliusuza]

@dangreen correct, not yet. However any platform's success highly depends on developer's ability to monetize their work, and app store distribution model is one of the best ways to do it. If developers will not have this ability, they will surely look for better alternatives (effectively killing this beast of a platform in it's tracks).

[dangreen]

@pauliusuza, Qt is good example: apps for Mac App Store contains frameworks, but in some Linux distributives Qt is system-wide framework.

[pauliusuza]

@dangreen what about compatibility? Are you willing to sacrifice the comfort of knowing your app is at all times compatible with the version of the wrapper running it?

To me decoupling the wrapper and making it a framework means that I will have 2x more bugs, since it can be updated, upgraded or degraded independently and I have no control over that process.

[dangreen]

@pauliusuza, make small package manager with repo, which will download required version of framework.

[rogerwang]

Thanks for reporting. This issue is duplicate with #64