Thanks a lot for this. In introspection it turns out you were right: this was born out of a bit of ignorance on my part. I had no idea of the existence of SailsJS, and that seems like the perfect match for this kind of project, since it automagically creates JSON apis for all your models.
On Monday, 25 March 2013 21:39:37 UTC+5:30, greelgorke wrote: > > derbyjs, sailsjs there are more for sure. we just suspect that the call > for boilerplate is born out of not-exploring. express is simple, and you > totally can write wonderful apps with very few boilerplate with it. but > many people don't want to change their mindset comming from opinionated > frameworks like rails or from clientside stuff like ember or backbone. > thats ok, but don't call for stuff which is already there. it just > look/work different. there are project built on top of express/socket.io. > you can take yeoman and create your singlepage-app based on it AND put a > simple REST-webservice behind to connect a db to your app. there are tools, > including express, exactly for this purpose. > > at the end of the day the very best practice is to create this > boilerplate-generator and publish it and see how much feedback it gets. may > be someone just find out that the boilerplate, he/she created before by > hand, was just an un-ellegant solution, and there are other, making the > generator worthless or even hindering. > > Am Montag, 25. März 2013 16:27:02 UTC+1 schrieb mgutz: >> >> Atypical CoffeeScript is #4 on npm >> >> The guy is specifically targeting single page apps. Backbone is the >> heavyweight king in that space. >> >> Not sure how npm-www relates? >> >> >> On Monday, March 25, 2013 1:53:18 AM UTC-7, Raynos wrote: >>> >>> typical node projects use npm & browserify for frontend. NOT bower. >>> >>> typical node projects use JavaScript. NOT coffeescript. >>> >>> typical node projects don't have grunt boilerplate. >>> >>> Serverside "MVC" is 100% overrated. >>> >>> Usage of backbone on the server is unnecessary, usage of it on the >>> client is completely 100% orthogonal to setting up the "boilerplate" for a >>> typical node project. >>> >>> As for the need for a "boilerplate", one already exists. It's called >>> https://github.com/isaacs/npm-www >>> >>> >>> On Sun, Mar 24, 2013 at 10:25 PM, Prajwal Manjunath >>> <prajw...@gmail.com>wrote: >>> >>>> Hi, >>>> >>>> I was trying to build a web app on express, and on the way I couldn't >>>> help but notice that there was a lack of proper boilerplates encompassing >>>> all major aspects of modern web apps. Now, a typical node project would >>>> use >>>> Bower for client-side library management, Grunt for dev workflow >>>> management. I couldn't find a boilerplate using these. >>>> >>>> Also, most boilerplates leave the entire configuration in one file >>>> (index.js/app.js). This is a nightmare for larger apps, and the lack of >>>> (intuitive) global variable declarations in CoffeeScript compounds the >>>> issue of splitting them into separate files. >>>> >>>> I really felt Node projects need a minimal wrapper around them, much >>>> like Marionette wraps Backbone to provide what most backbone developers >>>> felt were necessary of was best practice.* This is just a callout to >>>> see if anyone else feels the same, and to express interest in a >>>> collaborative project to achieve this.* >>>> >>>> My expectation of such a 'wrapper' would provide the following: >>>> >>>> - Effective ready to use templates for common Bower packages and >>>> Grunt tasks. >>>> - Use coffeescript everywhere. >>>> - A decentralized configuration architecture that minimizes content >>>> in the app entry script(index.js/app.js), and splits config into >>>> several >>>> files based on context. >>>> - Similar architectures to decentralize routes, and sever side >>>> models and controllers. >>>> - A scalable pattern and folder structure for building large >>>> Backbone/Marionette apps. >>>> >>>> And more things as more people offer their inputs. >>>> >>>> -- >>>> -- >>>> 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 nod...@googlegroups.com >>>> To unsubscribe from this group, send email to >>>> nodejs+un...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/nodejs?hl=en?hl=en >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "nodejs" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to nodejs+un...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
