On 22 jun, 19:58, Mark Hahn wrote:
> Node sounds like a fit to me.
>
> Why do you have workers? Doesn't rails automatically use threads/processes
> to allow multiple things to happen at once? (I know nothing about how a
> rails server works).
>
On the contrary, Ryan used rails as an example o
On 22 jun, 20:04, Ben Noordhuis wrote:
> On Fri, Jun 22, 2012 at 9:32 PM, Radhames Brito
> wrote:
> > I have a medium size application in Rails that is consuming lot of
> > resources because it has to communicate with a SOAP web service, every
> > time the application accesses the service is t
Your rant has a lot of truth to it. But many people in the node community
don't see this as completely negative. Node is still young and it has a lot
of catching up to do in terms of developing a large robust library space.
Having a lot of activity and people reinventing wheels is part of that.
Well, node.js is a bit like the Wild West, before the railroads where
built, and in my book this is a very good thing. Projects get traction or
they don't, based on what people like or dislike. No big hand watching over
us forcing us into doing it in a certain way. Or, more like Shadows and
less li
> I dont see node.js growing much
You must be blind. Node is exploding with no end in site.
--
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
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 don
On Sat, Jun 23, 2012 at 1:12 PM, Mark Hahn wrote:
> > I dont see node.js growing much
>
> You must be blind. Node is exploding with no end in site.
>
>
Yes I agree Node is exploding, but there needs to be standards, I know
everyone is running to it but efforts should be unified.
--
Radhamés
> I know everyone is running to it but efforts should be unified.
I don't agree. This is an evolutionary growth. The petri dish needs to be
able to grow anything. Having a god to design this would be far inferior
to evolution. And allowing some person or persons to dictate the design
would b
Couldn't disagree with you more.
Open environments thrive on small discreet and federated components and not on
central authority. It's closed systems that require more frameworks and widgets
and big SDKs in order to survive and compete against other closed systems.
On Jun 22, 2012, at June 22,
I'm with the evolution camp, but just for completeness sake, it is worth
considering the hybrid Linux model. Any rogue can develop apps, but distros
(i.e. Ubuntu), for better or for worse, tie them all up in a pretty bow (a
lot more involved than npm).
On Sat, Jun 23, 2012 at 5:03 PM, Mikeal Rog
Batteries not included.
I'm the authority.
I'm choosing my authorities.
My wish: An easy way to follow my authorities, preferably via npm
(star command..).
On Sun, Jun 24, 2012 at 3:38 AM, Baz wrote:
> I'm with the evolution camp, but just for completeness sake, it is worth
> considering the h
On Sat, Jun 23, 2012 at 7:58 PM, Mark Hahn wrote:
> > I know everyone is running to it but efforts should be unified.
>
> I don't agree. This is an evolutionary growth. The petri dish needs to
> be able to grow anything. Having a god to design this would be far
> inferior to evolution. And
On Sat, Jun 23, 2012 at 8:03 PM, Mikeal Rogers wrote:
> Couldn't disagree with you more.
>
> Open environments thrive on small discreet and federated components and
> not on central authority. It's closed systems that require more frameworks
> and widgets and big SDKs in order to survive and compe
On Sat, Jun 23, 2012 at 2:07 PM, Ian Lawrence 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
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 l
I personally think the Node community is one of the best I've experienced
for cultural adovcacy: it's just not necessarily evident as a newbie. The
community is diverse and Node itself is young. It also intentionally has a
very a small core, which leaves a lot open for interpretation. Node d
It is very possible that Node never will "mature". Having a zillion
choices may be here to stay. Hopefully it will get easier to find the ones
you need.
Of course the quality of the best modules will improve over time. And some
will dominate when they hit the sweet spot of what most developers
In my mind, "maturing" doesn't mean all the choices go away. It just means
there are some obvious choices that most people agree are the way to go.
This takes time and work. And it means those obvious choices are the first
thing newbs run into when they are considering solutions. This can be
helped
18 matches
Mail list logo
