Following
Critics call foul as Google takes aim at JavaScript with Dart
Critics call foul as Google takes aim at JavaScript with Dart
Mozilla Launches Open Badges Project
Facebook Launches Subscribe Button for Following Anyone's Public Updates
The HTML5 scoped attribute for styling
Un-fixing Fixed Elements with CSS Transforms
Brendan Eich…
…it looks like that will never see the light of day. That being said, even with all their effort, Google has been ahead of the game for years and with many more resources, making sure that all potential competitors are playing a losing game.
Sadly, this also means all of Christian Heilmann's old geo-mashups are going to die...
Yahoo also let go of Sled, its Node.js experiment. But there's a bit of good news for this one: its name was changed to Postmile …
Dominic Cooney with Google reported on an informal Web Components meetup . The gist of it seems to be that the developers from Mozilla/Apple want something slightly different from their Google counterparts. They would prefer to go ahead with a trimmed version of XBL 2.0, having declarative templates, and a way to extend and augment existing elements. The Web Component proponents wanted to start out with a purely imperative model and basically create elements from scratch. …
…out great last time around... We need competition, we deserve options. Microsoft, Google, Apple, Opera and Mozilla are all vital to the ecosystem of the web; to push each other to become better and to foster innovation that everyone gains from. I work for Mozilla, but I would definitely not want to see Firefox (or Gecko's rendering engine) as the only one out there. We need a balance to together form and grow the future of everyone.
To me, when it comes to just one owner, …
…so. Also, I just want to re-iterate that what's said here are my own thoughts and not those of Google unless expressly stated otherwise.
I've been arguing — mostly over beers — for the last year or so that the W3C needs to find a ways to re-focus on the needs of the constituencies that give it credibility; namely web developers and browser vendors. This tends to fall on frustrated W3C staffer ears as individuals might agree but the organization feels the effects of its failures …
…Robert Nyman
Brendan Eich on Ecma TC39, JavaScript.next, and Google Dash - Brendan Eich discusses the future of JavaScript and thoughts on the Google Dash/Dart initative
If you want to read more tips or discuss the web with Robert, he's available on Twitter as @ robertnyman .
LNUG
The London Node.js User Group occurs on the last Wednesday of every month, in Camden. This month's event is on the 28th of September at 6pm, and has four talks scheduled:
Tom Hall - Webscaling With Node.js
Andy Kent - Streaming Analytics and Node.js
Rob Tweed - The Globals Database: It's Significance To Developers
Garren Smith - These are the ORMs you are looking for
There's a Google Group for keeping up to date with the group: LNUG Google Group .
So what's the deal with Google and JavaScript?
Simply stated, Google is absolutely committed to making JavaScript better, and we're pushing hard to make it happen.
Erik Arvidsson, Mark Miller, Waldemar Horwat, Andreas Rossberg, Nebojša Ćirić, Mark Davis, Jungshik Shin and I attend TC39 meetings, work on implementations, and try to push JS forward in good faith. And boy, does it need a push.
Erik and I have specifically been working to focus the TC39…
…specification in favor of the work Aryeh Gregor has been doing on HTML Editing APIs .
Editing Meeting
A couple of people from Google and Mozilla came together in Canada to discuss the various challenges authors face with editing on the web and how they can be tackled. Ehsan Akhgari wrote a detailed report Future of editing on the web that is well worth reading.
Here is something that the Google leak about Dart ( née Dash) telegraphs: many Googlers, especially V8 principals, do not like JS and don't believe it can evolve "in time" (whatever that might mean — and Google of course influences JS's evolution directly, so they can put a finger on the scale here).
They're wrong, and I'm glad that at least some of the folks at Google working in TC39 actually believe in JS — specifically its ability …