Comments on: Scripty2 in the wiiiild

By: agenceweb

agenceweb — Wed, 17 Feb 2010 09:42:14 +0000

I am sorry to see the scripty, and thus Prototype, made so few changes in such a long time.

By: csuwldcat

csuwldcat — Mon, 21 Dec 2009 23:06:23 +0000

I’m sorry for the vehement defense, but ask yourself this: If someone told everyone in your grad school class that you “basically forked” your thesis from your classmate’s – which you spent months writing, would you be pissed at that person? I am not the guy who wrote the framework, but it is an achievement that took quite a while. To flippantly call it a virtual copy of something else pretty disrespectful in my opinion.

By: Iumentum

Iumentum — Sun, 20 Dec 2009 04:41:53 +0000

OMG, did ajaxian turn into yet another place where we can throw mud at each other? Staring to call each other things doesn’t make you right or look like it for that matter. Actually just gonna make you look stupid instead of someone who knows what he’s talking about. If you can’t keep a discussion on a civilized level it wont matter if you’re right or wrong since you’ll make yourself look ignorant. Did it turn out that while some developers are expanding their knowledge they lose their social skills? Please don’t turn this page into yet another meaningless battlefield of who are right and wrong. We are all here to help and learn from each other not to fight each other.

And oh, by the way, Scripty2 looks pretty good and looking forward to use it on the pages that i work for.

By: icoloma

icoloma — Sat, 19 Dec 2009 11:47:59 +0000

Sorry to get back to the subject at hand,

We have been using scripty2 for a couple of months and this library is awesome. We were a bit afraid about porting our legacy code from script.aculo.us, but it was a breeze.

About the background thread, the only incompatibility I have ever found is between Prototype and Mootools. According to our experience, Prototype works fine with the rest.

By: BenGerrissen

BenGerrissen — Thu, 17 Dec 2009 20:47:03 +0000

ps. Scripty looks dandy ;) keep it up.

By: jdalton

jdalton — Thu, 17 Dec 2009 20:01:28 +0000

@Thomas Fuchs – I totally dig the added controls and Themeroller support, I think it’s a really clever idea.

@Post Hijackers – I think we can all agree that MooTools was heavily inspired, not a true fork by definition, by Prototype as were others. Early MooTools builds included Prototype’s copyright notice and used much of the same API such as bind, bindAsEventListener, delay, $A, $, Object.extend, capitalize, camelCase (camelize), trim (strip), has/add/remove/toggleClassName, get/setOpacity/, get/setStyle, Ajax.getTransport, toQueryString (serialize, Object.toQueryString)
.
http://web.archive.org/web/20061021175741js_/mootools.net/mootools.js
.
And continues to be inspired by Prototype/Scriptaculous as MooTools More API has min, max, stripTags, repeat (times), parseQueryString (toQueryParams), Sortables (Sortable.create)
.
Credit was clearly given and that’s a good thing :D
.
http://web.archive.org/web/20061024032526/http://mootools.net/
.
None extend the Object.prototype. Any framework that extends dom or native objects will have naming collisions and/or 3rd party problems. It’s the nature of the beast.

By: Appletalk

Appletalk — Thu, 17 Dec 2009 17:43:04 +0000

jQuery in 2006: http://cld.ly/d1tgp

By: Appletalk

Appletalk — Thu, 17 Dec 2009 17:41:00 +0000

This is the first time I hear MooTools being called a Prototype fork.
.
We all take ideas from everyone. That’s what Open Source is about. MooTools takes from Base2, Prototype. Prototype takes from us, http://www.prototypejs.org/2009/2/16/pimp-my-code-1-element-storage, and that’s wonderful. And everyone has been credited when credit was due.
.
Obviously you weren’t around at the time to know about these things. Quoting slides, and removing the word `spiritual`, doesn’t help you look serious.

By: BenGerrissen

BenGerrissen — Thu, 17 Dec 2009 11:01:39 +0000

