News for hackers. Stuff that matters.
Re:Diablo in JavaScript by jQueryIsAwesome on Monday February 18, 2013 @09:05PM (#5242162)
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?
Re:Diablo in JavaScript by MrScruff on Tuesday February 19, 2013 @05:00AM (#5243522)
That argument works for anything, as long as you can convince the browser vendors to implement support for it and provide it as an api. So I would argue that's much closer to the definition of cherry picking an example.
Re:Diablo in JavaScript by jQueryIsAwesome on Tuesday February 19, 2013 @06:46AM (#5243797)
So I guess I can't talk about the DOM; many functions are just an API for it; and canvas is just an API for drawing accelerated by the CPU; so... Javascript is nothing and nothing can be blamed on it?
Re:Diablo in JavaScript by MrScruff on Tuesday February 19, 2013 @09:00AM (#5244263)
I'm just saying that the provision of video streaming as a web api is not a particularly technically interesting development. It's just a gradual beefing up of the browser as a thin client. And until support for the features are widespread, it's not really a commercially interesting development either.

I would class many of the other things you mention as incremental improvements of the rendering engine as a universal runtime. It's great that it's happening but it's not technically that exciting to me to see reimplementations of 16 year old games since we've had the flash runtime in the interim anyway.

Re:Diablo in JavaScript by jQueryIsAwesome on Wednesday February 20, 2013 @12:03PM (#5251591)
Broken argument; flash is way too slow compared to the current version of Canvas; recently I made a full conversion of flash to canvas (was painful but) the performance is outstanding and the ability to interact natively and play nice with the DOM is invaluable.
Re:Diablo in JavaScript by MrScruff on Thursday February 21, 2013 @09:32AM (#5257566)
The latest comparative performance of 2D drawing in one runtime vs another doesn't have anything to do with my argument.
Re:Diablo in JavaScript by jQueryIsAwesome on Friday February 22, 2013 @08:10PM (#5268018)
> I'm just saying that the provision of video streaming as a web api is not a particularly technically interesting development. It's just a gradual beefing up of the browser as a thin client. And until support for the features are widespread, it's not really a commercially interesting development either.

You mean P2P connections? Oh we have that now in Firefox and Chrome. You mean video chats? Oh we have that. You mean thousands of libraries to create and develop videogames for the web? Oh we have that. You mean easily extensible browsers via plugins/extension? Oh we have that. I need you to be very specific about what we are lacking.

Re:Diablo in JavaScript by MrScruff on Wednesday February 27, 2013 @09:46AM (#5292571)
What the html platform is lacking? My last project was built around QT, OpenGL, CUDA and made extensive use of various C based linear algebra libraries and was ~20kloc of C++. I'm sure it could be reimplemented as a web app but it would be a strange decision to do so.

But that wasn't my point. My point was that just because the web allows you to do things that were possible on the desktop 10+ years ago doesn't make it interesting to me. And the fact that you can always add specific functionality to the runtime like video conferencing doesn't really address that.

I don't have to wait for browser vendors, I just start coding.

Re:Diablo in JavaScript by kalleboo on Monday February 18, 2013 @09:56PM (#5242318)
The desktop equivalent, CU-SeeMe, was working in 1994.
Re:Diablo in JavaScript by coldtea on Monday February 18, 2013 @11:54PM (#5242699)
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 by thevdude on Tuesday February 19, 2013 @12:52PM (#5245801)
> speed, lag and buffering was horrible at the time

That has nothing to do with the software and everything to do with the network, no?

Re:Diablo in JavaScript by coldtea on Tuesday February 19, 2013 @04:29PM (#5247159)
Of course not.

Even on the same network, different conference apps have different characteristics. It depends on the compression and coded they use, how they handle changes in network performance, etc.

Plus the GUI and UX of that app was simply horrible.

Re:Diablo in JavaScript by jQueryIsAwesome on Monday February 18, 2013 @10:08PM (#5242360)