blocks|key|157374|text|电子有一个解释与nwjs不同的page。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|157375|与NW.js一样，|157376|也提供了一个使用web技术编写桌面应用程序的平台。这两个平台都使开发人员能够利用HTML、JavaScript和Node.js。从表面上看，它们似乎非常相似。|blockquote|157377|157378|然而，这两个项目之间存在根本性的差异，这使得电子产品与NW.js完全不同。|157379|157380|应用程序的HTML在NW.js中，应用程序的主要入口点可以是网页。在这种情况下，NW.js将在浏览器窗口中打开给定的入口点。|157381|在Electron中，入口点始终是JavaScript脚本。您可以手动创建浏览器窗口并使用API加载HTML文件，而不是直接提供URL。您还需要侦听窗口事件以决定何时退出应用程序。|157382|电子的工作原理更像是Node.js运行时。电子的API是低级的，所以你可以用它来代替PhantomJS进行浏览器测试。|157383|157384|节点集成在NW.js中，网页中的节点集成需要修补Chromium才能工作，而在Electron中，我们选择了一种不同的方式将libuv循环与每个平台的消息循环集成在一起，以避免黑客攻击Chromium。请参阅node_bindings代码了解如何做到这一点。|ordered-list-item|157385|157386|157387|JavaScript+context如果您是经验丰富的NW.js用户，则应熟悉节点上下文和web上下文的概念。这些概念之所以被发明，是因为implemented.|157388|是NW.js|157389|通过使用Node的多上下文功能，电子不会在网页中引入新的JavaScript上下文。|157390|注意:从0.13开始，NW.js可选地支持多上下文。|157391|157392|传统支持NW.js仍然提供支持Windows+XP的“传统版本”。它不接收安全更新。|157393|157394|鉴于硬件制造商、微软、Chromium和Node.js甚至还没有为该系统发布关键的安全更新，我们必须警告你，使用Windows+XP是非常不安全和完全不负责任的。|157395|然而，我们知道，可能存在超出我们想象的需求，所以如果您正在寻找运行在Windows+XP上的像Electron这样的东西，NW.js传统版本可能是适合您的。|157396|157397|功能在支持的功能数量上有许多不同。电子有一个更大的社区，更多的生产应用程序使用它，并在npm上提供大量的用户模块。|157398|157399|例如，Electron内置了对自动更新的支持和无数的工具，使安装程序的创建变得更容易。作为支持NW.js的一个例子，NW.js支持更多用于Chrome应用程序开发的Chrome.*+API。|157400|当然，我们相信对于使用web技术(如Visual+Studio+Code、Slack或Facebook+Messenger)构建的精致生产应用程序，Electron是更好的平台；然而，我们希望公平对待我们的web技术朋友。如果你有电子不能满足的功能需求，你可能想试试NW.js。|157401|请记住，这可能是有偏见的--它来自Electron的维基页面。|157402|电子不会引入|157403|在网页中|157404|一个新的JavaScript上下文。|157405|157406|157407|源代码保护|BOLD|157408|电子正在使用asar打包其应用程序，其中包含应用程序的未受保护的源代码。这使得应用程序1可以在用户不知道的情况下提取应用程序2并注入易受攻击的脚本。你可以在this+project+on+GitHub+to+see+an+example+of+how+to+manipulate+the+Slack+app上查看一个例子。就目前而言，the+Electron+team+don't+have+any+plans+to+implement+support+for+source+code+protection。|157409|NW.js有built+in+support+for+compiling+your+source+code+to+protected+binaries。|157410|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/electron/electron/blob/master/docs/development/electron-vs-nwjs.md|1|https://www.npmjs.com/package/asar|2|https://github.com/albinekb/enhanced-slack|3|https://github.com/electron/electron/issues/3041#issuecomment-180504349|4|http://docs.nwjs.io/en/latest/For%2520Users/Advanced/Protect%2520JavaScript%2520Source%2520Code/^0|8|4|F|4|0|0|0|0|0|0|0|0|0|0|0|2W|D|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|5|0|6|4|1|26|23|2|4N|2E|3|0|6|1X|4|0^^$0|@$1|2|3|4|5|6|7|2L|8|@$9|2M|A|2N|B|C]]|D|@$9|2O|A|2P|1|2Q]]|E|$]]|$1|F|3|G|5|6|7|2R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|2S|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|2T|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|2U|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|2V|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|2W|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|2X|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|2Y|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|2Z|8|@]|D|@]|E|$]]|$1|V|3|W|5|X|7|30|8|@$9|31|A|32|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|33|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|34|8|@]|D|@]|E|$]]|$1|10|3|11|5|X|7|35|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|36|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|37|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|38|8|@]|D|@]|E|$]]|$1|18|3|-4|5|6|7|39|8|@]|D|@]|E|$]]|$1|19|3|1A|5|X|7|3A|8|@]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|3B|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|3C|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|3D|8|@]|D|@]|E|$]]|$1|1G|3|-4|5|6|7|3E|8|@]|D|@]|E|$]]|$1|1H|3|1I|5|X|7|3F|8|@]|D|@]|E|$]]|$1|1J|3|-4|5|6|7|3G|8|@]|D|@]|E|$]]|$1|1K|3|1L|5|6|7|3H|8|@]|D|@]|E|$]]|$1|1M|3|1N|5|6|7|3I|8|@]|D|@]|E|$]]|$1|1O|3|1P|5|6|7|3J|8|@]|D|@]|E|$]]|$1|1Q|3|1R|5|6|7|3K|8|@]|D|@]|E|$]]|$1|1S|3|1T|5|6|7|3L|8|@]|D|@]|E|$]]|$1|1U|3|1V|5|J|7|3M|8|@]|D|@]|E|$]]|$1|1W|3|-4|5|6|7|3N|8|@]|D|@]|E|$]]|$1|1X|3|-4|5|6|7|3O|8|@]|D|@]|E|$]]|$1|1Y|3|1Z|5|6|7|3P|8|@$9|3Q|A|3R|B|20]]|D|@]|E|$]]|$1|21|3|22|5|6|7|3S|8|@]|D|@$9|3T|A|3U|1|3V]|$9|3W|A|3X|1|3Y]|$9|3Z|A|40|1|41]]|E|$]]|$1|23|3|24|5|6|7|42|8|@]|D|@$9|43|A|44|1|45]]|E|$]]|$1|25|3|-4|5|6|7|46|8|@]|D|@]|E|$]]]|26|$27|$5|28|29|2A|E|$2B|2C]]|2D|$5|28|29|2A|E|$2B|2E]]|2F|$5|28|29|2A|E|$2B|2G]]|2H|$5|28|29|2A|E|$2B|2I]]|2J|$5|28|29|2A|E|$2B|2K]]]]

