• A quick rant on web development and elegant solutions

    I think the (over)reaction to Dart, both before and after it's announcement, shows 2 important things.

    1. The web development community is desperately looking for an answer to it's problems.
    2. No solution will be well received unless it involves real change across ALL the major browsers.

    When confronted with these alternative language tools or even the new proposals for ES Harmony, people keep saying "syntax isn't the problem". I personally agree with that, but I'm also realizing it's the wrong mantra to respond with. Syntax is a problem. But it's not the most important one. It's not the one that's causing us the most pain right now. The real problem is browsers. Period.

    Keep Reading A quick rant on web development and elegant solutions »

  • The Node.js Community Could Use Some TLC

    I think everyone here can agree that Node.js is awesome. Along with the commonjs effort, it has intensified the interest in javascript as a server-side language. The combination of asynchronous I/O by default and strong support for easy networking code has proven to be what lots of developers want in a platform. It's exciting and the community is growing every day.

    But with growth comes growing pains. Node has matured as a project. It has a direction and a vision. This has happened organically and not everyone is aware that things are different. And I think we need to start broadcasting that direction and protecting that vision. I got motivated to write this blog post to offer some suggestions that could help ease some of the pain points of the community.

    Most of the node community is centered around the mailing lists (nodejs and nodejs-dev). I've been following the lists since the beginning. First as a lurker, then a more and more frequent contributor. There is lots of activity and some very smart people hang out there and respond frequently to questions. What's even nicer is that Ryan Dahl and other core members actually post frequently to give good info on what's happening with node. In short, it supports the growing node community pretty well in my opinion. At least until recently.

    Keep Reading The Node.js Community Could Use Some TLC »

  • A quick project to create an ebook from html

    Today I got distracted by small project and thought I'd throw up here for others.  I was going through my backlog of online reading material and found this http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-4.html. It's a free, Creative Commons licensed online version of the book Structure and Interpretation of Computer Programs.

    It's one of those books that keeps popping up when people give you advice on how to program better.  And here it is for free!  But due to my fear of a future that includes bad eyesight, I can't try and read this online.  What I really wanted was an ebook version for my handy dandy B&N Nook.

    Alas, Barnes and Nobles wants to charge me for this and so does Amazon. And to add insult to injury, they don't even have the ebook version.  So I set about doing it myself.

    Keep Reading A quick project to create an ebook from html »

  • Updating libxmljs on node.js: or, how to suck less at Google v8

    I just released the latest version of libxmljs for node.js http://github.com/polotek/libxmljs/tree/0.4.0. This is a major release that doesn't have many visible changes but lots of stuff happened under the hood. I figured it'd be good to describe some of my struggles with Google v8

    Debugging Segmentation Faults

    Previous versions of libxmljs were rife with segfaults that would pop up without warning. There are lots of reasons for this, but the most common had to do with not following best practices with the v8 API. V8 has this notion of Handles that are used to hold references to javascript objects in C/C++ space. Among other things, this design decision gives v8 a nice way to keep track of js references and clean them up at the appropriate time. A contrived example (assume v8 namespace).

    Keep Reading Updating libxmljs on node.js: or, how to suck less at Google v8 »

  • Creating a Blog I'll Actually Use

    I have 3 blogs including this one.  And they're all being neglected.  The last post on any of them was 5 months ago.  There are lots of reasons why I don't write more.  Busy at work, social life, good old-fashioned laziness.  But there's only one that activates my programmer's itch.  My blog interface is just not user-friendly enough.

    When I do get the urge to write, nothing derails it faster than getting irritated with the actual writing process.  Getting your thoughts onto paper should be the easy part.  The hard part is ensuring that those thoughts don't make you look like and idiot.

    So this blog post serves 2 purposes.

    Keep Reading Creating a Blog I'll Actually Use »

1 | 2 | 3 | >