Well I am unsure if I’ll ever really enjoy using JavaScript. But, good thing is that I do not really need it so far, am in the comfortable situation of just trying to do so out of curiosity and for my own entertainment. And after all, given my earlier rant on this, I have to say that by now I made a step ahead…
javascript
JavaScript Library Hell
After being into software development now for almost 20 years, counting in student days, these days I have to admit I spent most of this time, and especially most of my “productive” work on the server side using Perl and Java, with Python and shell scripting always being around as tooling things but never as real first-choice languages. Through these years, also my perceptions of architecture, technology and, actually, using server-sided Java have changed in many ways – from “web-only” applications to more complex structures running inside Java EE application servers to more lightweight structures running as standalone applications embedding HTTP servers or modules listening on messaging systems such as ActiveMQ or XMPP. Another change that happened all along the way is that JavaScript made its way from something everyone loved to hate to something everyone at least seems to want to use for day-to-day work. And while, after taking a few deep dives, in some fields I surely do understand this, in others I don’t at all…
a clueless start to node.js
node.js is a technology that has been on my “to-try” stack of technologies for quite a while now. There has been quite some fuzz out there recently regarding this framework, and as so far I wanted to have a closer look on what’s possible in JavaScript outside the browser, anyway, it seemed a good reason for dealing with something “new” just for the sake of it, even without immediately having any meaningful use cases at hand… Read on. 🙂