Electron has a <a href="https://github.com/electron/electron/blob/master/docs/development/electron-vs-nwjs.md" rel="nofollow noreferrer">page</a> explaining the differences with <code>nwjs</code>.
<blockquote>
Like NW.js, Electron provides a platform to write desktop applications
with web technologies. Both platforms enable developers to utilize
HTML, JavaScript, and Node.js. On the surface, they seem very similar.
There are however fundamental differences between the two projects
that make Electron a completely separate product from NW.js.
<ol>
<li>Entry of Application In NW.js, the main entry point of an
application can be an HTML web page. In that case, NW.js will open the
given entry point in a browser window.</li>
</ol>
In Electron, the entry point is always a JavaScript script. Instead of
providing a URL directly, you manually create a browser window and
load an HTML file using the API. You also need to listen to window
events to decide when to quit the application.
Electron works more like the Node.js runtime. Electron's APIs are
lower level so you can use it for browser testing in place of
PhantomJS.
<ol start="2">
<li>Node Integration In NW.js, the Node integration in web pages
requires patching Chromium to work, while in Electron we chose a
different way to integrate the libuv loop with each platform's message
loop to avoid hacking Chromium. See the <code>node_bindings</code> code for how
that was done.
</li>
<li>JavaScript Contexts If you are an experienced NW.js user, you
should be familiar with the concept of Node context and web context.
These concepts were invented because of how NW.js was implemented.
</li>
</ol>
By using the multi-context feature of Node, Electron doesn't introduce
a new JavaScript context in web pages.
Note: NW.js has optionally supported multi-context since 0.13.
<ol start="4">
<li>Legacy Support NW.js still offers a &quot;legacy release&quot; that supports
Windows XP. It doesn't receive security updates.</li>
</ol>
Given that hardware manufacturers, Microsoft, Chromium, and Node.js
haven't released even critical security updates for that system, we
have to warn you that using Windows XP is wildly insecure and outright
irresponsible.
However, we understand that requirements outside our wildest
imagination may exist, so if you're looking for something like
Electron that runs on Windows XP, the NW.js legacy release might be
the right fit for you.
<ol start="5">
<li>Features There are numerous differences in the amount of supported
features. Electron has a bigger community, more production apps using
it, and a large amount of userland modules available on npm.</li>
</ol>
As an example, Electron has built-in support for automatic updates and
countless tools that make the creation of installers easier. As an
example in favor of NW.js, NW.js supports more Chrome.* APIs for the
development of Chrome Apps.
Naturally, we believe that Electron is the better platform for
polished production applications built with web technologies (like
Visual Studio Code, Slack, or Facebook Messenger); however, we want to
be fair to our web technology friends. If you have feature needs that
Electron does not meet, you might want to try NW.js.
</blockquote>
<h3>Keep in mind this may be biased- it is from Electron's wiki page.</h3>
Electron doesn't introduce
<blockquote>
a new JavaScript context in web pages.
</blockquote>
Source code protection
Electron is packaging its applications with <a href="https://www.npmjs.com/package/asar" rel="nofollow noreferrer">asar</a>, which contains the applications' unprotected source code. This makes it possible for application 1 to extract application 2 and inject vulnerable scripts, without the user knowing it. You can checkout <a href="https://github.com/albinekb/enhanced-slack" rel="nofollow noreferrer">this project on GitHub to see an example of how to manipulate the Slack app</a> for an example. As for now, <a href="https://github.com/electron/electron/issues/3041#issuecomment-180504349" rel="nofollow noreferrer">the Electron team don't have any plans to implement support for source code protection</a>.
NW.js has <a href="http://docs.nwjs.io/en/latest/For%20Users/Advanced/Protect%20JavaScript%20Source%20Code/" rel="nofollow noreferrer">built in support for compiling your source code to protected binaries</a>.

We are planning to built cross platform desktop application. We found that <a href="https://github.com/rogerwang/node-webkit" rel="noreferrer">Node-Webkit</a> is a perfect choice for us. But GitHub developed their own framework called <a href="https://github.com/atom/electron" rel="noreferrer">Electron</a> instead of using Node-Webkit.

What is the difference between them?

Node-Webkit vs Electron

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们计划建立跨平台的桌面应用程序。我们发现对我们来说是一个完美的选择。但GitHub开发了自己的名为的框架，而不是使用Node-Webkit。它们之间的区别是什么？

Node-Webkit vs Electron-腾讯云开发者社区-腾讯云

问Node-Webkit vs Electron
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Node-Webkit vs ElectronEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Node-Webkit vs Electron
EN