71–80 of 144 posts
This characteristic doesn't mean Node is a shark-jumping cancer. Maybe some people just hate JavaScript.
All I have to say: the cycle continues.
Earlier quoted context omitted.
I think this post is about ridiculing the childish behavior of the Node.js fandom. I have to agree that I've never seen anything quite like this before except the Church of St. Jobs. I always thought that we software engineers are reasonable people. But apparently a subset of us aren't. However reluctant I maybe to join in this time-wasting back and forth. I'm just glad that someone has taken the time to point out ju…
I've seen it from the following communities: PHP, Ruby, Perl, Python, Java, C++, C, C#, Haskell, Emacs, Vim, Common Lisp, and Scheme. People are tribal. Some people are attracted to tribes, become attached without really knowing why, and start having the strong urge to fuck with the other tribes. Apparently this was good for the survival of the human race. Perhaps it's a bug now that we should consciously compensate…
Guess what. When the packets come in from the network, they sit in an event queue. When Apache takes a request event, it takes it from a queue and hand off to a process. If you are proxying, the webapp server in the back takes the request events from a queue and hands off to a thread. When you make a DB call, the SQL goes to an event queue and the DB processes them 1 by 1. Real world web apps will always, is always and have always been done in a combination of event queues/threads and processes.
Nothing to see here. Moving on… oh look! Takoyaki!
Earlier quoted context omitted.
Ted hates queues, too. But I don't, so instead of playing tough-guy and picking on random open source communities that don't want me, I get to write cool computer programs. Maybe we should all do the same.
What's his critique of queues?
I don't see how discussions like this signify the decline of NodeJS. Quite the opposite. Lots of people are thinking about how to do this kind of computation the right way, within the context of NodeJS. Honestly this discussion has kind of highlighted how bad almost all other platforms are and how much room for improvement there is.
Actually what I have found it has highlighted is just how many of the Node advocates completely and utterly fail to understand their competition. I really, really wanted to think it was just a few isolated people, but the evidence suggests that the meme that Node is actually some sort of multiprocessing breakthrough has spread further in the last few months, rather than dying out. So let me lay it out for you: Node's…
Popularity will also mean a broad based skill set ready to work for you when it comes hiring time.
Of ever developer who's worked in Ruby, PHP, C#, Blub... they've all had to have their hands on Javascript. So this one-ring-to-rule-them-all isn't necessarily about being the best & most powerful language ... but it's the one that might be easier to hire for.
What of the social cachet attached to working in the "cool" language?
I wrote project in node and I loved it. I learned a mountain about Javascript. And in that respect, it's been a resounding success.
It has even been mildly successful running at ~1000 uniques a day, ~3000pv. In retrospect, it was absolutely the wrong tool for the job. Totally stupid. Should have used PHP & MySQL. (Or even node+mysql for that matter).
Regardless - I'm now a lot clearer on what a good use of node is vs. what a bad use is. (Hooray for deliberate professional practice).
I've read about some other languages that "already do what node says it does" - I've heard "Ruby's twisted something-or-other does that", either LISP or SCALA or something.
But I couldn't work in those languages and simultaneously increase my knowledge and understanding within my current professional practice (in a way that is directly relevant). With node/javascript I am able to get both.
I'm not actually sure if my point is very well made. It's certainly not a rebuttal to what you've said (Or even a very effective redirect for that matter).
I'd love to know more about the other stuff & the competition (as you say), but I was attracted to node. I've only got so many hours a day to program. I've got to start somewhere and picking up node (to me) seemed a really fantastic place to start.
Earlier quoted context omitted.
Ted hates queues, too. But I don't, so instead of playing tough-guy and picking on random open source communities that don't want me, I get to write cool computer programs. Maybe we should all do the same.
What's his critique of queues?
TL;DR - It's not so much about queues, but about stacks, i.e. new software stacks. His proposition is that quite often you're better off with existing systems. He specifically mentions syslog, so you're logging your tasks and then the consumers monitor this log. Prevents data loss and lets you potentially restart lost tasks.
(That's his argument. I'd agree if you'd have to reimplement something like that in the pre-built *MQ solutions, but I don't know enough about all of them, maybe that – and more – is already in there.)
Earlier quoted context omitted.
What's his critique of queues?
It's here: http://teddziuba.com/2011/02/the-case-against-queues.html TL;DR - It's not so much about queues, but about stacks, i.e. new software stacks. His proposition is that quite often you're better off with existing systems. He specifically mentions syslog, so you're logging your tasks and then the consumers monitor this log. Prevents data loss and lets you potentially restart lost tasks. (That's his argument. I'…
I still use queues today, only more judiciously and with the issue of failure states a very well defined part of the design.