@landonfuller 1. Mozilla dying fast eating Google dust won't move AAPL or MSFT one inch; 2. Your claim Pepper is "small" = lulz. @rauschma
-
-
@wycats 1: Bundled Flash-in-Chrome. 2: Easier to reflect chromium Web+OS APIs as Pepper C++ than to JS/IDL-ize and stdize.@landonfuller -
@BrendanEich@landonfuller more browsers working on pepper would slow down the process same as any web spec unless every1 kowtowed to Google -
@wycats Not just kowtow: C++ code overspecifies, other browsers cannot port chromium or reverse-eng bug4bug compat w/o dying.@landonfuller -
@BrendanEich@landonfuller indeed. This was the story with "SQLite in the browser" - thankful to Mozilla for calling out spec limits on that -
@wycats@brendaneich That's actually the problem; the stack is limited to the degree that you need the browser vender to let you use SQLite. -
@landonfuller No,@wycats' point was that SQLite was like Pepper: single-vendor-impl, code-not-spec, bug4bug compat non-standard. -
@wycats@brendaneich Needing vendor support at all for SQLite is the deficiency of the big gap between vendor vs. developer exec environment - 7 more replies
New conversation -
-
-
@wycats Right. If Google took all the talent it threw at *NaCl/Pepper/Dart and worked on shorter-path Web evo, we'd have hyper-native web. -
@wycats I heard about Dart in 1H2010, already going; could have had bignums (Dart int) in ES6 if someone at G bothered to disclose/champion.
End of conversation
New conversation -
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.