@landonfuller Suggest you stop fixating on me and my Throne of Skulls, let me get back to my other evil plans. KTHXBYE! @rauschma
-
-
Replying to @BrendanEich
@BrendanEich Bit knavish to deflect criticism on the basis of a lack of authority after strenuously lobbying from that position of authority2 replies 0 retweets 1 like -
Replying to @landonfuller
@landonfuller Skull-note to Skull-self seated on Skull-Throne: add Skull-lobbyists, negotiate 1 MEELION$ kickbacks from AAPL+MSFT next time.2 replies 1 retweet 2 likes -
Replying to @BrendanEich
@BrendanEich The only "skull-throne"-like thing about it is deflecting criticism by claiming the authority doesn't exist.2 replies 0 retweets 0 likes -
Replying to @landonfuller
@landonfuller Criticize my arguments and observations, otherwise you're just failing with the _ad hominem_ fallacy. <3 from my Skull Throne!2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich Unless you're claiming that it's actually impossible for Mozilla to lead standardization efforts without AAPL+MSFT's blessing?3 replies 0 retweets 0 likes -
Replying to @landonfuller
.
@landonfuller Only thing circular here is you on my didn't-even-need-it "authority".@rocallahan on Pepper in 2010: https://mail.mozilla.org/pipermail/plugin-futures/2010-April/000088.html …1 reply 1 retweet 1 like -
Replying to @BrendanEich
@BrendanEich That claim that browser's platform API is "rich" is objectively false by simple comparison to modern platform APIs.2 replies 2 retweets 1 like -
Replying to @landonfuller
@landonfuller@BrendanEich The argument is "make it rich". If Pepper needs new APIs to get there, why skip Web APIs?2 replies 0 retweets 1 like -
Replying to @wycats
@wycats 1: Bundled Flash-in-Chrome. 2: Easier to reflect chromium Web+OS APIs as Pepper C++ than to JS/IDL-ize and stdize.@landonfuller4 replies 0 retweets 0 likes
@BrendanEich @landonfuller Standards take more time because it means they land in all browsers, which is the only time the features matter.
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.