Comments on: JS.Class 2.1 released

By: elazutkin

elazutkin — Mon, 15 Jun 2009 06:16:12 +0000

Spam is distributed with RSS. Got a virus in your WordPress?

By: ddjohnson

ddjohnson — Mon, 15 Jun 2009 00:24:23 +0000

Here’s a screen grab of the spam:

http://papernapkin.org/pastebin/resource/images/imageEntryId/5680

By: kae

kae — Sun, 14 Jun 2009 20:51:21 +0000

there’s a load of spam hidden in the HTML of this article…

By: Nosredna

Nosredna — Sat, 13 Jun 2009 22:30:45 +0000

How does this compare with Joose? Has anyone used them both?

By: jpedrosa

jpedrosa — Sat, 13 Jun 2009 13:56:31 +0000

If it works alright, it could be just what the doctor ordered for me.

As I write more Javascript, I am getting to the point of wanting to run more of it both at the client-side and on the server-side and the fact that this library is tested with V8 and Rhino etc does tease me to look at it further. I currently use PrototypeJS and its OO support but I have been thinking about even trying to move Prototype’s OO into an independent library but then I do not want to have totally unique code written using it in the world. ;-)

This library’s purposes seem cool, but I am not too sure either… Let’s wait and see. And this is from a Rubyist and Javascripter who is just a tad tired right now, trying to keep his email and news reader in check after days of letting them loose. ;-)

By: loveencounterflow

loveencounterflow — Sat, 13 Jun 2009 12:34:04 +0000

how is this better than using protoclass.js? when i do a little firbeug profiling it becomes clear that the majority of burned cycles is done within one of the protoclass facilities. that, in a physics engine, which *should* spend a lot of time in actual computation, not in code organization beaurocratics. simply: u need a tool to organize your javascript—true, coz js is so atrocius. u need someone to slow your javascript to a crawl—false, coz javascript already is slowed to a crawl, by the browser. i stopped believing in oop some time ago anyhow, so this news is old.

By: jhuni

jhuni — Sat, 13 Jun 2009 05:41:38 +0000

Ya I am sorry there is already like a ton of libraries which do the same type of thing. Personally I would rather use JSAN for modules and Joose for classes. Besides isn’t prototype supposed to make JavaScript like Ruby already? I mean if the community could agree on a single interpreter of Ruby in JavaScript then we would be much closer to solving that problem.

I am sorry I just don’t like the fact that there is so much overlap and reinventing the wheel and this is just another case of a person who decided to do everything himself I mean this doesn’t seem to reuse anything. It is well written and highly documented though.

By: Aimos

Aimos — Fri, 12 Jun 2009 15:59:32 +0000

Guys I have the perfekt idea. IE6 support is all about statistics. If the usage goes below 5% or so even bosses will say, letz ignore the IE6.

All we have to do is, grab a list of 100.000.000 kinda important websites or so. Write a tool which will give clients a chunk of 100 websites, to access for a couple of minutes each and in a few days, with enough Web Developer IE8 pcs. Every statistic of these 100.000.000 websites will have a lot of IE8 PIs and hopefully a very tiny percentage of IE6 access. (Like Seti, could work as Screensaver)

Something like a DDoS attack, BUT with a better background idea. :D

Save a web dev.

By: constantology

constantology — Fri, 12 Jun 2009 13:07:53 +0000

w00t! This rocks!!! Nice work! :^D