Comment Re:Wait, that's not right... (Score 2) 140
At least the OS will be up-to-date...
I figured Apple's intention is to thwart spammers; if you were able to recognize the real name of your buddy you were more likely accept the invitation rather than someone with a username like "THISISNOTVIAGRASPAM." Playing the whole social angle.
What Blizzard was intending was different. They wanted to put paper trail on all users on a publicly viewable form, in the interest of minimizing trolls and thus improving the quality of posts on their forums - to 'shame' the trolls from posting mindless drivel. Yeah, that didn't work out too well.
They're just desperate to find SOMETHING it'd good for.
Up untill you read a future article about the millionaire developer that made his riches making the first Whoopee Cushion iPad app.
Heh, the first thing I was thinking of was "$750" and not "$7.50"
Guess I know a lot of boardgamers
Man, I should have read the article. FTFA:
Note that the implementation for Internet Explorer 8 does not use the HTML5 canvas element, because this isn't supported. Freeciv.net implements a canvas-replacement using DHTML and divs with clipped background-images. Therefore the test results are not directly comparable with the other web browsers.
That's what I get for not reading the article
IE should not have even been tested - it does not support HTML5 canvas elements!
Indeed it doesn't. A lot of the hacks involved to get IE to support canvas is merely an emulation of canvas using VML.
I've experimented with a bunch of sprite based animation stuff on canvas, and have seen similarly terribly poor results on a bunch of versions of IE using the code google wrote. (I'm assuming their benchmark is regarding the rendering sequence) Might as well create <image> tags, and animate the image tags with some style manipulation using js, because functionally what the hacks are doing to make canvas work on IE. (This is not regarding tricks to speed up the rendering, such as recycling DOM elements, which is cheaper than creating new DOM elements *shrug*)
I had an install of World of Warcraft on my desktop computer. I pick up a new laptop, I figure it would be faster to copy the WoW install I have on my desktop to over to the laptop over the network. After about an hour of "calculating time" - I tried to cancel the operation. Frustrated at the length of time it took to simply cancel a file, I literally pulled the plug on both machines and powered them back up.
After that I went to the Blizzard website on my laptop to download the client from there. And as for the add-ons, I zipped them up and mailed them to myself as an attachment, in order to save time.
Both the laptop and desktop have Vista on it (came with the computer).
Considering that companies usually have a central file server somewhere, imagine business workers trying to do basic file IO stuff, like copy word docs, spreadsheet files, or large
As long as you never have to manage files on your computer, and you have gobs of ram, Vista is a nice OS. If not, it's better to wait for an alternative. I've preordered my copies of 7 a few months back, and I can't wait for the goddamn day I get rid of this POS operation system.
Then I can start streaming my music over the network to any machine in the house, once again.
The christmas rush is a profit gimmick - the games with the most (advertising) visibility generally would get the most cash - this is regardless of the quality of the game.
Blizzard doesn't really play by the marketing rules. Warcraft 3 was released in June '02. Diablo 2 also in June 2000. The first Starcraft was released at the end of March '98.
I would say that those properties have done pretty well on their own without the help of any holiday season shopping boost.
Why is Google spoiling good concepts by tying them to the browser exclusively? They just need to develop for the three major platforms, Windows, Linux and OS X.
Perhaps the team doesn't want to have to constantly maintain 3 seperate codebases for the same app whenever an OS goes thru a major revision.
Or perhaps because they want users to use it "right now" instead of having them go thru the install process considering almost every machine has a browser on it.
Neutrinos have bad breadth.