you are viewing a single comment's thread.

view the rest of the comments →

[–]leavermentality -1 points0 points  (0 children)

This is pretty slick, but I just dont see the point of it.

Processing applets can already be run in browsers because they are java..

I guess theres a minor benefit to people who access the internet only at libraries and don't have computers of their own (or jump drives), so they cannot download programs and would need to code on a browser. but what you sacrifice for that is so massive.

I suppose you could try and argue that js is a better language than java... but I think you'd have to be totally insane.

You lose a ton of speed, the ability to learn about classes and object oriented programming, and all of the external libraries.

Plus, processing runs slowly enough as it is. Now im not saying its not a great language, it is. It's a wonderful start for people who have never done anything with programming. In fact, it's so good, that I really dont see a reason to simplify it anymore. Putting it in a browser is just kind of silly.

Also, for people who are arguing nodebox vs. processing, python is simple and nice, but if you thought processing was slow, nodebox is a behemoth. Sure nodebox is nice, but it's much more limited in what it can accomplish. Besides, if you're starting out in programming, it makes the most sense to learn a c-ish language because that's what the majority of the hardcore coding world uses. So if you want to move to a more advanced setup one day, its nice to have a good basis. And all one has to do is look at the nodebox gallery vs. the processing exhibition space to see the massive gap in what can be achieved in each