for me, it's more than freedom, but also an approach comes close to true modularisation: unix-philosophy. it's in node its rebuild with one-function-modules a la substack + simple but powerfull and flexible interface convention: callbacks + streams. if i think i need an application server, i'd rather go back to jee, ror or even .net if it fits my task.
but we for sure need some help in finding the right modules. Am Samstag, 15. Dezember 2012 19:52:04 UTC+1 schrieb Mark Hahn: > > I'm sure many would appreciate such a comprehensive large framework. > I and many others in the node community would not. > > One characteristic of the node "philosophy" is freedom. The freedom > to plug existing small modules together like a lego set. The freedom > to easily write our own modules. The freedom to swap out modules for > others as better ones come along. The freedom to make our > architecture unique while not writing code from scratch or even using > boilerplate. > > If I had to live within the constraints of J2EE or ROR or even > Express, I would find another job. My architecture migrates quickly > from project to project with each one more awesome than the last. Any > existing framework would be outdated within a year as far as I am > concerned. > > It is a new world.. > > On Sat, Dec 15, 2012 at 2:13 AM, Angel Java Lopez > <[email protected]<javascript:>> > wrote: > > Hi people! > > > > Panyasan, very interesting... but I don't see the need of most of your > > items. Maybe you want not an "application server" (ooops.... I still > > remember J2EE... argg... ;-) but an "opinionated web framework" (like > Ruby > > on Rails wo/model code generation) (in the comments to your post, Geddy > was > > mentioned). > > > > Let's review: > > > > It should also not force a different programming model on developers > (like > > Opa or Meteor), but let you code in plain old asynchronous javascript. > No > > to-javascript-compilation (except optionally). No magic. Just the right > > tools. > > It exists. Node.js + Javascript ;-) > > > > It should have an integrated API for client and server. > > Can you elaborate this? > > > > It should provide a static HTTP server, REST routing, and bidirectional, > > realtime messaging and broadcasting (such as Socket.io). > > Then require('socket.io'); Why "static" for HTTP server? There is > middleware > > for Connect/Express. REST routing: it's not my area, but there are some > > modules. > > > > It should offer async startup/plugin/configuration system like > > Cloud9′sArchitect. > > Easy one (maybe some boilerplate for async support), or someone writing > it > > as a module, then require it; > > > > It should provide an out-of-the box system and API for user & group > > management, registration, access control, Password > storage/retrieval/update > > etc, preferrably with a set of built-in templates that can be used for > > managing the most generic configuration tasks. With this, a pluggable > system > > to use third-party authentication providers. > > ??? A bit: invoicing to users included, paypal system, etc. ;-) Ok, > again, > > it could be resolved with a module. > > > > It should also provide an integrated system of data modeling and > > persistence. I really do not care about database technology. I simply > want > > to store, edit and retrieve my model data. > > I work in many technologies, and all these or not needed, or provided by > a > > library and tools. > > > > t could also have a toolset that would allow you to deploy your > application > > instantly to a cloud provider such as Heroku or Nodejitsu. > > Again, Node.js > > > > Sorry if it sounds harsh, I don't manage English expressions and > variants, > > it's not my mother tongue. But IMNSHO, we don't need all that, unless > you > > like Ruby on Rails and alike (maybe Geddy). > > > > Other opinions? > > > > I think that that is the key point of your post: RoR-like or not > (Node.js > > community (or part of community) actually "prefers" Sinatra-like). > > "Application Server" term confused me. In my jargon, it's related to > things > > where the business logic, application resides, exposed to many kind of > > clients (web, desktop, no web, whatever the future will bring to us, > > etc....) SAP uses that term too, a la J2EE (sorry for mention it again > ;-) > > > > Angel "Java" Lopez > > @ajlopez > > gh:ajlopez > > > > On Fri, Dec 14, 2012 at 10:51 AM, panyasan > > <[email protected]<javascript:>> > wrote: > >> > >> This is not strictly a technical question on node, so please excuse if > >> this is the wrong forum, but if you're interested, I'd like to hear > your > >> opinions on the following blog post: > >> > >> > >> > http://panyasan.wordpress.com/2012/12/10/why-we-need-a-nodejs-application-server-or-writing-boilerplate-considered-harmful > > >> > >> > >> -- > >> 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]<javascript:> > >> To unsubscribe from this group, send email to > >> [email protected] <javascript:> > >> For more options, visit this group at > >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > > > > -- > > 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]<javascript:> > > To unsubscribe from this group, send email to > > [email protected] <javascript:> > > For more options, visit this group at > > http://groups.google.com/group/nodejs?hl=en?hl=en > -- 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
