This is a heads-up for anyone who's having trouble with Flash in Firefox on Windows after updating the former to 11.3 (which you should, since it fixes a bunch of new security holes).
How well does the non-Flash version of video sites work for you, such as on YouTube or Vimeo? It's always seemed fantastically pointless for video to pretend to be Flash, when it's actually just plain ole H.264/AAC, just within a Flash container.
syswow64
I'm sure that pathname was chosen entirely pragmatically. =:)
Oh, good question! The last time I tried the HTML5 version of Youtube I was still using Firefox 3.6, which was woefully lacking in that department - slow and unusable. Presumably the newer versions will have fixed that; I'll have to give that a try.
I'm sure that pathname was chosen entirely pragmatically. =:)
I'm sure it was. :) But I'm curious now...
Hmm, according to Wikipedia, it supposedly means "Windows 32-bit on Windows 64-bit"; still chose entirely pragmatically, of course. ;) (It sure beats names like "GIMP", too.)
On an interesting if unrelated side note, Wikipedia also notes that "[a] bug in the translation layer of the x64 version of WoW64 also renders all 32-bit applications that rely on the Windows API function GetThreadContext incompatible. Such applications include application debuggers, call stack tracers (e.g. IDEs displaying call stack) and applications that use garbage collection (GC) engines. One of the more widely used but affected GC engines is the Boehm GC. It is also used as the default garbage collector
( ... )
Comments 2
syswow64
I'm sure that pathname was chosen entirely pragmatically. =:)
Reply
I'm sure that pathname was chosen entirely pragmatically. =:)
I'm sure it was. :) But I'm curious now...
Hmm, according to Wikipedia, it supposedly means "Windows 32-bit on Windows 64-bit"; still chose entirely pragmatically, of course. ;) (It sure beats names like "GIMP", too.)
On an interesting if unrelated side note, Wikipedia also notes that "[a] bug in the translation layer of the x64 version of WoW64 also renders all 32-bit applications that rely on the Windows API function GetThreadContext incompatible. Such applications include application debuggers, call stack tracers (e.g. IDEs displaying call stack) and applications that use garbage collection (GC) engines. One of the more widely used but affected GC engines is the Boehm GC. It is also used as the default garbage collector ( ... )
Reply
Leave a comment