From: David Mark on
On Jan 11, 3:01 am, Jorge <jo...(a)jorgechamorro.com> wrote:
> On Jan 11, 8:47 am, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote:
>
>
>
> > I can't believe I wrote that. And posted it.
>
> That's because you don't think before you talk.

This from you "Jorge?" When have you ever made sense?

From: Garrett Smith on
David Mark wrote:
> On Jan 10, 8:51 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote:
>> RobG wrote:
>>> Jorge wrote:
>>>> On Jan 9, 2:53 pm, RobG <rg...(a)iinet.net.au> wrote:
>>>>>> (e.g., you don't know
>>>>>> a word of cocoa),
[...]

> Clearly they didn't have a clue. Same for IBM with Dojo and Yahoo
> with YUI.

Yahoo didn't sponsor an external effort. YUI has priority for Yahoo
needs. Don't expect your bugs to get fixed.

I have personally filed bugs on YUI that have gone over 1 year unfixed.
I had a bug regarding fixing e.pageX for UserAction get marked INVALID.

Fixes from YUI come faster if you just patch it. YUI can be forked and
patched, but in order to get those patches accepted back into YUI, you
must first go through a signup process to become a registered external
contributor. Smells like lawyers.

> The Web developers are revolting? Yes, they certainly are.
>
>> I've seen the demos for the 280 north cappucino (same guys).
>
> Yes. As I pointed out some time back, it sucks.
>

That's actually different guys, though. Similar looking code, with the
`YES` and `NO` variables, but different guys.
--
Garrett
comp.lang.javascript FAQ: http://jibbering.com/faq/
From: Garrett Smith on
David Mark wrote:
> On Jan 11, 1:56 am, Ross Boucher <rbouc...(a)gmail.com> wrote:
>>>> I've seen the demos for the 280 north cappucino (same guys). While the
>>>> code is atrocious, they speak and present well.
>>> I contacted them about their demos (which were similarly dismal) ages
>>> ago. They didn't seem to think it was an issue. There seems to be
>>> something of a disconnect between the public and web personas, perhaps
>>> that is what raises my hackles.
>> Just pointing out this error. Sproutcore and Cappuccino have nothing
>> to do with each other. Not sure where this "same guys" idea came from.
>> Also not sure if the rest of these comments are supposed to be about
>> Cappuccino or about Sproutcore.
>
> Doesn't really matter. Have you realized that your developers

[...]

Lets be clear about this first: Ross is working on Cappucino:

http://github.com/boucher/cappuccino

I don't see any jQuery there.

It looks a bit like Sproutcore, but nope! It's Cappucino, not Sproutcore.

Here is his Github master:-
http://github.com/boucher/cappuccino/blob/master/Objective-J/constants.js

var MAYBE = 0.5;

;-D Kidding.

My code comments about making js look like Cocoa apply even more
strongly to Cappucino.
--
Garrett
comp.lang.javascript FAQ: http://jibbering.com/faq/
From: David Mark on
Garrett Smith wrote:
> David Mark wrote:
>> On Jan 10, 8:51 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote:
>>> RobG wrote:
>>>> Jorge wrote:
>>>>> On Jan 9, 2:53 pm, RobG <rg...(a)iinet.net.au> wrote:
>>>>>>> (e.g., you don't know
>>>>>>> a word of cocoa),
> [...]
>
>> Clearly they didn't have a clue. Same for IBM with Dojo and Yahoo
>> with YUI.
>
> Yahoo didn't sponsor an external effort. YUI has priority for Yahoo
> needs. Don't expect your bugs to get fixed.

I don't expect anything from them. I don't care. ;)

>
> I have personally filed bugs on YUI that have gone over 1 year unfixed.

Same for Dojo. And then you see the same stupid bugs biting people over
and over in the tracker. It's madness.

> I had a bug regarding fixing e.pageX for UserAction get marked INVALID.

That's because the code monkeys probably didn't understand what you were
saying. I've seen that more than a few times. :)

>
> Fixes from YUI come faster if you just patch it. YUI can be forked and
> patched, but in order to get those patches accepted back into YUI, you
> must first go through a signup process to become a registered external
> contributor. Smells like lawyers.

Dojo has some similar "CLA" thing. It's all much ado about nothing if
you ask me. Why is anyone bothering with these things?

>
>> The Web developers are revolting? Yes, they certainly are.
>>
>>> I've seen the demos for the 280 north cappucino (same guys).
>>
>> Yes. As I pointed out some time back, it sucks.
>>
>
> That's actually different guys, though. Similar looking code, with the
> `YES` and `NO` variables, but different guys.

My question is, what is wrong with these guys (all of them?)
From: David Mark on
Garrett Smith wrote:
> David Mark wrote:
>> On Jan 11, 1:56 am, Ross Boucher <rbouc...(a)gmail.com> wrote:
>>>>> I've seen the demos for the 280 north cappucino (same guys). While the
>>>>> code is atrocious, they speak and present well.
>>>> I contacted them about their demos (which were similarly dismal) ages
>>>> ago. They didn't seem to think it was an issue. There seems to be
>>>> something of a disconnect between the public and web personas, perhaps
>>>> that is what raises my hackles.
>>> Just pointing out this error. Sproutcore and Cappuccino have nothing
>>> to do with each other. Not sure where this "same guys" idea came from.
>>> Also not sure if the rest of these comments are supposed to be about
>>> Cappuccino or about Sproutcore.
>>
>> Doesn't really matter. Have you realized that your developers
>
> [...]
>
> Lets be clear about this first: Ross is working on Cappucino:
>
> http://github.com/boucher/cappuccino

Oh that's right. He was the keyboard guy. I thought he was the
"creator" of Sproutcore guy that popped up in this thread a week ago.
My mistake.

>
> I don't see any jQuery there.

Duh.

>
> It looks a bit like Sproutcore, but nope! It's Cappucino, not Sproutcore.

Somebody had mentioned that one relied on the other at some point.
Regardless, I've seen both and both are appalling.

>
> Here is his Github master:-
> http://github.com/boucher/cappuccino/blob/master/Objective-J/constants.js
>
> var MAYBE = 0.5;
>
> ;-D Kidding.
>
> My code comments about making js look like Cocoa apply even more
> strongly to Cappucino.

Yes, they are misguided neophytes, just like the Prototype guys were in
2005. They don't understand the language, so they try to make it look
like a language they do understand. It couldn't be a more foolish
strategy for browser scripting as scripts need to be as simple,
lightweight and efficient as possible. How ignorant can these people
be? It's 2010 and they are stocking up on canned misconceptions
(browser sniffs) from years ago. How will that add up to relevance
today (or even then?)