> 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".
That wiring is different for every author. It's different for every project I've done as an author. It's different for every base framework. If you want this you fit right into the target audience of meteor and should probably be using that. Alternatively consider using ruby on rails, it does the things you want reasonably well. > There were a lot of loose ends, the stuff didn't naturally fit each other, and I had to spend more and more time on the "glue code". Your also forgetting that application architecture is application specific. A generic boilerplate won't fit most apps. the reason things dont naturally fit is because you didn't architect your application base based on the application, you tried to use something generic. On Sun, Dec 16, 2012 at 3:31 AM, panyasan <[email protected]> wrote: > 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". -- 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
