Skip to main content

Home/ Future of the Web/ Group items tagged webapps

Rss Feed Group items tagged

Gary Edwards

Brendan's Roadmap Updates: Open letter to Microsoft's Chris Wilson and their fight to s... - 0 views

  • The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
  • In my opinion the notion that we need to add features so that ajax programming would be easier is plain wrong. ajax is a hack and also the notion of a webapp is a hack. the web was created in a document centric view. All w3c standards are also based on the same document notion. The heart of the web, the HTTP protocol is designed to support a web of documents and as such is stateless. the proper solution, IMO, is not to evolve ES for the benefit of ajax and webapps, but rather generalize the notion of a document browser that connects to a web of documents to a general purpose client engine that connects to a network of internet applications. thus the current web (document) browser just becomes one such internet application.
  •  
    the obvious conflict of interest between the standards-based web and proprietary platforms advanced by Microsoft, and the rationales for keeping the web's client-side programming language small while the proprietary platforms rapidly evolve support for large languages, does not help maintain the fiction that only clashing high-level philosophies are involved here. Readers may not know that Ecma has no provision for "minor releases" of its standards, so any ES3.1 that was approved by TG1 would inevitably be given a whole edition number, presumably becoming the 4th Edition of ECMAScript. This is obviously contentious given all the years that the majority of TG1, sometimes even apparently including Microsoft representatives, has worked on ES4, and the developer expectations set by this long-standing effort. A history of Microsoft's post-ES3 involvement in the ECMAScript standard group, leading up to the overt split in TG1 in March, is summarized here. The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
munna1357

Crocodile Attack on food people screem around the way. - YouTube - 1 views

  •  
    Crocodiles are brilliant animals. They have been around since the season of the dinosaurs, and they have taken this opportunity to consul themselves into a definitive executing machines. They are bosses of disguise, solid, and if necessary they can abandon sustenance for quite a while. They are the animals of numerous individuals' bad dreams. However, when you are cautious around crocodile domain, you don't need to dread them, you can simply appreciate them for what they are, the guardians of the waterways. What's more, please add to crocodile protection.  The entire group of various species is known as the 'crocodilians'. This incorporates salt-water crocodiles, new water crocodiles, gators, gharials and caimans. At present there are 23 unique types of crocodilians around the globe. The majority of these are imperiled however, in light of the fact that human development is gradually assuming control over their region. This implies lodging improvements are worked around the waterways where they live, and crocodilians are pursued out. This is a disgrace, and unbalances the entire eco-frameworks of these waterways. Numerous other creature species have adjusted to the crocodiles around them, and crocs live by the tenet of the fittest will survive. They eat feeble and wiped out creatures. Crocodile protection is critical and merits much more consideration than it as of now gets.
Paul Merrell

Offline Web Applications - 0 views

  • Abstract HTML 5 contains several features that address the challenge of building Web applications that work while offline. This document highlights these features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML 5 and provides brief tutorials on how these features might be used to create Web applications that work offline.
Paul Merrell

W3C Public Newsletter 2008 06 09 - 0 views

  • W3C launched a new Web Applications (WebApps) Working Group, co-Chaired by Art Barstow (Nokia) and Charles McCathieNevile (Opera Software). This group merges the former Web APIs and Web Application Formats Working Groups. Per the charter for the Web Applications Working Group, the group's mission is to provide specifications that enable improved client-side application development on the Web, including specifications both for application programming interfaces (APIs) for client-side development and for markup vocabularies for describing and controlling client-side application behavior.
1 - 4 of 4
Showing 20 items per page