41–50 of 165 posts
I guess this is cool. Not a big fan of "port everything to the browser" though. I really don't want gaming to go any more in the direction of SaaS than it already is. There is already too much rent-seeking.
Earlier quoted context omitted.
Flash had more issues than "politics."
Yeah lets see how many security issues we get to see in WebAssembly sandboxes once researchers set their sights on them, given that they already found a couple on JS engines.
If you have real criticism based on real information, let's see it.
Earlier quoted context omitted.
Why? Quake III was the best Quake.
It depends on when you discovered the game and what you played most. Quake I was the first "true" 3D game (with levels that could stack rooms vertically), and many people remember it very fondly. Personally, I really enjoyed Quake II. I did play Quake III when it came out, but the lack of a single player mode meant the game had no backstory at all.
Earlier quoted context omitted.
Flash had more issues than "politics."
Yeah lets see how many security issues we get to see in WebAssembly sandboxes once researchers set their sights on them, given that they already found a couple on JS engines.
Earlier quoted context omitted.
Yeah lets see how many security issues we get to see in WebAssembly sandboxes once researchers set their sights on them, given that they already found a couple on JS engines.
You bring this nonsense up in every webasm thread and every time it is explained to you that webasm does no IO and is contained in the same environment as javascript. Every time you either bring up details that have nothing to actually do with webasm or you say something vague about possible security problems in the future. If you have real criticism based on real information, let's see it.
Quake's source code is very hackable. I forked ioquake3 for a personal project and it was surprisingly easy to add WebRTC support to the C codebase, so you could play it in your browser over WebRTC :)
I read some people tried to use it for multiplayer, but the performance suffered with more than 10 players.
Earlier quoted context omitted.
Yeah lets see how many security issues we get to see in WebAssembly sandboxes once researchers set their sights on them, given that they already found a couple on JS engines.
Wasm has been here for years already. There's no flood of issues waiting for some cue to be released. It's no worse than any other part of the browser; probably better than some. Besides, modern browsers don't rely solely on one sandbox anymore. There are many levels of protection now.
The only thing that makes WebAssembly safer than its predecessors, is that most security researchers haven't yet bothered with it.
Earlier quoted context omitted.
It's intellectually dishonest to imply de-adoption of flash was just "politics". Flash had all sorts of problems, we should be happy we managed to get rid of it. Back in the day I was too cynical to think one day we can do so.
Not at all, it remains to be proven that WebAssembly is any better. I eagerly wait for the first batch of CVEs.
Quake's source code is very hackable. I forked ioquake3 for a personal project and it was surprisingly easy to add WebRTC support to the C codebase, so you could play it in your browser over WebRTC :)
What was your experience with WebRTC? I read some people tried to use it for multiplayer, but the performance suffered with more than 10 players.
Earlier quoted context omitted.
Not at all, it remains to be proven that WebAssembly is any better. I eagerly wait for the first batch of CVEs.
Html5 and modern javascript already replaces flash as a target. I don't know if the tools are the same. Webasm isn't necessary for that, its use is accelerating cpu intensive parts of a web page.