Re: News to Hackers?
- From: David Mark <dmark.cinsoft@xxxxxxxxx>
- Date: Mon, 14 Dec 2009 19:43:03 -0800 (PST)
On Dec 14, 10:14 pm, Ross Boucher <rbouc...@xxxxxxxxx> wrote:
David, this started with you calling me out in this post:http://groups.google.com/group/comp.lang.javascript/browse_thread/thr...
I know that. Nothing personal. I'm just sick of seeing people shoot
themselves in the foot. Mainly because I have to browse the Web too
and their misfires often interfere.
Admittedly, its difficult to follow threads across multiple sites. But
in between that post, the one on hacker news, and this, you've
repeatedly called me a fool, and someone who doesn't know what I'm
talking about.
Bullshit. I called everyone involved in GoogClosure fools (and they
are). WTF are you thinking wasting time on that? And don't get me
started on that other thing. Sproutcore is on the same level as
GoogClosure (i.e. hopelessly outdated).
As for you not knowing what you are talking about. That was in
response to your comment about me on that ridiculous "hacker" site.
The only way I recognized you at all was from your cite.
The question I asked was a related but simplified version of the
problem in the Closure code.
Asked in their forum? Yes, I vaguely remember that.
So, in reality, what I'm saying is you
should have offered *any* alternate approach to that problem in the
original thread, rather than just complain about how stupid I and
everyone on the google closure team must be.
That forum is moderated. Moderators tend to be the lowest common
denominator posters and therefore incapable of moderating
discussions. They should only exist to filter spam. ;)
In response to your comment about the timeout/interval, you're
response to my question now seems to be that you think firing
repeating key events isn't a feature the browser or the framework
should offer.
The browser? How could any piece of software not feature typematic
repeats? As for a script, it's not possible to regulate repeats,
except as I have done with my design. Most mistakes in browser
scripting stem from untenable (and typically over-ambitious) designs.
Stop and think and you will realize that nobody is going to care if
your JS widget exactly matches the OS typematic rate on unprintable
characters (e.g. arrows). The typical JS wodget is lucky if it
initializes without throwing an exception. ;)
In other words, you're just pretending the problem
doesn't exist.
In other words, you are trying to cling to the idea that you weren't
wrong about browser sniffing after all (see also IFrame shims,
translucent PNG's). It won't fly. It hasn't flown since the
mid-90's.
You may not see the utility of having this be a
framework level feature, the fact that it exists in pretty much every
desktop development framework suggests that reasonable people
disagree.
What the hell is a desktop development framework? And reasonable
people would realize that my design does not interfere with typematic
features at all. You can deal with the stream of duplicated keydown
events in your app if you really want to. But I can tell you it is
the wrong strategy (for reasons you seem to be partially conscious
of). ;)
.
- References:
- News to Hackers?
- From: David Mark
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: David Mark
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: Thomas 'PointedEars' Lahn
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: David Mark
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: David Mark
- Re: News to Hackers?
- From: Ross Boucher
- Re: News to Hackers?
- From: David Mark
- Re: News to Hackers?
- From: Ross Boucher
- News to Hackers?
- Prev by Date: Re: Firefox 3.5.5 crapping itself (redux)
- Next by Date: Re: How to change the overall mousepointer?
- Previous by thread: Re: News to Hackers?
- Next by thread: Re: News to Hackers?
- Index(es):
Relevant Pages
|