3 ms·
How else am I going to make a game in the browser that be controlled with a controller?
by shadowgovt 1y ago
How else am I going to make a game in the browser that be controlled with a controller?
- gmueckl 1y agoEvery decent host OS already has a dedicated driver stack to provide game controller input to applications in a useful manner. Why the heck would you ship a reimplementation of that in JS in a website?
- shadowgovt 1y agoSo that you can take input from countrollers that haven't been invented yet and won't fit the HID model.
- gmueckl 1y agoIf it hasn't been invented yet, you don't need driver software for it, do you? ;) Anyway, in your scenario the controller would be essentially a one off and you'd be better off writing a native app to interface with it for the one computer this experiment will run on.
- account42 1y agoIf it hasn't been invented yet we don't know the implications of giving a website access to it either. And that's before realizing it's already a bad idea with existing devices because they were never designed for giving untrusted actors direct access.
- shadowgovt 1y agoThat's why we have a privacy and security sandbox in browsers.
- account42 1y agoYou don't, that's the point: not everything needs to be crammed into a browser.
- shadowgovt 1y agoUnlikely. The convenience incentives are far too high to leave features on the table. Not unlike the programming language or the app (growing until it half-implements LISP or half-implements an email client), the browser will grow until it half-implements an operating system. For everyone else, there's already w3m.