@everybody: Thanks for taking time to comment on my post! I really appreciate your input. I still think that there are some misunderstandings, which is my fault, because it seems that I haven't made my intention clear enough. As a summary, let me try to restate my argument - not because I hope to convince you, but to show you that there is a segment of developers that would profit from what I was trying to outline. This segment -- part-time and occasional programmers -- is a minority, yes, but it would be able to contribute valuable stuff in return, when being relieved of "The Boilerplate (c)". ;-)
I did not mean to say that we need something new to replace the existing stuff (express+middleware, mongoose, passport, etc., etc., etc.) with a monolithic new architecture. On the very contrary, my argument was that it could be worthwhile to make something that you, as full-time developers, do for every new of your projects -- the wiring together of all these different parts -- into a collaboratively maintained project, which I labeled (or maybe: misnamed) "application server". The claim is -- and here maybe you would strongly disagree -- that there is a certain amount of application logic that is the very same for 90% of applications, at least the ones I would like to write (see my post). It is not that I am too lazy to do this. I have done it in the past and learned my lesson (see my post). It is that I have too little time to be spending it on a) writing it in the first place, b) writing tests to make sure it is stable, and c) most importantly, maintaining it beyond the time I will be paid (or have free time) to develop the main app. Contracting it out to someone else wouldn't help, because the problem simply shifts. As soon as you stop paying this person (and nobody would be paying her indefinitely), the backend will become obsolete, the libraries used will go out of maintenance, etc, and nobody is there to fix that. So, to sum up: the disagreement is not over whether the node community has already created great tools, which individually will do what I need. It most certainly has. I understand what you're saying is "if you're not ready to do everything yourself (i.e. wire the different modules together), don't be in the business of writing node applications". That is of course a valid opinion, but as I said, I think that a lot of valuable things could be created if one only had to worry about the "real stuff", i.e, the business logic specific to the application, and not to the generic parts. I love coding with JavaScript and NodeJS and really think the JavaScript/NodeJS community and ecosystem are awesome. That is why, even if I had the time for it, I wouldn't want to learn Ruby or switch to Java. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
