1,986 karma · joined December 9, 2014
Damn... that's honestly a shocking thing so say, if only for the fact that you can run in JS other languages. But even then, if you could "only" run JS it gives you access to a high level language but also all kind of inputs, from a keyboard and mouse, obviously, all the way to MIDI, hand tracking in WebXR, etc and all kind of outputs, e.g. screen, obviously, but also 6DoF XR, but you also get low level access to actual hardware. Totally anecdotal but I was precisely in my other browser window accessing my XR headset via adb via ... JavaScript in the browser, thanks to WebUSB. You can also run parallel computations via shaders but also WebGPU. The amount of things you can do is really mind blowing. You mind not like the syntax or some decision about the language itself but that somehow it's not interesting to have access to all that and more from any browser window is just surprising to me.
Last but not least, all that is done with 0 installation. You start a device, open the browser window, open the console and voila, you get a development environment instantly.
I just find it incredible.
That being said I didn't compare both, not sure why you brought that up. I specifically discussed about prototyping, quoting a specific sentence, not scientific research.
I won't comment on hiring interns as that's not my expertise (even though if you want to teach your staff, obviously I can see a problem there) but I can comment on rapid prototyping, it's what I do.
Rapid prototyping is NOT making a CMS quick. It's not about making a quick mockup of a UI. It's not about making yet another well known... anything. The entire POINT of prototyping is to make something NEVER done before. Typically that means you are reaching the frontier. You are making something with NO documentation to rely on. You are using tools, hardware or software, which do NOT have tons of StackOverflow errors. There is no dataset to crawl, there is no well structured Q&A database to train on. You have to poke and see if the thing actually works as expected, and it often does not.
So sure, if you are using interns as a trick to underpay your staff, or if you are using prototyping as an excuse to build poor quality software fast, maybe it does help. If you are genuinely prototyping, it breaks fast and the supervision overhead makes it pretty pointless, especially since typically it's by actually implementing that you find out not just how the new setup works, but also its limits, and thus the actual needs of the project, not the one the stakeholder imagined would be.
So not, not for rapid prototyping either.
TL;DR: prototyping is a learning process, not a low fidelity output.
PS: this comes up very often from NON prototypists that I wrote a short piece about it https://fabien.benetou.fr/Content/GoodPrototypesAre10LinesLo... so much so that it feels like a pattern "GenAI/LLMs is good for tasks X" while the author actually does not do task X except very superficially.
I have few rooted Quests, only some Quest2 still left unrooted.
Zero days are valuable because they can be exploited but if the pace of exploitation is faster (which I'm not sure is the case), then the response WILL be faster, even if it means going offline. Institutions that won't will simply go offline by losing their data or becoming unprofitable due to ransomware.
Now for components that are core to the infrastructure, say OpenSSL, there is already a TON of attention and efforts, including red teaming, so it's not as if it's opening floodgates.
Sure low hanging fruits will get picked either faster or a at a larger scale, say a random outdated IoT device at your local flower shop, but for the rest, I don't think it's realistic to expect no response.
Security, digital or not, has always been an arm race. New threats means new responses specifically by incorporating the threat.
Array.from(document.body.querySelectorAll('p,li')).filter(e=>e.innerText).map(e=>e.innerText = e.innerText.split('\. ').map(s=>s[0].toUpperCase() + s.slice(1)).join('. ') )
Not perfect but hope it helps.IMHO usable real estate relative to the task (because coding doesn't have the same need as video editing, 3D modeling, etc) is a proper way to compare, not pixel density or anything or the sort that doesn't take what VR can actually offer.
PS: I do spend times in HMDs to work, including Vision Pro, Varjo, Frame, other HMD I can't mention, and in my experience it did already reach point where it is actually "good enough" for most tasks even one where a lot of text (which is typically quite demanding for readibility) is needed, but we don't have the same eyes, workflow, etc. It is though not good enough if you try to reproduce what you already have and compare exactly, but it's also not the point.
Gosh I'm so "behind" it's painful. /s
Have you considered providing GadgetBridge support? I don't see anything on https://codeberg.org/Freeyourgadget/Gadgetbridge/issues?stat... but it could bring interesting combinatorial possibilities.
For anybody who wants to try that without any extra hardware but just your webcam give a go to https://codepen.io/mediapipe/pen/bGweWyR based on MediaPipe Hands in JavaScript https://chuoling.github.io/mediapipe/solutions/hands.html
You can bind a hand position or gesture (e.g. going from one position to another) to a desktop command by running this in the background on your NodeJS companion app and spawn() for the commands.
FWIW did something similar using OpenCV https://fabien.benetou.fr/Portfolio/PostureMaintenance 15 years go.
If you also are interested in gaze tracking https://lebmatter.github.io/gazerjs/ is another Web based example.
In this specific case though as others pointed out there are already a lot of products on that specific segment with that name.
FWIW it's very to test by the way, pick a random XR demo support hand tracking and you will see it's not that tiring. It doesn't mean it's useful though.
I switched recently from mouse to touchpad and ... next day my great ergonomic mouse was basically in a drawer. Meanwhile when I tried to use Tap Strap the first step was to learn combinations with basically no gradient of feedback, it was either success or failure.
Inertia isn't such a big problem if the investment is small but if you have to learn an entirely new way then it's a huge risk.
I spend a LOT of time with different interfaces (eye tracking, 6DoF controllers, pens, touchpad in keyboard, ergonomic mouse, etc) and... basically if there is 1 thing I'm confident about is that input methods are very task dependent. If you want to input text, especially hard to pronounce keywords and symbols, keyboard is great, if you want to move a pointer at arbitrary position in 3D keyboard sucks. It also depends on the context, behind a desk vs on the move is totally different.
So yes quite curious about such a wide statement.
Is there a Web version running in a VM/container in the browser?
I worked a bit with Tap Strap on XR and without but in my experience once you master a keyboard nothing comes close while manipulating text, e.g code.
People working on alignment focus on "big picture" like existential threats meanwhile building the technology today, not tomorrow or in a near future, is already using a massive amount of resources (GPUs, RAM, themselves consuming a lot of energy, establishing data centers in water poor areas, using gas turbine to temporary power them) and horrendous work condition (for supervising learning, curating datasets, etc) while being an actual excuse for job destruction (regardless for how AI itself does the job) so that in fine kids cheat on their homework while imagining their have no job prospect.
So... who gives a shit really?