Yeah I don't think there's anything wrong with what you're saying. It's just that things don't work that way right now.
If you want a full-featured robust SOAP client, you should write one. And you should promote it and have everyone that needs SOAP use your client. Then the next time anybody is looking for a SOAP client, everyone will recommend yours because the soap problem is basically "done". That's usually how it goes. If you're asking why people build their own version instead of contributing to an existing project, I've asked this question myself. It's frustrating sometimes, but it's part of what comes with a period of rapid innovation. There are a couple of reasons I can see for all the NIH. - Building your own module from scratch is a great way to learn node and how the module ecosystem works. - Javascript is flexible and people are opinionated about APIs (low-level vs high-level, declarative, chaining, streaming, etc). - It's fun to build node modules If you're asking why someone in the node community hasn't yet done the hard work on module X to your satisfaction, it's probably because they didn't need it. If you'll excuse the generalization, I think most people using node are forward-looking and prefer RESTful, json APIs to something like SOAP (obviously there are exceptions). If they do have to deal with a legacy system, people build what they need and stop at the point it becomes over-engineering. At that point it's up to contributors to decide what they need and contribute new features. If there are areas with big gaps in terms of modules and features, it's probably because people aren't doing a lot of that with node. And it might mean that the best person to take up that responsibility is you. Finally, there is a part of your frustrations that is shared by lots of people in the community; a better way to discover good modules and to have recommended modules bubble to the top. There is work being done right now to enable that. If you want to hurry it along, maybe Isaac is looking for folks to help. You should ask him. :Marco On Sat, Jun 23, 2012 at 8:41 PM, Radhames Brito <[email protected]>wrote: > > > On Sat, Jun 23, 2012 at 2:07 PM, Ian Lawrence <[email protected]> wrote: > >> Hi >> >> >> > Most project lack the proper documentation. I dont see node.js growing >> > much as long as there is no central leadership of some sort that can >> > impose some standars like, "everything in npm must be documented this >> > way or this other", or "if you are doing the same thing as someone >> > else dont duplicate efforts join that project and help build one >> > robust solution". There are like 5 ORM (most lack support for >> > relational databases) , 3 SOAP clients (none fully featured), 10 RoR >> > clones (all missing one thing that the other has), 8 mailers and so >> > on. So many smart people doing great things but most are not what the >> > could because everyone seems to want to be the next DHH or something. >> >> This command and control form of software development is based on the >> idea that people do what you tell them to do, and if they don’t, you >> yell at them until they do, and if they still don’t, you fire them. >> It's popular in some companies. The problem with this is that people >> don't like it and the people who don't like it (especially with >> something like node) are pretty damn smart and so don't like being >> told what to do. >> It seems better in such cases to let many ideas and implementations >> from many sources emerge and let 'a hundred flowers blossom'. It's >> popular in open source and good developers seem to like it >> >> Well look at how node come to exist, one person come up with a great > solution to a problem, it didnt spawn dozens of async javascript libraries, > developers joined what Ryan was doing and now look at the core library, yet > node is open and the contributors decide how to help solve the different > issues, no one is forcing them, they are organized because they want to > reach the same goal. I know most developers dont need to be told what to do > (specially node which pull some extremely smart people), but if you ask > them to publish projects (via npm) to first meet certain characteristics it > would allow users and contributors support the projects they start. There > are many projects which wont get any contributors and/or users because the > code is illegible and there is no documentation. > > > > -- > 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 > -- Marco Rogers [email protected] | https://twitter.com/polotek Life is ten percent what happens to you and ninety percent how you respond to it. - Lou Holtz -- 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
