Boy is the learning curve to the WebIDL spec steep. Thoughts on what would make it more palatable welcome.
-
-
Replying to @tobie
Any particular trouble spots? Or just general "too many moving parts" issues?
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
it's super large. Some of the algorithms are very abstract. Makes it hard to mentally connect them to what they're trying to solve.
1 reply 0 retweets 0 likes -
Replying to @tobie
OK. Large is hard to address, but I'm happy to add informative "what is the goal?" text to things. Please ask as needed!
4 replies 0 retweets 1 like -
Replying to @really_bz @bz_moz
2 others difficulties come to mind: 1. grasping the overall structure, 2. figuring out what the prerequisites are.
3 replies 0 retweets 0 likes -
Replying to @tobie
For #2... Other than the ES spec, are you thinking of something else in this bucket?
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
it would be nice if it could be limited to a subset of the ES spec. "Here are the x things you need to know."
1 reply 0 retweets 0 likes -
Replying to @tobie
Hmm. That would take some thought. Off the top of my head, you don't need to know syntax or regexps, but need to know internal ops
1 reply 0 retweets 0 likes
Gah, and other stuff, but twitter is a sucky conversation medium if the conversation has content. ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.