21–30 of 141 posts
Earlier quoted context omitted.
Oh yuck, they're bringing back the big wasted void along the top of my page? The fact that Firefox replaces the title-bar with tabs is my favorite feature of the darned thing.
https://addons.mozilla.org/en-US/firefox/addon/classicthemer... you're welcome :)
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this using the same amount of processing power as native, or is this "67% as fast as native, using 200% of the CPU as a native solution?" I mean, I realize that processors and machines are only getting more capable. It seems silly to start requiring faster and faster p…
Epic Games and Mozilla are demonstrating how the Web is continuing to evolve as a powerful platform [..] And you're still using a youtube embed because a single, simple tag like is too effin' problematic. Yeah yeah, I get it. isn't relevant to gaming. WebGL and gaming are cool new stuff, is prehistoric crap nobody cares about anymore. The world has moved on.
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this using the same amount of processing power as native, or is this "67% as fast as native, using 200% of the CPU as a native solution?" I mean, I realize that processors and machines are only getting more capable. It seems silly to start requiring faster and faster p…
Especially considering that asm.js isn't really using a JS execution engine. You can smuggle a low-level machine code via any mechanism. As I understand, without asm.js specific optimizations, it doesn't really work. I know, it's a cute way to get some movement without the political nightmare of having to decide on a proper VM for the web. Since it's "just JavaScript", other browsers will run but be really slow, lead…
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this using the same amount of processing power as native, or is this "67% as fast as native, using 200% of the CPU as a native solution?" I mean, I realize that processors and machines are only getting more capable. It seems silly to start requiring faster and faster p…
Earlier quoted context omitted.
Oh yuck, they're bringing back the big wasted void along the top of my page? The fact that Firefox replaces the title-bar with tabs is my favorite feature of the darned thing.
Chrome and current FF have the same "big wasted void" when not maximized. You need something you can grab to drag the whole window about, as opposed to a single tab. It goes away when maximized, and I'd hope Australis will stay the same.
This is neat and all, but I wonder if things are really better moving to "in the browser." The discussion is of "upwards of 60% as fast as native." Is this using the same amount of processing power as native, or is this "67% as fast as native, using 200% of the CPU as a native solution?" I mean, I realize that processors and machines are only getting more capable. It seems silly to start requiring faster and faster p…
For a high level managed language, 67% would be pretty godlike. There are some C programs that are less than 67% the speed of their own -O2 compilations. If 67% native speed winds up being the average efficiency, that's plenty good enough for the vast majority of computing. As recent history has been teaching us, doing more with less has mainly to do with getting more mobile, distributed, and ubiquitous. We're quickl…
Earlier quoted context omitted.
Oh yuck, they're bringing back the big wasted void along the top of my page? The fact that Firefox replaces the title-bar with tabs is my favorite feature of the darned thing.
Chrome and current FF have the same "big wasted void" when not maximized. You need something you can grab to drag the whole window about, as opposed to a single tab. It goes away when maximized, and I'd hope Australis will stay the same.