shaver

9 ms·

1.
by shaver 15y ago
Yes, you should block apps that you don't want to see. They are (per your reasonable definition) badly behaved, and you should exclude them from your stream. I think that's exactly the behaviour that FB would want, because it ties the utili
2.
by shaver 15y ago
Can you give me an example? Sites get entered in there if they try to install malware on people's machines. I think it's straight-up ridiculous to say that FB's text there is an attempt to mislead users. It gives good advice that most peopl
3.
by shaver 15y ago
You're right, of course. While I believe that the MPEG-LA's enforcement practices are not non-discrimatory as it's claimed to be, that's a different discussion, and it wasn't appropriate to single x264 out that way. I apologize.
4.
by shaver 15y ago
No, but this is a common misconception. Though the summaries talk about "sold to users", the license itself defines "sale" in such a way as to include zero-cost distribution: "Sale (Sell) (Sold) (Seller) – shall mean any sale, rental, lease
5.
by shaver 15y ago
No, it's noncommercial (really not user-monetized) streaming of video that's free. Shipping H.264 hardware requires paying licenses regardless of whether it's a commercial situation or not. For software, if the patents are enforceable in yo
6.
by shaver 15y ago
It definitely needs nightly. I'm not sure what's up with salmanapk's setup, will need to dig into it.
7.
by shaver 15y ago
Use and distribution of implementations requires a license (though, curiously, x264 seems to get a pass), so using the decoder will require a license as with using a closed-source one.
8.
by shaver 15y ago
Brendan's demo was running at 30fps, I believe on a Macbook Pro (I'll find out). Some content will run slower right now, which is true of all codecs AFAIK but is more so for this stuff right now. The patches linked from the github README ar
9.
by shaver 15y ago
You need Firefox nightly for it to run well, because it depends on the hybrid static/dynamic type inference work and some other optimizations. I believe that Brendan was demoing it from a Mac laptop of some kind. As far as applications, it
10.
by shaver 15y ago
John's a sweetheart, for sure.
11.
by shaver 15y ago
I wonder how one would ever see that it was necessary. Seems a hard hypothesis to falsify, if you will.
12.
by shaver 15y ago
This is a FAQ; I should finish writing the FAQ, clearly. We’re currently aiming at mobile/tablet devices rather than a notebook form factor. We’re looking to expose all device capabilities such that infrastructure like phone dialers can be
13.
by shaver 15y ago
Firefox on Android uses very little in the way of the Java APIs, it's virtually all NDK code. That said, it will certainly require some meaningful adaptation.
14.
by shaver 15y ago
"Also, the web platform isn't ready to be the only platform available for applications." That's the whole point. The web wasn't quite ready to subsume PDF, until people went and tried to do it, found the pieces that were missing, and got t
15.
by shaver 15y ago
MSRC didn't say it's not worth it. They said it couldn't survive the SDL process or be securable, which is the standard for technologies they deploy. Given that they deploy those pre-existing technologies and added more in IE9 (WOFF, acce
16.
by shaver 15y ago
The shader models in XNA D3D and WebGL are pretty similar. One travels as pre-compiled bytecode and the other as text, and there are some differences in how loop constructs work, but they're both basically shader model 2. But the argument
17.
by shaver 15y ago
Based on face-to-face conversations with senior people at GPU manufacturers, I do, yes. You should absolutely decide for yourself; I said what our belief was, and what it was based on.
18.
by shaver 15y ago
The post wasn't from the IE team, but from MSRC, the company-wide security research group.
19.
by shaver 15y ago
My point is that those technologies have been added to browsers, and we've been able to deal with the security surface. Microsoft's position is that WebGL is inherently unsecurable, and therefore somehow qualitatively and fundamentally dif
20.
by shaver 16y ago
[Disclosure: I work at Mozilla, and have been closely involved in the JS engine for some time.] For a while (3.5 and 3.6, I think), Linux distributors shipped 64-bit builds of Firefox, which did not have JIT support. (Mozilla did not produ
21.
by shaver 16y ago
What would an RSS reader good enough for Kroc's grandmother and 419,999,999 other Firefox users look like? I would be genuinely interested in his designs for one. Of the many different RSS reader add-ons I've tried for Firefox, for exampl
22.
by shaver 16y ago
I'd be interested in two things (well, quite a few, but these two especially): any change in FF4b8, and a link to your code or (better) a bug report on the performance issue; we'll get to it after FF4 if it's not already better.
23.
by shaver 16y ago
tl;dr: Mozilla is hiring, and we have many different kinds of positions open. Main offices are in Mountain View, Toronto, Auckland, Paris; remote work very much a possibility, esp for people with experience doing it. I know most about eng
24.
by shaver 16y ago
Neil is one of the world's quietly great people. I had the good fortune of knowing him in high school, and working with him at my first job (Ingenia Communications, running Canada's SchoolNet). He's always been an alloy of incredible inte
25.
by shaver 16y ago
The URL for this item points to my lightly hacked version, but the real thing is at http://www.quasimondo.com/StackBlurForCanvas/StackBlurDemo.h... . (I just made it update when the slider moved, instead of requiring a button press, so th