Diablo in JavaScript • Hacker News Board

Re: Diablo in JavaScript

#81

Post by Bockit » Tue, Feb 19, 2013, 3:11 AM UTC

I look forward to the day when I can watch in-game footage of games, maybe replays from RTS games for example, in a game-engine in the browser.

Re: Diablo in JavaScript

#82

Post by qu4z-2 » Tue, Feb 19, 2013, 4:02 AM UTC

aethr wrote: post #59

daleharvey wrote: post #54

Earlier quoted context omitted.

The me in 1997 would be pretty happy to know that the game would be playable by virtually every computer user in the world by clicking a link.

Well, every user using Chrome.

With a reasonably modern computer and internet access.

Re: Diablo in JavaScript

#83

Post by coldtea » Tue, Feb 19, 2013, 4:54 AM UTC

kalleboo wrote: post #78

jQueryIsAwesome wrote: post #69

Earlier quoted context omitted.

Yeah, only now with javascript we can transmit HD videos in realtime via webcam with Chrome or Firefox, just like in 1997... no wait... the cherry picking of an example went wrong on that one. But maybe we can still devalue Javascript by saying HD videos is a separate thing and that speed connections is more important than Javascript in that example?

The desktop equivalent, CU-SeeMe, was working in 1994.

I tried it circa 1998. I wouldn't call it "working" even then.

Not to mention it needed installation (Javascript just needs people to go to a specific page), and the speed, lag and buffering was horrible at the time.

Re: Diablo in JavaScript

#84

Post by sangupta » Tue, Feb 19, 2013, 4:57 AM UTC

Awesome work. It's a bit slow in FF but works fine in Chrome. A welcome screen would be helpful.

Re: Diablo in JavaScript

#85

Post by frannk » Tue, Feb 19, 2013, 5:22 AM UTC

can not believe only 500 lines of code

Re: Diablo in JavaScript

#86

Post by marcloney » Tue, Feb 19, 2013, 5:55 AM UTC

overgard wrote: post #44

MatthewPhillips wrote: post #41

Earlier quoted context omitted.

Dead Space 3 wasn't created by 1 person in their spare time. But by all means, don't let that temper your cynicism.

I meant it as a commentary on celebrating javascript in general, not on this person's project. It's not cynicism I feel, it's dissatisfaction. I /want/ to use the web for powerful things, but the limitations of javascript make many of those things impractical. Hence my ambivalence towards "x in javascript"

What exactly makes it impractical to do powerful things? You may have disdain for certain language features but I don't understand how that makes it impractical.

Most of the tech demo's we're seeing coming out of the JS crowd are from people who have only just started using the WebGL API (which is still experimental). I'm extremely excited to see the things that experienced OpenGL developers will be able to do as the API becomes more mainstream.