我对使用 HTML5+webkit 创建桌面应用程序很感兴趣，并且我希望能够为各种目标平台构建独立的可执行文件，例如 Windows 的 .exe 文件和 Mac OS 的 .dmg 图像。我玩过node-webkit，除了打包/分发部分之外，这看起来不错。我也偶然发现了TideSDK，但该项目似乎处于非活动状态。例如，我看到的最新版本是 2012 年 11 月的测试版。然而，似乎核心开发人员已经转而开发TideKit。
这里有人知道 TideKit 是否旨在替代 TideSDK 吗？TideSDK 会消失吗？等等
好吧，TIDE 现在正式成为一个死项目。我大约 15 分钟前才收到这封电子邮件。
TideKit.com 和 TideKit 已停产。
TideKit 是用于同时为所有平台开发应用程序的软件，使用 JavaScript 编写的单一代码库。
产品的范围和复杂性使得一次组装平台变得困难。这源于针对所有平台的应用程序开发的整体方法。在为 JavaScript 开发人员创建平台时，大部分核心工程都是使用各种影响开发速度的低级语言。当我们达到里程碑时，我们考虑交付部分平台，但这不适合开始试验。
我们因未在发布前披露我们的技术创新而受到广泛批评。在竞争激烈的环境中，边走边展示优势也意味着边走边吸收。我们已经见证了我们的技术优势可以多快被竞争对手吸收到我们的开源 TideSDK 产品中。因此，我们推迟了竞争对手对功能的复制，增加了我们的技术壁垒，并努力保护我们的知识产权和商业案例，直到我们觉得我们准备好了。
在初创公司中，我们谈论最小可行产品（MVP）。在我们的案例中，我们的最小可行产品要大得多，也更难实现。总共投入了大约三年的研发时间，多名开发人员的工作时间超过了全职工作时间。扩展开发的一个因素是扩大范围，旨在降低应用程序开发过程中的摩擦。
2014 年 2 月，我们创建了一个系统，为开发人员排队预订系统，以便尽早访问 TideKit。我们的目标是在可用时提供早期试用。由于开发本身很复杂，我们无法提供持票人可以开始试用过程的日期 - 但它将遵循我们的测试版，然后随着我们扩展平台而继续前进。
We were clear with our language on the site concerning reservations. As a result, we expected little confusion about what was being purchased, our expectations of timing to market, or the terms of purchase for a reservation ticket. Purchasers were not paying for our product at this point, but for their position in a queue for a trial of our new technology. We also included a refund policy to ensure the terms of purchase for your ticket were available. The wait has been long, but not nearly as long as other difficult engineering challenges including Myo that pre-sold their product and were also delayed before successfully rolling out.
Throughout the development cycle we provided updates of our status via posts roadmap page, email to our ticket holders and communications on our social channels. We did our best as a team to open ourselves to questions and maintain a social presence.
At the end of May 2015, we communicated our strategy to execute a series of focused betas that would have seen the platform revealed publicly and incrementally. We were at a stage that parts of the platform needed developer feedback as we rolled these out consecutively.
In the days preparing for our first public beta, we recognized the extent to which our brand had been poisoned by our timing to market. A campaign of negativity that had begun several months earlier with followers and ticket holders had taken its toll on our team, brand, and business.
We believed the beta releases would soon bring an end to the negative talk. On July 8 and 9 we faced further eruptions on social media that reached the tipping point. With the discussion no longer about the product nor its future, this was far more serious.
We failed to bring the product quickly enough for you. As a result, we came to the serious decision to discontinue TideKit and dissolve our company.
We wish to thank everyone involved that worked on the product and with our team. This includes businesses, entrepreneurs and supporters of our vision for app development.
Your TideKit Team
你是对的，TideSDK 今天已经老化并且相当不活跃。你也说得对，我们作为一个核心团队现在完全专注于 TideKit。TideKit 是未来！
如果您想了解我们为何停止开发 TideSDK 并启动 TideKit 的完整故事，我建议您阅读我们的第一篇问答。在那里，您还将找到有关我们如何与 node-webkit 竞争的答案：
https://blog.tidekit.com/post/your-questions-our-answers-01
我们刚刚达到了所有应用程序开发平台所达到的最高 HTML5 分数。如果你想了解更多关于构建的信息，比如你提到的 Windows 和 OS X，你应该阅读这个
桌面构建 https://blog.tidekit.com/post/from-a-desktop-perspective-tidekit-for-tidesdk-developers
这类项目有一个新手：atom-shell基于 nodejs 并用于创建出色的Atom 编辑器
与 node-webkit 的技术差异：https ://github.com/atom/atom-shell/blob/master/docs/development/atom-shell-vs-node-webkit.md
在 JSLA 上关于“Native NodeJS Apps”的演讲：http: //vimeo.com/97881078
如果你看这篇博文，他们会谈论经济形势是多么不可持续
http://www.tidesdk.org/blog/2013/04/11/tidesdk-in-numbers/
而且我找不到说明从一个项目过渡到另一个项目背后的原因的推文。但我想这篇博文不言自明。
无论如何，我正在交付一个用 node-webkit 编写的项目（因为我开始使用 Tide 但出于明显的原因我不得不切换）并且我正在使用 grunt 进行打包，最终并没有那么糟糕。
Electron (http://electron.atom.io/) is the new way to go.
I also had an app running on TideSDK (https://github.com/vinyll/worktimer.titanium) and I'll have to migrate it to Electron.