neoEdge vs NW.js ? - Forum

Forum Navigation
You need to log in to create posts and topics.

neoEdge vs NW.js ?

Thinking out loud about neoEdge vs NW.js

neoEdge Positives

  • Well integrated with IDE for an easy edit, run and repeat cycle
  • Can use VisualNEO Win code for OS interaction
  • Tiny sized distribution files

neoEdge Negatives

  • Windows only
  • Requires purchase of an additional plugin for full customisation
  • Needs user to install MS WebView2

NW.js Positives

  • Cross Platform
  • Huge community

NW.js Negatives

  • Not integrated with IDE
  • Requires learning Node.js for OS interaction
  • Large environment distributed and duplicated for every app

If being cross platform is essential, then NW.js is the solution, but if you need Windows only the answer is less clear.

Any other thoughts, or other +ve and -ve that have been missed?

luishp, Vadim and 2 other users have reacted to this post.
luishpVadimjoferar333Darbdenral

@susan I think you have done a very complete analisys.
Note that you can integrate NWjs with the IDE using the Tools menu.
It's also possible to make VisualNEO Web plugins targeting Node.js functionalities.

Thank you!

Vadim has reacted to this post.
Vadim

Maybe you do not really have to choose because you can have both same time.

Because of the nw.js folder structure and the fact that they share identical package.json you can run basically same app so you get benefits of both.  Anyway you have many options to build your final app using for example  _run and _runInRectangle .

When you combine here the possibility to use neoCMS, third party php software, visualNEO vin database access and other plugins you have a soup to mix long time.

 

 

luishp has reacted to this post.
luishp