pouët.net

buckethead: I agree it's hard to tell. it also runs very unsteady (min framerate probably ~1 or 2 fps, max. maybe 30 (if facing a wall)
(no cycle-eating background processes running, of course)
if the player is hit, I can even see the red background repaint (FPS drops down to, dunno, 1 or so in that case). browser window size is 1177x1150. playfield is ~400x260 apparently.

disk I/O started again, btw. reason enough for me to NOT use this browser anymore. whatever is going on there..auto-indexing my a**..

Exactly! I closed it as well. Strange shit.

Have you ever noticed how many I/O Reads firefox does?

Chrome: (1 tab)
============================================
RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total: 6173.8ms +/- 9.3%
--------------------------------------------

FF3 (17 tabs)
============================================
RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total: 5991.0ms +/- 1.5%
--------------------------------------------

am i doing it wrong?

Yes, you can see it in my screenshot on the previous page. Almost nothing compared to Chrome. Note that the firefox instance was already being used for sometime while the chrome instance was just used to browse pouet.net for a minute or so. After that I just left it idling and the IO read was increasing with loads of reads per second.

Response was for imbusy, JSYK.

hermes: :D np. The rendering technique in 3D Tomb II worked reasonably well when I wrote, in the IE5.5/6 days, but touching 2000+ DIV elements is kinda sub-optimal. Anyhow I hope you can still appreciate the size code fu of fitting a basic game play, cramming a few gfx, the generation of the levels and such, etc... . If I were to write a similar game today, it'd be bigger, cleaner, faster ... and wouldn't work in IE at all :p

p01: you rock

missing scroll with middle click and delicious bookmarks

p01: actually I immediately clicked on Play so I did not notice the size-coding aspect of your game ;) so yes, I do appreciate the effort !
I wonder how the script compression works ?! Could you explain, pls ? :)

Hm, tried it and IMHO it isn't that much faster than FF3, in eg. the very objective "scroll the pouet index page up and down like mad" it tends to stutter. And it doesn't have AdBlock (Plus), so it's out of the equation for me anyway.

(as far as I can tell it starts displaying the page eariler than FF, so it feels faster in the beginning, yes)

Then again the sandboxing surely helps plugins run way more stable than in other browsers; especially FF3 has some issues with eg. letting the Flash plugin run reliably.

Same thing with the excessive Read activity here, judging from the Process Explorer output it's the top-level process that does all the IO (the child processes seem to be connected via named pipes only without any file access on their own). Interestingly it doesn't iterate over the whole HD but only has a few files in its dir, AppData and Temp opened, so no idea what the hell is happening there. It's probably fixable.

<< me: have you tried chrome yet?
Owen: na, doesn't support os x
yet
me: Man its amasing.
Sent at 12:46 PM on Wednesday
me: Like floating in a cloud of bigtitted yet slender man friendly lesbians made of candy floss rainbows and joy.
Owen: that actually made me snort

me: Heh.
>>

Its cool how you can grab this text field and resize it to any size you want. Innovation, i havent seen innovation since opera!

Chrome running with processes and cpu graph

Everything "just works" so far, thing appear faster, haven't felt any chugg that i get with other browsers time to time, i am normally a cynical person but this is really fun.

Cool how new tabs opened with middle click are grouped with the site you middle clicked from.

Interface doesnt waste as much space on borders and toolbars yet has all the same functions.

The textarea resize is a regular feature of webkit. It's not exclusive to Chrome.

thec: kinda silly just to pick a browser for mousegestures, eh? i used myie2 a lot ages ago, had proper mousegestures too, got addicted to them.. moved to firefox2, installed an extension for it.. hated it, installed strokeit (freeware mousegestures app, you can even have mousegestures for explorer and whatever other app you like cos it's very customizable, it can learn mousegestures just to the way you actually do them, so yay) and now it's GREAT.

as for chrome.. used it a bit. indeed it's a helluvalot faster than FF3, i thought it ate less mem too, but well, it starts multiple processes so as a sum up it's quite comparable.. havent used it much yet tho, but thusfar i can only say i dislike the downloads-thing and all the floatovers!

I think that the chrome browser will do pretty good on my eee pc :)

it's fucking fast, we tried it with youporn.

I hope they will release an adblocker very soon

nice, writing on the username box in pouet with chrome doesn't work (it keeps deleting it)... copy and paste worked though :)

The cnet javascript benchmark

so what's revolutionary with their javascript vm ?
JIT compiler ?

firefox 3.1 will get something like that too, afaik.

sxrebbel: AFAIK it's about half. So yeah, that's quite good.

jcl: works here...

supported OSes: WinXP, Vista
Guess who's "fucked". Correct, me running Win2k