51–60 of 136 posts
Wow! Those screen readers are fast (his example https://soundcloud.com/freecodecamp )! I barely understood a word. I didn't know that. It's a shame that so many programs don't follow the accessibility guidelines, but it's just too damn easy to forget about the disabled if you aren't. But this article was an eye-opener for me (no pun intended).
I'd like to know: what is the most comfortable posture for coding once you no longer have to look at a screen? I've wondered whether a syntax-sparse language like iolanguage might allow you to code entirely by voice and ear, with no need for keyboard. For those of us with vision, imagine having a lounge with a large screen on the wall. You can talk into your headset as you pace around, or lie on the couch.
Wow ...so many questions ...I'm not sure where to begin answering all of these :) HN is throttling me, so please come find me on #zersiax on freenode to discuss this if you have more questions :) I hope this goes through ...
I'd like to know: what is the most comfortable posture for coding once you no longer have to look at a screen? I've wondered whether a syntax-sparse language like iolanguage might allow you to code entirely by voice and ear, with no need for keyboard. For those of us with vision, imagine having a lounge with a large screen on the wall. You can talk into your headset as you pace around, or lie on the couch.
Technically I can already sort of do that in any language. Do keep in mind that all I need to interact with a computer is a keyboard and some way to hear audio ...so I can in fact lay back on the couch with a keyboard on my lap and code away. In fact ... I do that all the time ;) I can't check my work using braille that way though, which is kind of essential with very complex code
I always wondered what happened to that dude.
Wow! Those screen readers are fast (his example https://soundcloud.com/freecodecamp )! I barely understood a word. I didn't know that. It's a shame that so many programs don't follow the accessibility guidelines, but it's just too damn easy to forget about the disabled if you aren't. But this article was an eye-opener for me (no pun intended).
Wow, the audio example... It's like a solid wall of pure data.
I had to download the audio example and lower the playback speed to a third of what it was before it started making sense! It is a reading of an earlier draft of the first bit of the post, btw, so there are several divergences which make it even harder to try to match text to speech.
Another advantage of the ruby community's general commitment to produce a language that can be written in any old text editor. I think Java long past that point, you really need an effective IDE with certain features that it knows about Java to be effective in Java.
Making sure things are still doable with a plain text editor gives developers a lot more options (including for developing new editing environment improvements), instead of locking them in to certain IDEs. A lot more options for accessibility reasons or any reasons.
Florian @zersiax 2 hours ago
mate, could you comment on there that I created a channel on freenode called #zersiax if peeps have questions?
Florian @zersiax 2 hours ago
seems I posted too many comments on HN , its blocking me from sending more :) and I do want to reply o all these
https://twitter.com/zersiax/status/560810466789044224 https://twitter.com/zersiax/status/560810548263407617
---
There's something beautiful about a typo from a visually impaired person :)
Wow! Those screen readers are fast (his example https://soundcloud.com/freecodecamp )! I barely understood a word. I didn't know that. It's a shame that so many programs don't follow the accessibility guidelines, but it's just too damn easy to forget about the disabled if you aren't. But this article was an eye-opener for me (no pun intended).
If someone can understand at that speed, listening to audiobooks must be a very quick activity...