We used Jamboard at a previous job. It was atrocious. Very quickly was replaced with one of the huge Surface devices, which, due to just running a real OS, let people use the whiteboard tools built into other conferencing tools, as well as figma.
And this company was almost exclusively conferencing with Google hangouts (whatever name it was going by that particular day). So it wasn't an issue of mixing services.
We've had actors in videogames for as long as there's been the ability to play samples at a high enough quality. Hell, the 90s FMJ era was full of them. Some good, some not so good.
When I was going through a job hunt last year, I encountered a few of these. I either reported them on the job listing sites, typically as misleading, or told my recruiter.
I doubt anything came of it, but its what we still need to do when they pull this shit.
Yeah. A lot of companies try to just bolt a11y onto an existing app. You have to design from the start that way. And if you do, it actually makes a better app for everyone
It's a clusterfuck. I don't need any accessibility hardware or software. I'm "abled". But I use it anyways, because it makes the human computer interaction far easier.
Most of the hardware out there is utter shit. I have a big 3 pedal foot switch I use with my MacBook. Out of the box it's helpfully set with each pedal being a b and c, with no built in way to change any of that. I've got a karabiner configuration that makes them more useful.
I tried using eye tracking hardware to center my cursor on the display I was looking at, before I got rid of it in frustration.
The only pieces of hardware that work how I want to are the ones I built myself (keyboard and numpad). Everything else requires a bodge. And that's shit. I'm abled and technically minded. If a system doesn't work for me, I can just go back to the happy path. A person with limited mobility cannot. And the disability advisors and advocates and volunteers who set these things up for people usually don't know any better, so they just cargo cult solutions and employ them rote. They don't mean anything negative by it, they're trying to help people. But they aren't typically super knowledgeable about tech either. They get led around by the nose by clever bits of marketing and poorly understood instructions.
Software explicitly marketed as "accessibility" is generally awful. At previous jobs I helped oversee the implementation of accessible systems for a website, in cooperation with a local accessibility advocacy group. For screen readers they used either JAWS or the Apple built in one, voiceover. Both of which work, but not great, with chrome or firefox. Eventually we found ChromeVox, made by Google, and showed it to this accessibility group. Iirc they now use it when helping to set up people with software, because it's just so much better than anything they used before.
Similar stories exist with regards to the SurfingKeys browser extension. In short, it gives you a keystroke that puts vim style easyjump targets on every clickable element on the page, so you can trigger anything with a few keystrokes. Target selection can be simplified down to a very small selection of keys, say the left hand home row.
For people with highly limited mobility, most page navigation solutions out there are atrocious. At best you get an x-y scan, where you trigger the scan, get a slowly moving cursor in one axis, stop it when it intersects what you want to interact with, and then repeat with another cursor along the opposing axis. If you don't use this, you get to tab through everything, one item at a time. Some systems allow for cursor key navigation (arrow keys), but that's hit and miss.
I showed the accessibility consultant SurfingKeys, and they were floored. They had a few people they were helping out who had full operation of a hand or whatever, but not enough to really use a mouse. SurfingKeys and a simple USB numpad with some key rebinding let these people use the Internet far faster than ever before. They could click links! They could scroll. Finding and clicking something on a search engine was no longer an exercise in patience and frustration.
I've used one before. Maglev is a ruby runtime built atop GemStone/S, which is an object db. Gives Ruby some distributed powers, like BEAM languages (Elixir and Erlang) have.
Practically all it meant was you didn't have to worry about serializing ruby objects to store them in your datastore, and they could be distributed across many systems. You didn't have to use message buses and the like. It worked, but not as well as you'd hope.
Amusingly, BEAM languages, have access to tools a lot like oodbmses right out of the box. ets, dets, and mnesia loosely fit the definition of an oodb. BEAM is functional and doesn't have objects at all, so the comparisons can be a tad strained.
Postgres also loosely satisfies the definition, with jsonb columns having first class query support.
Interesting that they think there's a single universal voice amongst hens. I've got a small flock of a dozen birds, and they each have distinct voices and calls. You can always tell who just finished laying by which egg song you're hearing, until the others join in and it's a cacophony.
We've got one anericauna who likes to "scream" for her egg song. Awful sound, very close to a hen screaming because a bobcat got her.
This is particularly painful with starfield. I know the game just came out, but the Fandom wiki is atrocious, and I haven't been able to find any others.
Or the asocial, where you come up to a stop sign, look right, see a guy coming way too fast to stop in time, and don't go till after he's blown through the intersection
JetBrains users kind of live in their own weird bubble. Of the ones I've worked with, a decent number didn't even know how to use git, they just relied on the built in vcs tools
Paradox @ Paradox @lemdro.id Posts 8Comments 324Joined 2 yr. ago
Kagi solves this problem