Phase I Voting
From RuntimeWiki
Background
This wiki page lists the Phase I Votes (i.e., the Top 5 Features) from various people.
The various phases and timeline for those phases are listed at the bottom of the home page for this wiki. This wiki page holds the Phase I votes for the various participants in the form of their favorite 5 features. (OK to list any number of features. The number 5 is just an arbitrary guideline.)
After Phase I, the moderators will review the Phase I votes and then reorganize the wiki, possibly trimming some of the features which did not receive many votes.
Phase I Votes: Top 5 Features
Please cast your votes here. The level 2 subsection should list your name. The content of your subsection should list your favorite features. You can use whatever formatting you would like, but a simple bulleted list (eg., as shown in Coach's and Dylan's list) works just fine.
Vote from Coach Wei (Nexaweb)
Coach cast the first votes and selected the following features:
- Better Security for Cross-site Scripts - Obviously important
- Persistent Connections Issue
- 2D Drawing/Vector Graphics - Vector graphics is the differentiator between green screen CICS and PC. The web is still at green screen age at the moment.
- Offline Support
- Rich Text Editing
- JavaScript Pause Release - A big missing feature in Javascript language that can enable so many other things. For example, long running client side JS code currently is not possible because it will simply cause the browser not responding. With "pause", the long running code can give control back to the browser from time to time to avoid this problem. etc etc.
Vote from Douglas Crockford (Yahoo!)
- Better Security for Cross-site Scripts - Nothing else comes close
- Offline Support
- The Two HTTP Connection Limit Issue
- Ajax Toolkit Caching
- DOM Performance
- 2D Drawing/Vector Graphics
- Rich Text Editing
- Video and Audio
Dylan Schiemann (Dojo and Sitepen)
My personal voting would be in this order:
- DOM Performance
- 2D Drawing/Vector Graphics
- Rich Text Editing
- The Two HTTP Connection Limit Issue
- Persistent Connections Issue
- Ajax Toolkit Caching
- Event Transparency API
- Video and Audio
- Offline Support
Bertrand Le Roy (Microsoft)
Bertrand cast votes for the following features:
- Mutation Events
- Better APIs Positioning Styling
- Matching Element Against CSS Selector
- IE "Array" Sub-classing
- Client Element Hash
Kris Zyp (Sitepen)
Kris cast votes for the following features:
- JavaScript Pause Release - reasons explained within feature wiki page
- Issue: Persistent Connections Issue, feature request: XHR Connection Length Advice - provides the most comprehensive solution for the different persistent connection issues
- Issue: Better Security for Cross-site Scripts, feature request: Better IFrames Better Sandboxing and Threading Support (for sandboxing) - This best concrete feature for helping in this area
- Offline Support - Following Gears lead
- Threading Support - Once again, following Gears lead
Andrew Dupont (Prototype)
- Better APIs Positioning Styling (We're forced to do so much math and coerce so many strings into integers... functions to get size and offset should be built-in and intuitive. There's some overlap with CSS Object Model here.)
- Ajax Toolkit Caching (Eliminates one of the least interesting talking points fueling the framework wars — hysteria over file size.)
- Better UI Layout (Find a way for HTML to behave like a declarative UI language [hbox, vbox, spacers, etc.] without compromising semantic purity. Take a cue from CSS layout tables.)
- 2D Drawing/Vector Graphics
- Mutation Events
Sam Lie (jQuery)
- Override Back Button Event (Ajax application breaks the back button, this is due to the
fact the programmers cannot override the back button event to load the correct corresponding previous Ajax content. The same applies to refresh/reload button.)
- CSS Gradient Fill and Blur (Alot of the great visual effects of Flash and Silverlight comes from simple implementation of these APIs. If only CSS had these, we won't need to be relying on hacks of background images and the look and feel of Ajax applications will be on par with Flash/Silverlight.) (JonFerraiolo: There are two new separate feature items, Gradient Fill and Blur Effect.)
- DOM Performance (Poor DOM Perfomance or just poor set of DOM node access API?)
- Rich Text Editing (Why Google Docs still no match for Microsoft word?? Here is why: 1. no built in APIs to handle 'UNDO'. 2. 'createRange' and 'createSelection' doesnt work properly 3. no 'onpaste' event in Firefox. 4. tab to indent and unindent text broken. Simple functionalities that would be easy to implement but takes forever to appear on the browser.)
Krishna Sankar (Cisco)
- Better Security for Cross-site Scripts Need to solve this in a scalable way
- DOM Performance Performance/API/JIT
- Native JSON Parsing Multiple vectors - performance, security and even a better programming model
- The Two HTTP Connection Limit Issue
I will compensate for Dylan's long list by keeping mine short ;o)
Marc Bonnier (NetScript)
- JavaScript Pause Release
- Threading Support
- Offline Support
- Better Security for Cross-site Scripts
- Native JSON Parsing
- CSS Object Model
- Better Testing Support
- "Array" Operation Performance
Brad Neuberg
- The Two HTTP Connection Limit Issue
- DOM Performance
- Better Security for Cross-site Scripts
- Persistent Connections Issue
- Video and Audio
- Component Model XBL HTC
- Better UI Layout
- Threading Support
Samuel Santos (Present Technologies)
I vote for the following features:
- The Two HTTP Connection Limit Issue
- Native JSON Parsing
- Better APIs Positioning Styling
- Offline Support
- Drag Drop Copy Paste
- Persistent Connections Issue
Greg Wilkins (Webtide)
- The Two HTTP Connection Limit Issue - better sharing of the two connections, not an increase in the limit.
- Persistent Connections Issue - avoiding bad pipelines
- Better Security for Cross-site Scripts
- Better IFrames Better Sandboxing
