NW.js and Electron compared
来源:互联网 发布:云计算案例分析 编辑:程序博客网 时间:2024/05/16 13:37
https://www.xplatform.rocks/2016/02/09/nw-js-vs-electron/
09 Feb 2016
I've spent a lot of time doing cross platform development over the past year with a huge workload on cross platform desktop development.
During that time, I found some customers and blog readers asking me if they should go forNW.js or if they should go direction Electron. There is no quick answer to this question. It's really this kind of question that has to be answered withIt depends.
I've used both frameworks for real projects in the past and both of them worked great for the given projects. Neither Electron nor NW.js is perfect (but they'are close :D). Each has it's own pitfalls. But the communities behind those frameworks are awesome and keep on answering really quick to questions popping up on GitHub or in tools like Gitter or Slack.
There is already a post on the web comparing both from various perspectives but the post(available here) is a bit outdated. Especially Electron has evolved a lot since the linked post was initially published. So it's time to compare both frameworks again with all the information publicly available by February 2016.
I've create a simple sheet on Google which allows anyone to leave comments in it.
Here the direct link to the Google Sheet.
Soft Facts
Since the first public release of Visual Studio Code - which is based on Electron-, the framework gained a lot more attention than before.
Since July 2015, we're waiting for a new NW.js release. Which have to move all new features and the highly required dependency updates (like migrating from io.js to latest Node.js) from beta status to a release candidate. Testing stuff on beta software is great but shipping real world products on beta frameworks will not work!
If you compare both frameworks based on non-beta releases Electron is far ahead. But I believe in the team building NW.js to ship their great beta as soon as possible.
Besides the hard facts listed in the Google Sheet, you and your team should invest some time and look at both frameworks. There are some differences when it comes to architecture and usage from a developers perspective. Make yourself comfortable with Electron and NW.js. Decide which one fits better to your needs. Currently both are under active development, so chances are pretty good that both exists for long time from now (whatever that means in this age :D).
Summary
In the end, it's once again a personal decision which depends on your requirements. Have you also tried both? What are experiences with those frameworks?Leave a comment and share your thoughts.
- NW.js and Electron compared
- NW.js & Electron Compared (2016 Edition)
- nw.js
- VML and SVG Compared
- NW.js入门学习
- NW.js初体验
- nw.js入门
- nw.js 填坑
- Nw.js开发
- nw.js学习
- ZFS,XFS,and EXT4 filesystems compared
- NW.js的简单使用
- nw.js:编写桌面应用
- NW.js开发笔记(一) nw入门及使用
- nw.js node-webkit系列(22).nw执行过程及如何获取.nw真实路径
- 安装Node.js和Electron
- A Compared Overview of C++, C#, and Java
- A Compared Overview of C++, C#, and Java
- 从通用类型开始
- 软件测试中80/20原则
- pxeboot install centos7
- [转]c++ 中__declspec 的用法
- X265整个数据流向
- NW.js and Electron compared
- DllMain操作不当造成死锁
- 一个项目从开始到结束-1
- 大津法理解
- 迷雾,笔试面试题
- 数据密集型系统架构设计
- java
- 关于<吞吐量,延迟> & <信号量和互斥锁>的比喻区分
- xpstopdf