Um, I still use it daily, on projects new and old. It gets the job done, and
the logo makes me happy.
I charge extra if a client insists on jQuery.
> On May 25, 2017, at 11:04 PM, Bob Ippolito wrote:
>
> I don't think anyone is building anything new on MochiKit at this
MochiKit was started specifically because Prototype didn't suit my needs
and didn't have sufficient docs or tests :)
On Thu, May 25, 2017 at 23:56 Arnar Birgisson wrote:
> Prototype was one of the main contenders towards the end, before jQuery
> took over. When I started
Indeed:
https://github.com/google/closure-library/blob/master/closure/goog/dom/dom.js#L16-L17
So I guess mochikit lives at my new employer too!
ab
On Fri, May 26, 2017 at 5:26 AM, Chaz Gatian
wrote:
> Sounds like there was quite a vibrant community of developers
>
> Sounds like there was quite a vibrant community of developers consuming
>> the framework. I loved digging through the source code.
>
>
I actually stumbled upon this while viewing the JavaScript source in Google
Photos. Surprised to see such an old web framework is still used in
portions
> On 26 May 2017, at 07:55, Arnar Birgisson wrote:
>
> Must say thanks to Bob, Thomas, and Per for putting it out and maintaining.
> It was an enormous value in my work back then,
Ditto.
> and I'm sure that code is still running at my old company.
The code eventually got
Prototype was one of the main contenders towards the end, before jQuery
took over. When I started using mochi it was between it and mootools
however (winter 2005-2006). jQuery, and I think Prototype as well, came
later. I distinctly remember picking mochikit because of its documentation
and module
Whoa. Blast from the past.
Mochi was way ahead of the curve 10 years ago. I used it last around 2009.
At that point jquery had sort of taken the position, as I remember it.
For sake of a bit of code archeology, there were definitely other tool kits
even before Mochi. I think xb (xbrowser?) was