News for hackers. Stuff that matters.

A comment on Artillery is building a hardcore RTS with HTML5 and WebGL. Parent comment

Re:Artillery is building a hardcore RTS with HTML5 and WebGL by _random_ on Thursday September 19, 2013 @03:26PM (#6413673)
Also unlike Steam you might have to re-download the whole thing if your browser decides to clear the cache for whatever reason. Can't play underground, on a plane or while camping as well (not a typical scenario though - nitpicking a bit).
[ Parent | on HN ]
Re:Artillery is building a hardcore RTS with HTML5 and WebGL by rictic on Thursday September 19, 2013 @04:43PM (#6414178)
There's work going on for better app caching systems at the browser level. This is a UI and platform issue, but there's no tricky technical aspects. The user expresses the intent of wanting to cache a web app, and it is cached locally.
[ Parent | on HN ]
Re:Artillery is building a hardcore RTS with HTML5 and WebGL by _random_ on Thursday September 19, 2013 @05:58PM (#6414581)
"The user expresses the intent of wanting to cache a web app, and it is cached locally."

So I will use [x] to find a game in [y] and then [z] it to play.

Where: x = {Chrome|Firefox|Steam}, y = {some-sort-of-web-app-store|Steam store}, z = {cache|install}.

I guess the success will depend on how easy and rich x-y-z experiences are, but you will still have to register, pay and download.

[ Parent | on HN ]
Re:Artillery is building a hardcore RTS with HTML5 and WebGL by grey-area on Friday September 20, 2013 @06:40AM (#6416937)
But crucially you will be able to buy on the app using x,y,z, and continue to play the app using a,b,c from different hardware/software vendors, unlike the situation today with say a game bought on a mac.

That's the advantage of the web over native APIs, and why I think its ethos will eventually win out - it is better for developers and users, but not for the corporations who would like to sit between the two as intermediaries.

[ Parent | on HN ]
Re:Artillery is building a hardcore RTS with HTML5 and WebGL by kodablah on Thursday September 19, 2013 @04:41PM (#6414160)
Not when deployed with something like node-webkit which I would assume would be a common deployment strategy so you can guarantee Chrome and a certain version w/ certain features enabled/disabled.
[ Parent | on HN ]