connect

Okay, I'm gonna say it: I had to chuckle at the name "Connect", because there is already [0], and _even more so_ with Stripe also naming their user onboarding flow "Express", like [1]. Beautiful work nonetheless. [0] https://github.com/senchalabs/connect [1] https://github.com/expressjs/express

While this looks stellar and having a serializable format is cool too, I am personally not a fan of gigantic configuration files as this. Being declarative is much better than being imperative and configuration files seem like a natural fit for a declarative system, but they lack expressiveness. They are hard to make generic and lend themselves to repetition and fragility (in my experience). I'd say that composition wins over configuration. If you provide a domain specific language with a set of useful primitives, users can leverage it to describe what they want with more flexibility and freedom. For concrete examples within js-land, look at gulp.js[1], connect[2]-style middleware, and JSX[3]. All of them describe their structure with code, in a composable, pluggable, reusable fashion. That being said, with a robust enough representation

Most of the middlewares (like logger) are no longer bundled with Express and must be installed separately. https://github.com/senchalabs/connect#middleware

Koa, if anything, will actually replace connect[1], which is the middleware layer that express is built on top of. And yes, TJ built that too. [1]: https://github.com/senchalabs/connect EDIT: Looks like Express doesn't use Connect anymore. I'm out of the loop.

Here's a few sources I really liked: * Express - https://github.com/visionmedia/express - I don't like TJ's coding style, and general trolling of CoffeeScript, but this is a really great, clean and tiny codebase. (As well as all the connect middlewares - https://github.com/senchalabs/connect) * Async - https://github.com/caolan/async - is very readable. Async is a great library for async ops handling in JS, and it's really neat seeing the implementation patterns. * Ray - is a games DSL in Ruby - https://github.com/Mon-Ouie/ray - I love it, and it's a great read especially if you are interested in DSLs as much as I do. * Jekyll - https://github.com/mojombo/jekyll - really helped me going forward with my ruby skills. It's nice, clean, commented, not too big, and useful. * Redis - https://github.com/antirez/redis - lots of data structure imp

Agreed. I came here to post basically the same line. >without ... trying to create some other application on top of Meteor to sell I hope I dont see millions of dollars of time spent on abstraction and magic, or losing sight of a scientific process or an ability to correct fundamental architectural flaws that would challenge or invalidate the need for or the existence of what is now meteor, just because there has been introduced a fiduciary duty. Introspection on the fundamental usefulness and proper use cases in comparison to competition or existing equivalents is an ongoing dialogue that would be unprofessional to dismiss. Meteor is for everything? I really doubt that. Dont think about proper tools for the job, dont think about how to really scale out javascript architecture or solve that problem without subjectivity, dont think simplic

Unfortunately, this is like comparing apples and oranges. Express provides more robust routing, content negotiation, view rendering and partial support, environment based configuration, etc, etc. I presume if kick.js eventually achieves feature parity with Express, kick.js will incur a performance penalty as much, if not more, than Express. A more fair comparison could be made between kick.js and something lower-level such as connect (https://github.com/senchalabs/connect). Or better yet, between kick.js and a "raw" node http server. Also, the name is somewhat taken: https://github.com/mortennobel/KickJS/

Even something like Connectjs (http://github.com/senchalabs/connect), which isn't even a would get you a lot of the way there. They have a lot of middleware bundled with it, and a lot of people since have written stuff to work with it.

Have you looked at Express[1]? It's a fairly complete and (by now) well fleshed-out framework, and it implements Connect[2], which is a middleware stack for Node.js. The only thing it lacks (and Geddy seems to have) is a way to manage models/validations. [1] http://github.com/visionmedia/express [2] http://github.com/senchalabs/connect