yuvi

6 ms·

1.
by yuvi 16y ago
Safari will strip identical title prefixes in tab names for exactly that case. Perhaps other browsers should copy this.
2.
by yuvi 16y ago
CDBaby and tunecore are pretty close I guess, they'll get you on iTunes and more (physical copies too in CDBaby's case)
3.
by yuvi 16y ago
> You can set the pointer to any address, which includes future stack. This is wrong. Attempting to use random pointers to outside of what your compiler and malloc allocated is undefined. And indeed, aliasing issues like in your example
4.
by yuvi 16y ago
Were you using gcc? I wouldn't be surprised if e.g. MSVC didn't perform that optimization since it doesn't have the pure function attribute.
5.
by yuvi 16y ago
That isn't hardware decode, that's hardware scaling. http://blogs.adobe.com/penguin.swf/2008/05/flash_uses_the_gp... Also, Flash does not use any of the multiple hardware decode APIs on linux yet due to it needing readback support which a
6.
by yuvi 16y ago
You can disable compilation of MPEG codecs if it makes you feel safer. But I don't see what that has to do with my comment.
7.
by yuvi 16y ago
Chrome uses FFmpeg, which already has a good amount of ARM optimizations and is around 10% faster than Theorarm on my Cortex-A8. Maybe it's in the same vein as summer of code?
8.
by yuvi 17y ago
I think cover.jpg came from doom9 [1] I guess robux4 was talking about the old system, which I honestly didn't know existed before you brought it up. If the new system doesn't use the 16 bit format then yeah, it isn't well specified. [1] h
9.
by yuvi 17y ago
No clue what the depreciated version might be, as far as I know what I linked to hasn't changed since sometime around 2005 (which would explain any broken links.) Cover art wasn't specifically defined in mkv I think, but it became standard
10.
by yuvi 17y ago
You can't do that in ogg either, you need the header packets.
11.
by yuvi 17y ago
Flash has never supported VP7, and the only VP6 on youtube was on self-encoded sponsored channels.
12.
by yuvi 17y ago
1. Probably true in that most demuxers don't read matroska tags, but it's standardized (and has been for the past 5 years or so) at http://www.matroska.org/technical/specs/tagging/index.html Whereas ogg metadata is codec-dependant. In pra
13.
by yuvi 17y ago
The 9400 is still active when the 9600 is; you can use both at the same with with OpenCL for instance. And I'd imagine that there's only one video decode ASIC between the two of them, no need to uselessly duplicate hardware.
14.
by yuvi 17y ago
By not overriding Apple's decoder for baseline and main profile H.264
15.
by yuvi 17y ago
The best explanation I've seen is http://www.kaourantin.net/2010/02/core-animation.html when you also realize that for video playback and animation in general, OpenGL > Core Animation > Quartz 2D > QuickDraw for OS X 10.2 and
16.
by yuvi 17y ago
Useful error messages. Even in C gcc is lacking, let alone C++, and I'd imagine that fixing this in gcc wouldn't be/have been much easier than writing clang.
17.
by yuvi 17y ago
Develop all you want for free: as long as you only want to run your application on a simulated iPhone. You can't load apps onto your own device without paying $100/year or jailbreaking. Heck, you can't even use XCode to compile an app for t
18.
by yuvi 17y ago
Elliptic curve cryptography and LDPC codes are two that come to mind. Though afaik the latter hasn't really been improved since ~1960 and were only patented after rediscovering them in 1993, and I have no clue whether progress in elliptic c
19.
by yuvi 17y ago
My guess is that the author wasn't the one who encoded either video, and the guy who did didn't know what hinting meant but enabled it anyway when exporting from QuickTime. (hinting is only ever used by Darwin Streaming Server, and only if
20.
by yuvi 17y ago
Encoding it with a good encoder would require access to the source, which I don't feel like finding if it even exists on the internet. So instead, here's the same file with the junk stripped out: http://www.mediafire.com/?yuwj5zmmw4m
21.
by yuvi 17y ago
Technically, ogg, ogm, ogv, and oga all follow RFC 3533 and can legitimately be called the same file format, namely ogg. The only difference between all those extensions the codecs used; Xiph intentionally left the definition of how to map
22.
by yuvi 17y ago
Tech-wise, I don't remember any devices with a 3.5" capacitive touchscreen + multitouch before the iPhone came out. That was imo the most important hardware feature of the iPhone, given that the "accepted" mode of interaction with similar d
23.
by yuvi 17y ago
Off the top of my head: http://www.axiotron.com/index.php?id=modbook if you want to pretend that Apple makes tablets. http://www.alwaysinnovating.com/ smaller screen and thicker chassis but longer battery life for $300. Various Windows
24.
by yuvi 17y ago
>it's nicely coherent, has nicely orthogonal features Obviously with exceptions, especially with the instructions added after armv4. For instance, the allowed addressing modes vary depending on instruction: ldr allows a 12 bit offset, l
25.
by yuvi 17y ago
There are really two separate issues with SEO: 1. The little legitimate stuff they do that would increase pagerank (better website design, alt text, metadata, etc.) is incredibly overpriced for the actual value, especially compared against
26.
by yuvi 17y ago
I re-read C99, and the reason this is allowed is not because of §6.5.2.2 p10, but rather §6.5.16 p4 as far as I can tell. Though it's weird to me that the expression (x = 2) can ever be evaluated as anything but 2. Also, it's not illegal C,
27.
by yuvi 17y ago
clang gives 7 9 9 7 2 2 as well. gcc gives 7 10 9 7 3 2 when targeting arm. 2,3,7 are all valid possibilities for the 4th and 6th numbers, but apparently gcc interprets the 5th as 2 + 1 somehow, which I can't see as being valid whatsoever.
28.
by yuvi 17y ago
You skipped over 26, 27, and 34...
29.
by yuvi 17y ago
There are a couple reasons you wouldn't know that (for an entire inline asm function): 1. x86_64 vs. x86_32. It's possible that you'd want to use more registers than 32-bit has. In this case, it's usually optimal to use memory operands on x