On behalf of all the idiots that decided to rain on your parade, I would like to apologize. All of you should be ashamed. How dare you insult this young person whose only wish is to share his work with us?<p>In terms of the module, can't really comment much on your code. It looks clean and well written. I'll try and run it during my free time to get a good feel for it. Well done. Now go back and build something bigger.<p>PS. Shoot me an email (in profile). You might enjoy hanging out with the Nuuton team.
Hi all! Thanks for the great feedback. I did realize the title might have been controversial, but I have a small argument for it.<p>A few weeks ago, there was the 14 year old who posted their rad iPhone game on HN. Their post did inspire me to post my own work. I have a tiny hope that someone else who's doing something like I am will see this and post their own work. I doubt it, but you never know! :D
Well done. One question, though: Shouldn't the commands be a list instead of an object? I would think you would want to be sure to keep order for image processing. For instance, I don't want my image down-sized for the web until after all the processing is done to it.<p>The Ecmascript spec leaves the object attribute iteration order undefined (though it appears most implementations iterate in the order attributes are added).
Many didn't like posting the age in the title. Yeah, no one ever words their HN submissions to be inflammatory and get to front page, right?<p>I'll take a million hackers showing their projects and trying to win brownie points with their age than a single freakin smart phone troll blog post any day of the week.
"Wizardry is a task-based library for GraphicsMagick / ImageMagick that focuses on simplicity and getting one thing done right: processing images."<p>Why I like these words: It's not enough to be able to write code, or even to package up a module for a framework. Knowing that you can't do everything, and that you should not try to do everything, with a single module, is a promising sign in and of itself. Having a clear goal to reach makes getting there all the more possible.
Hmmm ... when I was 15, I spent all my time playing ultimate frisbee and riding my bicycle. Except when I was poring over the schematics and ROM code for the 1802-based COSMAC Elf.
Here we go with another one of these "I'm (under 18) and I did x" posts and an equal amount of people complaining why that isn't relevant.<p>But yeah, this is a really cool little module, congrats.
Already at 15 you've done more than (I would wager) most of the people on this site -- you've shipped open source.<p>Congratulations, and ignore the haters. Remember that it doesn't matter what you think or say, it matters what you do. Creating software is more important than talking about it.
Guess I'll leave one of the few comments about the project itself.<p>I'm going to evaluate this when I get home. If it works as described, I think I'll be integrating this into an imaging service we're building. The interface looks great.<p>Keep coding man. This looks really good.
Looks great - nice job!<p>I'm 13 and I've created a node.js command line app (<a href="http://gtmtg.github.com/view-test" rel="nofollow">http://gtmtg.github.com/view-test</a>) and an iOS control (<a href="http://gtmtg.github.com/MGDrawingSlate" rel="nofollow">http://gtmtg.github.com/MGDrawingSlate</a>) among other things, but none of them are nearly this advanced...<p>Again - looks really cool...
One thing to notice about this module is that it's spawning a sub-process out to imagemagic itself. I'm not saying this is good or bad, I'm just pointing it out. There are also other modules that wrap the imagemagic libraries themselves and do not spawn sub-processes. Just be mindful about the different implementations.
This post is a few days old, but I think it would have really limited the amount of criticism if you'd also noted that you work at DIY (a company that is promoting kids and teens to make all sorts of things - programming or otherwise) in the post somewhere (even though technically people can see the name in the URL). It makes a lot more sense to note his age when the company he's working for is specifically trying to help younger generations.<p>Great work regardless, I love everything DIY is doing and it's fantastic they have their target audience in the office!
The font-weight on your link is <i>very</i> close to being too small to be legible - in Opera on Windows - hello to edge case asshats like me!)<p>And my vision is pretty decent.<p>I know you're probably using a default or something, but it's really bothersome to someone like me to read it.<p>Great job on the project itself, though.
Good one! Seriously! For the work you have done according to your age is tremendous. I certainly was not able to do anything even close to it when I was 15. So I'd say, hats off!!
Oh a 15 year old, how cute. So, what about that module? Why is it special enough to be posted to HN?<p>The age is not relevant. Imagine someone of 36 made this module and included his age. If he had gotten into programming at 35 and this was some kick-ass thing, then yeah that would be kinda neat. Now you could have been programming for five years or so, which gives you a big advantage.<p>If you had been twelve or so, then I'd say it rocks. But fifteen is a fine age to develop something.<p>I don't mean to discourage you at all, just let the product speak and not your age.
You know how I know you're 15? Light grey text on a white background.<p>I remember when I was younger and discovering ImageMagick - a perennial favourite for building little tools on top of.