blocks|key|1952058|text|在这个问题被问到一年半之后，一些更新：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1952059|当比较Express和Flatiron时，首先想到的区别是Express是一个服务器端框架，而Flatiron被宣传为同构，涵盖了服务器端和客户端，因此应该适合于开发传统的服务器端应用程序，客户端单页应用程序以及介于两者之间的所有东西(例如：Derby或Meteor)。然而，我可能找不到任何客户端使用Flatiron的例子，而不是因为缺乏尝试。|offset|length|1952060|有一个an+issue+on+GitHub提供了一个简单的TODO应用程序示例，它已经开放了两年多，(据我所知，在那里阅读评论)你不能单独使用Flatiron构建客户端应用程序，而不添加jQuery、Backbone等东西，因为Flatiron的客户端方面似乎还没有准备好(“我们正在努力。我们还有几个步骤要让它完全同构。”)对于一个从一开始就试图同构的框架来说，这似乎是一个真正的问题。(另请参阅一个相关的TodoMVC问题：Add+FlatIron+example)。|1952061|结论是Flatiron还没有准备好。当它准备好的时候，它可能会比Express涵盖更多的网络开发领域，但是如果一个简单的TODO app+example多年来都不能提供，那就真的很难判断它何时会出现。|1952062|与此同时，有大量的Node框架，很难跟踪它们，所以我现在和将来推荐做的是在GitHub上的Joyent/Node+wiki上看到the+list+of+Web+frameworks，并将它们与TodoMVC项目中的客户端框架进行比较-这两个列表相交的将是涵盖服务器和客户端的框架，并能够在其中编写简单的TODO应用程序-希望有一天能包括Flatiron。|1952063|entityMap|0|LINK|mutability|MUTABLE|url|http://expressjs.com/|1|http://flatironjs.org/|2|http://derbyjs.com/|3|http://www.meteor.com/|4|https://github.com/flatiron/flatiron/issues/5|5|6|http://backbonejs.org/|7|https://github.com/tastejs/todomvc/issues/74|8|http://todomvc.com/architecture-examples/backbone/|9|https://github.com/joyent/node/wiki/modules#web-frameworks|10|http://todomvc.com/^0|0|3|7|0|B|8|1|3D|5|2|3J|6|3|0|3|I|4|2L|6|5|2S|8|6|5Y|K|7|0|1O|G|8|0|1S|Q|9|2O|7|A|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]|$D|1H|E|1I|1|1J]|$D|1K|E|1L|1|1M]|$D|1N|E|1O|1|1P]]|A|$]]|$1|F|3|G|5|6|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]|$D|1U|E|1V|1|1W]|$D|1X|E|1Y|1|1Z]|$D|20|E|21|1|22]]|A|$]]|$1|H|3|I|5|6|7|23|8|@]|9|@$D|24|E|25|1|26]]|A|$]]|$1|J|3|K|5|6|7|27|8|@]|9|@$D|28|E|29|1|2A]|$D|2B|E|2C|1|2D]]|A|$]]|$1|L|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]|X|$5|O|P|Q|A|$R|Y]]|Z|$5|O|P|Q|A|$R|10]]|11|$5|O|P|Q|A|$R|U]]|12|$5|O|P|Q|A|$R|13]]|14|$5|O|P|Q|A|$R|15]]|16|$5|O|P|Q|A|$R|17]]|18|$5|O|P|Q|A|$R|19]]|1A|$5|O|P|Q|A|$R|1B]]]]

Some update after a year and a half after this question was asked:

The first difference that comes to mind when comparing <a href="http://expressjs.com/">Express</a> to <a href="http://flatironjs.org/">Flatiron</a> is that Express is a server-side framework while Flatiron is advertised as being isomorphic, covering both the server side and the client side and as such should be suitable to develop traditional server-side applications, client-side single-page application and everything in between (much like eg. <a href="http://derbyjs.com/">Derby</a> or <a href="http://www.meteor.com/">Meteor</a>). However, I have failed to find any examples of client-side usage of Flatiron, and not for the lack of trying.

There is <a href="https://github.com/flatiron/flatiron/issues/5">an issue on GitHub</a> to provide a simple TODO app example that's been open for over two years and (from what I understand reading the comments there) you cannot build a client-side app using Flatiron alone, without adding things like <a href="http://flatironjs.org/">jQuery</a>, <a href="http://backbonejs.org/">Backbone</a> etc. because the client-side aspect of Flatiron doesn't seem to be ready yet ("We are working on it. We still have a few more steps to go to make it completely isomorphic.") which seems like a real problem for a framework that tried to be isomorphic from the start. (See also a related TodoMVC issue: <a href="https://github.com/tastejs/todomvc/issues/74">Add FlatIron example</a>).

The conclusion is that Flatiron is not ready yet. When it is ready it may cover much more areas of Web development than Express does, but it's really hard to tell when it might be, if a simple <a href="http://todomvc.com/architecture-examples/backbone/">TODO app example</a> couldn't have been provided for years.

Meanwhile there are tons of Node frameworks and it's really hard to keep track of them so what I'd recommend doing now and in the future would be to see <a href="https://github.com/joyent/node/wiki/modules#web-frameworks">the list of Web frameworks</a> on the Joyent/Node wiki on GitHub and compare them to the client-side frameworks on the <a href="http://todomvc.com/">TodoMVC</a> project - where those both lists intersect would be frameworks that cover both the server and the client and are capable of writing a simple TODO app in them - which hopefully will include Flatiron one day.

blocks|key|1738601|text|在我看来，Express与Flatiron的较量显然是由Express赢得的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1738602|目前还没有关于熨斗框架ATM的积极开发。|1738603|请参阅GitHub存储库：https://github.com/flatiron/flatiron。最新版本是2014年9月16日的0.4.2。|offset|length|1738604|熨斗官方网站http://flatironjs.org/宕机了。|1738605|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/flatiron/flatiron|1|http://flatironjs.org/^0|0|0|D|10|0|0|6|M|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

It looks to me that the battle Express vs. Flatiron is clearly won by Express.

There is no active development for Flatiron framework ATM.

See GitHub repository: <a href="https://github.com/flatiron/flatiron" rel="nofollow">https://github.com/flatiron/flatiron</a>.
The last release is 0.4.2 from Sep 16, 2014.

The official flatiron website <a href="http://flatironjs.org/" rel="nofollow">http://flatironjs.org/</a> is down.

Akin to <a href="https://stackoverflow.com/questions/5683916/node-js-express-vs-geddy">this question</a>, "I'm looking for the pros and cons of each framework and why one is particularly useful over the other" (but mostly what Flatiron has to offer, due to the fact that Express is already detailed pretty well in that question).

From my slight experience with Express, it seems to cover just about what you need and no more. Flatiron seems to do that, but much more minimalistically. If you check their <a href="http://flatironjs.org/" rel="nofollow noreferrer">website</a>, you see that they offer around 5-7 main functionalities, compared to the many others included in Express.

Finally, which seems the most promising for a highly-scalable web app(s), and why should I use this or that framework over not using a framework at all?

Node.js Express vs. Flatiron

服务器

GitHub

类似于，“我在寻找每个框架的优缺点，以及为什么一个框架比另一个框架特别有用”(但主要是Flatiron必须提供的，因为Express在这个问题上已经很详细了)。从我使用Express的轻微经验来看，它似乎只涵盖了您需要的内容，仅此而已。Flatiron似乎可以做到这一点，但要小得多。如果你查看他们的，你会发现他们提供了...

问Node.js Express vs. Flatiron
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Node.js Express vs. FlatironEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Node.js Express vs. Flatiron
EN