News for hackers. Stuff that matters.
Re:Losing Sight by kabdib on Saturday October 03, 2015 @06:35PM (#10325659)
One of the best programmers I know is nearly blind. He can see, a little, with the aid of a telescope-like affair that is mounted to a pair of glasses.

But the breadth and depth of his understanding of computers and software is amazing, and the code that he writes is some of the best I've seen: Very clear, very direct and unsullied by useless abstraction, and easy to maintain.

Re:Losing Sight by eps on Saturday October 03, 2015 @07:32PM (#10325833)
Which language does he use primarily? Just curious.
Re:Losing Sight by mwcampbell on Saturday October 03, 2015 @08:18PM (#10325922)
Naturally I can't answer your question about the specific person the GP was talking about, but FWIW, blind programmers are working productively in all popular languages (and some less popular ones too). Even significant whitespace, as in Python, isn't a problem, because the more full-featured screen readers can be configured to announce changes in indentation.

Accessibility of development environments and tools is another issue. For example, Xamarin Studio is totally off-limits because it uses GTK, and GTK is inaccessible on Windows and Mac.

Re:Losing Sight by voltagex_ on Saturday October 03, 2015 @09:56PM (#10326090)
>Xamarin Studio is totally off-limits because it uses GTK, and GTK is inaccessible on Windows and Mac.

Shit. Is there a bug report for this? (Upstream, with GTK)

Re:Losing Sight by mwcampbell on Sunday October 04, 2015 @09:44AM (#10327478)
There's this old bug, specifically for Windows:

https://bugzilla.gnome.org/show_bug.cgi?id=303304

And this mailing list post from a few years ago provides a more up-to-date overview of the Windows accessibility APIs:

https://mail.gnome.org/archives/gtk-devel-list/2012-April/ms...

Making GTK accessible on Windows or Mac, never mind both, would be a lot of work.

Re:Losing Sight by kabdib on Saturday October 03, 2015 @10:22PM (#10326159)
C++ and C# when I was working with him. He also wrote a bunch of (pretty good) documentation.