« part 1 « part 2
Part 3 – Hacking the library
Code libraries essentially provide abstraction. Abstraction is good. But anyone who regularly uses third party code in their work has at some point hit the knowledge wall; that point where the abstracted nature of the library leaves you helpless in resolving an apparent problem. You have limited choices – Wait for a patch, hit the forums, or hack it yourself. The latter is probably the worst thing to do, but deadlines are deadlines. Read more…
I’ve been asked how I generate the JavaScript parse table for jParser, so I’m posting the grammar file here for anyone else who’s interested.
↓ JavaScript grammar file for jParser
Read more…
I’ve received quite a few emails recently asking me where the code is for jParser.
I’ve had to disappoint so far, because it’s not currently available for download. My web analytics also tells me that a lot of people are finding this blog by Googling “php javascript parser“. There’s clearly a need out there, so I’d better do something about it.
I know why I want a JavaScript parser, but what kind of things might you need it for? What API features/functions would you like to see? Please post a comment and let me know. Watch this space for a release, and in the mean time here’s some food for thought …
Read more…
I was thrilled this morning to see a post on TechCrunch about The Death of “Web 2.0“. The death here is of the term, hence the quotes, as opposed to the death of everything we take this term to mean. As you can tell by the sarcastic name of this blog, I hate the term. I hate it for various, mostly pedantic reasons. Read more…
Not being a marketeer or PR guru I’ve been struggling to get JASPA‘s raison d’être across succinctly enough. The elevator pitch is easy; give me a 100 words and your attention and I’ll get the message across. Give me 10 words and I’m useless. Read more…