Reply to: Tedium

[NorthWestPerm2Contr]

…and I'm out of here

Must be a good feeling in a way....

What are your plans now?

[Kryten]

Oh my word.

Though so.

[Cliphead]

And in < 100 posts

Admin sussed me

[Kryten]

Oh my word.

Pray do tell

[Kryten]

Love the new custom title

And in < 100 posts

Admin must like me

[minestrone]

For example, I wonder how long it would take to develop a fully function message queue, that allows you to inject JS routines via an IOC pattern? Not long.

Oh my word.

[Cliphead]

Just read an article on node. Fantastic concept, but not new. Very powerful indeed. Node is a bit like writing within the windows driver model, in that the request maps to an interrupt, and the response maps to completing the interupt and passing back to user mode.

A bit of a mind shift for regular web devs but once you get your noggin round it you see the world of server development differently.

For example, I wonder how long it would take to develop a fully function message queue, that allows you to inject JS routines via an IOC pattern? Not long.

The first time I've been excited about code in a while. Can't wait to mess about with this tomorrow

Love the new custom title

[Kryten]

+1 on plan B all data collection got moved to Node so we can drop the request immediately with a valid response and then start all the data processing within node itself.

Although I don't think I would want to create an MVC membership based website in it just yet.

Just read an article on node. Fantastic concept, but not new. Very powerful indeed. Node is a bit like writing within the windows driver model, in that the request maps to an interrupt, and the response maps to completing the interupt and passing back to user mode.

A bit of a mind shift for regular web devs but once you get your noggin round it you see the world of server development differently.

For example, I wonder how long it would take to develop a fully function message queue, that allows you to inject JS routines via an IOC pattern? Not long.

The first time I've been excited about code in a while. Can't wait to mess about with this tomorrow

[eek]

With all these new TLDs they should really register .js...

I wish they would. I would pay an absolute fortune for one in particular.

[d000hg]

You just go to nodejs.org and download it

With all these new TLDs they should really register .js...

[eek]

As for Plan B: I'm still doing that in Django to start with, primarily because I like Django. But I'll definitely be turning to Node more often for things like shell scripts and maybe the occasional quick server app.

+1 on plan B all data collection got moved to Node so we can drop the request immediately with a valid response and then start all the data processing within node itself.

Although I don't think I would want to create an MVC membership based website in it just yet.

[MarillionFan]

Last day at ClientCo, and I'm finishing off documentation

There's only so much one can think of to say about fields called "title" or "description". Next time I'm going to use random strings for all method and property names, and make the code as convoluted as I can, so I at least have something to write about - indeed, something to figure out - at the end of the gig

Not documenting until the last day hey!

Bloody fly by night cowboy.

[NickFitz]

How do you find node.js Nick (if you can bear to discuss it now you're not paid to know about it)?

You just go to nodejs.org and download it

Seriously though: I rather like it. I've been working with JS since the days of Netscape Navigator 3, so I'm comfortable with the language and know how to avoid the pitfalls. Of course the interesting thing about Node is the asynchronous environment, which can be a bit mind-bending even if you're used to event-driven stuff (which is basically what it comes down to). I found it was much more manageable if things were decoupled using pseudo-events; so, for example, the callback handler of an HTTP response would just fire off a "dinner's ready" event to which some other component had subscribed, and that helped to prevent the sideways-pyramid-of-doom that a callback-based environment can lead to.

If I was starting this again I'd probably look more closely at some of the recent implementations of promises; jQuery's implementation is apparently rather broken from a purist's point of view, and anyway I wouldn't want to use jQuery in what amounted to a shell script (too much irrelevant DOM-related stuff in there), but I came across some interesting work being done in that field.

As for Plan B: I'm still doing that in Django to start with, primarily because I like Django. But I'll definitely be turning to Node more often for things like shell scripts and maybe the occasional quick server app.

[CoolCat]

I once spent a few weeks debugging a really complex set of multi dimensional bugs. I eventually figured out it was somewhere in a small section of about 12 lines of code. Looking at the comment it said "Hello CoolCat this is your old mate Fred here, I couldnt figure out how to get this to work either, I knew you would get here eventually, sorry mate"

Fred of course had left several months earlier

Those were the days

[d000hg]

How do you find node.js Nick (if you can bear to discuss it now you're not paid to know about it)?