⚡ Feel the Beat!
@bHaptics returns to Synth Riders on #MetaQuest#PCVR#PSVR2 ! To celebrate, you've got a chance to feel the music like never before and WIN a sweet bundle.
To Enter:
✅ Follow @synthridersvr and @bHaptics
✅ Re-tweet this post!
✅ Tag 3 friends who need to feel the beat in VR!
🏆 Prizes:
🎯 1x bHaptics FPS Bundle (TactSuit Pro & TactSleeve)
🎟 10x Synth Riders Base Game + Complete Collection Keys
Winners announced on March 21st! 🎉
@mahemoff@aalaap@bnj I know the intended flow for Apple Watch and it seemed obvious to me the user thought it was NFC or similar. RFID predates QR codes by more than 10 years, and lots of people use it for "sharing information" (like contact cards). Also the design flow implied by eg MagSafe chargers
@0xabad1dea Intuitively to me, dots feel like either stopping a ringing string or (on a double strung harp) reaching through to pluck the string from the “wrong” side. I haven’t looked closely enough at the patterns to see if that makes any sense in context
@0xabad1dea I think there’s probably some further conjecture you *could* explore around the “|” divisions as well as the dots. They look like measures of 3 beats, one long (2 beat) note and one short, occasionally in double time.
Maybe a good moment to blast one of my favorite performances of one of my favorite pieces of music: https://t.co/Bja2nme25z
Thank you #UkhoEnsemble#Kyiv
@krilia @wagnerSRiii @ERosson1982 @That1MedStudent@PedsDrJeff So I looked it up. It’s plausible but not confirmed because the effect works, but there’s no historical record to confirm it. https://t.co/85n3RBnup9
Anyway, it’s a very easy experiment to do to yourself to confirm that doing this works, whether or not it’s why pirates did it.
@krisdages@DasSurma You should be able to type async wrappers for sync functions. https://t.co/7dPv4gFh0s
You can do something similar if you need to handle async iterators and not just promises, although I think there's an extra layer of type indirection to pull it off.
@syrusakbary@MaxGraey@DasSurma You could argue that since the types align, ts is doing its job here. A stricter type system could, for example, narrow by the valid radix: between 2 and 36. That would help guide in the correct direction, since an index value of 0 would then be invalid.
@syrusakbary@MaxGraey@DasSurma Unsound because `parseInt` is being passed `(value:string,index:number,arr:string[])`, but is expecting `(str:string,radix?:number)`. Presumably, you don't want to change the radix of parseInt based on the index value of the array being mapped.
@tabatkins@DasSurma This is the most frustrating part of ts to me. You know ts is "capable" of providing the right inference, but you must cajole the inference engine into providing it. It is tantalizing in the worst way