Good God... I think the most entertaining part of this is watching how much processor it takes up. It's regularly hit over 100% on my Mac Pro tower using a recent build of Chromium.
Worked fine on my Macbook Pro, the fan didn't even come on.
Arcade Fire meets HTML5
11–20 of 55 posts
Re: Arcade Fire meets HTML5
#12Takes minutes to load, CPU at 100%, form over function; aren't these all the same critics Flash receives?
Re: Arcade Fire meets HTML5
#13Re: Arcade Fire meets HTML5
#14I didn't have any issues running it in Chrome. Loading rather quickly and stayed responsive the entire time even though I have quite a bit running on my dev box right now (Eclipse, SQL Server, Visual Studio, Skype, etc).
Anyway, I thought it was cool. The effect was somewhat lost on me, howerver, as the community I spent most of my childhood years in is what many people think of when you ask them to imagine a stereotypical redneck trailer park: dirt roads, "mobile" homes that should be condemed, broken down cars on cinder blocks, couches in the front yard, etc. I was still impressed though.
Re: Arcade Fire meets HTML5
#15This is very trippy and will take some time to process. Part of me is in revolt: "You shouldn't be able to make a film about me and my house!" And yet, I know that it's not about me or my house per se.
Yet this is clearly a portent of things to come: when everything I see is 'about' me.
For instance, when people cull Street View data (or something similar) to identify houses with wood siding, and send direct-marketed advertising with a "before" and "after" photos of the house with aluminum siding or fresh paint. I could potentially identify east/west facing houses and market shade trees or awnings.
My movies could be similarly contextualized: living in LA I get to see a lot of architecture I recognize since so many films are made here. So I see Fox Plaza in Die Hard or Fight Club. Why shouldn't Des Moines residents see 801 grand topple, instead?
And the ending, as trees 'reclaim' the space? I've often wondered what people might think if they were to return to this place following a catastrophic collapse of civilization. Now I have a visual inkling of what they might see.
There's something interesting going on here that more insightful minds will hopefully digest.
Re: Arcade Fire meets HTML5
#16Slideshow on my Intel Core 2 E5400 with the latest version of Firefox.
If this is the best HTML 5 has to offer over Flash, color me not impressed.
EDIT: There seems to be something wrong with Firefox on my computer. It doesn't seem to want to update HTML canvas properly unless I'm actually moving the mouse around in the canvas. Might have something to do with it. Weird...
Re: Arcade Fire meets HTML5
#17Slideshow on my Intel Core 2 E5400 with the latest version of Firefox. If this is the best HTML 5 has to offer over Flash, color me not impressed. EDIT: There seems to be something wrong with Firefox on my computer. It doesn't seem to want to update HTML canvas properly unless I'm actually moving the mouse around in the canvas. Might have something to do with it. Weird...
I would hold off judgment till when HTML5 gets properly hardware accelerated.
Re: Arcade Fire meets HTML5
#18Takes minutes to load, CPU at 100%, form over function; aren't these all the same critics Flash receives?
Uh... it's art. It's supposed to be form over function.
Re: Arcade Fire meets HTML5
#19Bah. No Street View in Germany yet.
Tried London. Interesting, though the trees did apparently grow through cars. I certainly would be happy if there was more content like this.
Re: Arcade Fire meets HTML5
#20Very cool, though it would be about 114% better if they used just normal divs inside a single window.
If you manage to navigate away from the browser, good luck restoring the state.
Also why to spoil beautiful content by putting chrome (lowercase) around it?