I wholeheartedly support this proposal. +1000.
From: Yehuda Katz wyc...@gmail.commailto:wyc...@gmail.com
Date: Wed, 16 May 2012 00:32:51 -0400
To: public-webapps@w3.orgmailto:public-webapps@w3.org
Subject: Shrinking existing libraries as a goal
Resent-From: public-webapps@w3.orgmailto:public
On Wed, 16 May 2012 06:32:51 +0200, Yehuda Katz wyc...@gmail.com wrote:
In the past year or so, I've participated in a number of threads that
were implicitly about adding features to browsers that would shrink the
size of existing libraries.
Inevitably, those discussions end up litigating
On Thu, May 17, 2012 at 4:03 PM, Julian Aubourg j...@ubourg.net wrote:
I've been meaning to do a test suite to help provide guidance to
implementors (something I figure would be much more useful than yet another
round of specs) but I admit I haven't got to it yet.
In general, this is probably
[I haven't been near my computer in a long time now, but I really wanted to
reply to this :) So sorry for the out of context top post.]
Yes! That is the best thing ever. Someone at Opera is currently looking at
updating our testsuite (which I promised to upload to the w3 test server at the
On Thu, May 17, 2012 at 3:21 PM, Yehuda Katz wyc...@gmail.com wrote:
I am working on it. I was just getting some feedback on the general idea
before I sunk a bunch of time in it.
For what it's worth, I definitely support this idea too on a general
level. However as others have pointed out, the
On 5/17/12 7:03 PM, ext Julian Aubourg wrote:
To me the biggest abomination of all is
Just a reminder that WebApps' [PubStatus] page enumerates all of its
specs and for each spec, there (or will be): a) a link to the spec's
Bugzilla component; b) a link to the spec's Test Suite.
Finally,
[ My previous response was accidentally sent before it should have been
(delete it) ... ]
On 5/17/12 7:03 PM, ext Julian Aubourg wrote:
To me the biggest
Comments on all of WebApps' specs are always welcome, regardless of
where the spec is in the W3C's Recommendation process.
I've been
A related TL;DR observation...
While we may get 5 things that really help shrink the current set of
problems, it adds APIs which inevitably introduce new ones. In the
meantime, nothing stands still - lots of specs are introducing lots of new
APIs. Today's 'modern browsers' are the ones we are
On May 17, 2012, at 10:58 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, May 17, 2012 at 3:21 PM, Yehuda Katz wyc...@gmail.com wrote:
I am working on it. I was just getting some feedback on the general idea
before I sunk a bunch of time in it.
For what it's worth, I definitely support
To me the biggest abomination of all is the XMLHttpRequest object:
- the spec is probably one of the most complex I've seen
- yet, vast portions are left to interpretations or even not specified
at all:
- the local filesystem comes to mind,
- also every browser has its own
FYI, a Script Library Community Group (Cc'ed) was formed some time ago
and it may have some similar interest(s)
http://www.w3.org/community/scriptlib/ (although their mail list
archive indicates the CG isn't very active).
Perhaps someone in that CG has some comments on Yehuda' email.
-AB
On Thu, May 17, 2012 at 9:31 AM, Scott González scott.gonza...@gmail.comwrote:
I'm sure Yehuda can speak more to the status of scriptlib, but the way I
see it is:
There was a some buzz about scriptlib and the W3C being excited about
developers participating via CGs.
Very few developers
On Thu, May 17, 2012 at 9:29 AM, Rick Waldron waldron.r...@gmail.com wrote:
Consider the cowpath metaphor - web developers have made highways out of
sticks, grass and mud - what we need is someone to pour the concrete.
I'm confused. Is the goal shorter load times (Yehuda) or better
developer
On Thu, May 17, 2012 at 6:29 PM, Rick Waldron waldron.r...@gmail.com wrote:
[...]
FWIW, we have bugs filed against DOM for both better event
registration and constructing of event targets:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16491
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16487
On Thu, May 17, 2012 at 1:05 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, May 17, 2012 at 6:29 PM, Rick Waldron waldron.r...@gmail.com
wrote:
[...]
FWIW, we have bugs filed against DOM for both better event
registration and constructing of event targets:
On Thu, May 17, 2012 at 9:56 AM, John J Barton
johnjbar...@johnjbarton.com wrote:
On Thu, May 17, 2012 at 9:29 AM, Rick Waldron waldron.r...@gmail.com wrote:
Consider the cowpath metaphor - web developers have made highways out of
sticks, grass and mud - what we need is someone to pour the
On Thu, May 17, 2012 at 10:10 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, May 17, 2012 at 9:56 AM, John J Barton
johnjbar...@johnjbarton.com wrote:
On Thu, May 17, 2012 at 9:29 AM, Rick Waldron waldron.r...@gmail.com wrote:
Consider the cowpath metaphor - web developers have made
Yehuda Katz
(ph) 718.877.1325
On Thu, May 17, 2012 at 10:37 AM, John J Barton johnjbar...@johnjbarton.com
wrote:
On Thu, May 17, 2012 at 10:10 AM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Thu, May 17, 2012 at 9:56 AM, John J Barton
johnjbar...@johnjbarton.com wrote:
On Thu, May
So, out of curiosity - do you have a list of things? I'm wondering
where some efforts fall in all of this - whether they are good or bad
on this scale, etc... For example: querySelectorAll - it has a few
significant differences from jQuery both in terms of what it will
return (jquery uses
On Thu, May 17, 2012 at 2:35 PM, Brian Kardell bkard...@gmail.com wrote:
So, out of curiosity - do you have a list of things? I'm wondering
where some efforts fall in all of this - whether they are good or bad
on this scale, etc... For example: querySelectorAll - it has a few
significant
On Thu, May 17, 2012 at 2:47 PM, Rick Waldron waldron.r...@gmail.com wrote:
On Thu, May 17, 2012 at 2:35 PM, Brian Kardell bkard...@gmail.com wrote:
So, out of curiosity - do you have a list of things? I'm wondering
where some efforts fall in all of this - whether they are good or bad
on
On Thu, May 17, 2012 at 3:21 PM, Brian Kardell bkard...@gmail.com wrote:
On Thu, May 17, 2012 at 2:47 PM, Rick Waldron waldron.r...@gmail.com
wrote:
On Thu, May 17, 2012 at 2:35 PM, Brian Kardell bkard...@gmail.com
wrote:
So, out of curiosity - do you have a list of things? I'm
Has anyone compiled an more general and easy to reference list of the stuff
jquery has to normalize across browsers new and old? For example, ready,
event models in general, query selector differences, etc?
On May 17, 2012 3:52 PM, Rick Waldron waldron.r...@gmail.com wrote:
On Thu, May 17,
I am working on it. I was just getting some feedback on the general idea
before I sunk a bunch of time in it.
Keep an eye out :D
Yehuda Katz
(ph) 718.877.1325
On Thu, May 17, 2012 at 3:18 PM, Brian Kardell bkard...@gmail.com wrote:
Has anyone compiled an more general and easy to reference
On Tue, May 15, 2012 at 9:32 PM, Yehuda Katz wyc...@gmail.com wrote:
In the past year or so, I've participated in a number of threads that were
implicitly about adding features to browsers that would shrink the size of
existing libraries.
Inevitably, those discussions end up litigating
On Wed, May 16, 2012 at 9:53 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
I think it's a great idea. Shipping less code over the wire seems like
a win from any perspective.
How about a cross-site secure (even pre-compiled) cache for JS
libraries as well? We almost have this with CDN now,
In principle, I agree with this as a valid goal. It's one among many
though, so the devil is in the details of each specific proposal to balance
out this goal with others (e.g. keeping the platform consistent). I'd love
to see your list of proposals of what it would take to considerably shrink
In the past year or so, I've participated in a number of threads that were
implicitly about adding features to browsers that would shrink the size of
existing libraries.
Inevitably, those discussions end up litigating whether making it easier
for jQuery (or some other library) to do the task is a
+1
We've been saying this for a long time on the PhoneGap team. Indeed,
it is happening, as evidenced by libs like xuijs and zepto, but having
a stated goal and formal process to monitor and respond to community
hacks, shims, libs, and practices would be great.
On Wed, May 16, 2012 at 6:32 AM,
Yehuda Katz
(ph) 718.877.1325
On Wed, May 16, 2012 at 12:43 AM, Brian LeRoux b...@brian.io wrote:
+1
We've been saying this for a long time on the PhoneGap team. Indeed,
it is happening, as evidenced by libs like xuijs and zepto, but having
a stated goal and formal process to monitor and
A few questions:
1. What is the definition of a modern browser that we could build data
against?
2. Is this a line-in-the-sand kind of effort? (meaning libraries become smaller
but limited in browser compatibilities).
On May 15, 2012, at 9:46 PM, Yehuda Katz wrote:
Yehuda Katz
(ph)
31 matches
Mail list logo
