Live data from Hacker News

QuakeJS – A Quake Port to JavaScript with Emscripten

quakejs.com

141–150 of 165 posts

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#141
post #120
post #73

Earlier quoted context omitted.

Pretty cool. You don't happen to have some ping comparisons betwen WebRTC and WebSockets?

Sadly no, but I don't think there's much of a ping difference on a good network. With WebRTC (datachannels in UDP mode) you just get the benefits of UDP (or lack thereof :)).

I see.

I had the impression UDP would lower the average ping, because you wouldn't have to wait on lost packages like with TCP.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#142

Earlier quoted context omitted.

Descent came out in 95. Quake was 96.

I should have said the first true 3D FPS. Descent is in a different genre that is a little more niche.

Terminator Future Shock predates it, had 2D guns but the world and enemies were polygons and it even had driveable vehicles.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#143
post #128
post #81

Earlier quoted context omitted.

I don't know what point you are making here. These projects could have been done by compiling to asm.js - webasm isn't what makes them technically possible, it just makes them faster, smaller and parsed faster. You have been told all of this before.

Just like you have been told before that WebAssembly is nothing new beyond politics, all the way back to 1961.

Above you linked projects that you said happened specifically because of webasm. Here you are saying it is nothing new 'since 1961' (what does that mean exactly)?

How have you made CPU workloads run at native speeds across all major browsers before we webasm?

Many people have corrected you on your extreme and bizarre vendetta against webasm. You are the only one saying it is both nothing new and somehow enables new projects that you don't like.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#144
post #128

Earlier quoted context omitted.

Just like you have been told before that WebAssembly is nothing new beyond politics, all the way back to 1961.

Above you linked projects that you said happened specifically because of webasm. Here you are saying it is nothing new 'since 1961' (what does that mean exactly)? How have you made CPU workloads run at native speeds across all major browsers before we webasm? Many people have corrected you on your extreme and bizarre vendetta against webasm. You are the only one saying it is both nothing new and somehow enables new p…

As shown at the start of the thread, with Flash Alchemy, already in 2011.

Those people are the ones with an agenda to spread WebAssembly as above anything else in regards to safety, and the very first attempt to have a bytecode format for C and C++ code, when IBM and Unisys mainframes, CLR, Brew, Tendra, PNaCL, Alchemy have been there first.

My agenda, is only to prove a point that, it isn't that much safer than PNaCL, and the only thing we got from its adoption is a 10 year delay having a general purpose VM in the browser.

Ironically, Chrome is anyway who calls the shots in WebAssembly, as per browser market share.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#145
post #130
post #79

Earlier quoted context omitted.

Can you link one that has to do with webasm? Are you saying that you think javascript is less secure than flash?

Indeed, https://www.contextis.com/en/blog/webgl-a-new-dimension-for-... https://react-etc.net/entry/exploiting-speculative-execution... https://www.virusbulletin.com/virusbulletin/2018/10/dark-sid... https://www.cvedetails.com/vulnerability-list/vendor_id-2041... https://i.blackhat.com/us-18/Thu-August-9/us-18-Lukasiewicz-...

All of these are speculation about the future. Most have nothing to do with webasm at all.

The first is about webgl (that has nothing to do with webasm)

The second is about using javascript with intel speculative execution exploits.

The third is grasping at straws, saying that call center scams would be more obsfuscated, even though javascript or asm.js can be just as obsfuscated, if not more.

The fourth is about crashes in the webasm JIT

The last is about -theoretically- executing arbitrary javascript. Heavens no.

What is the real reason you have some crazy crusade against webasm? You go to great lengths to grasp at any straws you can. It isn't that big of a deal. It is a more direct way to JIT cpu intensive parts of a web page. Get over it. Incredibly, the alternative is to run actual native instructions by downloading a binary.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#146
post #54

This is great. Does anyone remember quakelive? Around 2010 it was playable in the browser via a browser plugin. Loved playing it on my macbook. I don't recall if the plugin was flash or a java applet but when support stopped for those quakelive moved to steam as a desktop app. Edit: Per wikipedia it used NAPI https://en.wikipedia.org/wiki/Quake_Live

If it required a custom plugin, what was significant about playing it in a browser?

To me, the appeal of a browser game is that it is contained and you don't have to worry about malware.

(Notwithstanding the occasional vulnerability, but those get fixed.)

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#147
post #144

Earlier quoted context omitted.

Above you linked projects that you said happened specifically because of webasm. Here you are saying it is nothing new 'since 1961' (what does that mean exactly)? How have you made CPU workloads run at native speeds across all major browsers before we webasm? Many people have corrected you on your extreme and bizarre vendetta against webasm. You are the only one saying it is both nothing new and somehow enables new p…

As shown at the start of the thread, with Flash Alchemy, already in 2011. Those people are the ones with an agenda to spread WebAssembly as above anything else in regards to safety, and the very first attempt to have a bytecode format for C and C++ code, when IBM and Unisys mainframes, CLR, Brew, Tendra, PNaCL, Alchemy have been there first. My agenda, is only to prove a point that, it isn't that much safer than PNaC…

You think all the people in this thread talking about quake 3 and doom 3 running smoothly are part of an agenda against ancient bytecode formats for IBM mainframes?

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#148
post #130

Earlier quoted context omitted.

Indeed, https://www.contextis.com/en/blog/webgl-a-new-dimension-for-... https://react-etc.net/entry/exploiting-speculative-execution... https://www.virusbulletin.com/virusbulletin/2018/10/dark-sid... https://www.cvedetails.com/vulnerability-list/vendor_id-2041... https://i.blackhat.com/us-18/Thu-August-9/us-18-Lukasiewicz-...

All of these are speculation about the future. Most have nothing to do with webasm at all. The first is about webgl (that has nothing to do with webasm) The second is about using javascript with intel speculative execution exploits. The third is grasping at straws, saying that call center scams would be more obsfuscated, even though javascript or asm.js can be just as obsfuscated, if not more. The fourth is about cra…

Survivor of the anti-PNaCL, Java and Flash crusade I guess.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#149
post #144

Earlier quoted context omitted.

As shown at the start of the thread, with Flash Alchemy, already in 2011. Those people are the ones with an agenda to spread WebAssembly as above anything else in regards to safety, and the very first attempt to have a bytecode format for C and C++ code, when IBM and Unisys mainframes, CLR, Brew, Tendra, PNaCL, Alchemy have been there first. My agenda, is only to prove a point that, it isn't that much safer than PNaC…

You think all the people in this thread talking about quake 3 and doom 3 running smoothly are part of an agenda against ancient bytecode formats for IBM mainframes?

Only those pushing for WebAssembly as if it was the best thing since the Web came to be.

Re: QuakeJS – A Quake Port to JavaScript with Emscripten

#150
If I wanted to learn to write browser-based games what would be a good place to start? I know some JavaScript but am not particularly enamoured with the language. Should I learn TypeScript plus some framework? (React?) Or how about something functional like Elm?
Post reply on HN