I think *fork” is a wrong term when discussing js frameworks. We all copy bits code from eachother, open source to the core.
.
@ExtAnimal, wrong. All people who yell *woo another wheel* should be forced to ride a horse and carriage as obviously they don’t believe in innovation.

By: ExtAnimal

ExtAnimal — Thu, 17 Dec 2009 09:12:52 +0000

woo.

Another wheel.

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 01:26:15 +0000

Oh, and I officially call shenanigans on your lack of response to the letmegooglethatforyou link that you prompted with this line: “Google is your friend” – Thanks for that insight Jadet, I am after-all in the process of “growing up”, so as you can imagine I’m trying to get healthy portions of milk, Wheaties, and your advice on googling shit that I KNOW like the back of my hand.

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 01:17:27 +0000

Will do guy who makes sweeping-and-provably-false-claims about a framework he likely uses infrequently or never – right back at ya slick! ;)

By: Jadet

Jadet — Thu, 17 Dec 2009 01:03:39 +0000

@csuwldcat: Spending less time trolling around wasting people’s time might help you to dig around and learn a thing or two, have fun growing up ;)

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 00:39:59 +0000

Just for your own investigatory curiosities, here is the link that shows what “everyone” supposedly thinks on this issue: http://lmgtfy.com/?q=mootools+fork+of+prototype

And that’s the Word. :))

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 00:35:28 +0000

@All other than Jadet -
Just so you all know what Jadet mean by “everyone” I searched for these queries on Google, mootools fork of prototype – mootools “fork of prototype”, and found a single Google Groups post, the slide that Resig made, and this article *this.inject(‘irony’)* that claimed anything along the context that Jadet is claiming. In conclusion: “everyone” to Jadet is Resig, one guy on a Google Group, and himself – lol, you have to be kidding me son…

By: Jadet

Jadet — Thu, 17 Dec 2009 00:28:05 +0000

@csuwldcat: It’s not a single developer that calls it a fork, everyone called it a fork at the time and a lot of people still do. Google is your friend. If you’d been paying attention you would have known what I ment with Mootools starting out as a Prototype fork and saved yourself the trouble coming across as an ignorant jackass.

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 00:22:49 +0000

Wow, I made about 50 typos in that comment, please forgive; that’s what typing comments from a stupid phone gets me! :P

By: csuwldcat

csuwldcat — Thu, 17 Dec 2009 00:20:16 +0000

@Jadet –
So because Resig says fork has many variants YOU get to decide which to apply to what a framework developer says? Uhhh, why not go with reality instead actually find out the facts instead. The Mootools author was initially inspired by Prototype and did not fork it, and “spiritual fork” sounds a hell-of-a lot closer to “inspiration” than “copy” to me hombre. You can *say* whatever you want, that doesn’t change the facts what the reality is.

Call me crazy Jadet, but I am going to go ahead and stick with this *generally accepted* version of what “fork”means as opposed to what a SINGLE developers puts on a slide, maybe you should think about what you label other frameworks as be for doing so: http://en.wikipedia.org/wiki/Fork_%28software_development%29

By: Jadet

Jadet — Wed, 16 Dec 2009 23:28:39 +0000

@csuwldcat: You should have a look at your caps-lock, and check Resig’s slides to see how broad the meaning fork is. At the first release of mootools everybody called it a Prototype fork, it’s pretty obvious that with that we don’t mean changing a few things around and giving it a new name. Next time you start calling people ignorant you might want to make sure you know what you are talking about.

By: csuwldcat

csuwldcat — Wed, 16 Dec 2009 22:52:11 +0000

@ Jadet + driverdave: When it comes to compatibility, Mootools releases the $ fn when it detects it on init, it falls back to document.id() for this functionality.

Conflicts occur more frequently with Prototype because they modify the Object native which is a compatibility non-starter under some conditions.

Other than that, there is jQuery’s noConflict() which helps mitigate conflict issues with most libraries that don’t detect collisions inherently as Moo does.