I personally use:
- Atom for webdev stuff
- IntelliJ IDEA for Java
- Visual Studio for C++ / C#
- Pycharm for Python
I used to be a fan of Eclipse until I found IntelliJ, which is simpler to use while maintaining a lot of useful functionality.
You are viewing a single comment's thread from:
I wish I had that many options available for me, honestly. Being blind, not too many IDEs are accessible to the degree they need to be in order for the blind programming community to get anything out of them. Hence why I pretty much use either VSCode or Visual Studio for everything. On a side note, while I could bother trying to get into contact with everyone and make requests that they fix stuff, I've discovered that the ones who care about the entire population are the open source communities, so I'd rather support them than some big corporation. Jetbrains, for instance. I can't even use reSharper, never mind trying to use one of their full-fledged IDEs. If you run over to NVDA, you'll understand what I mean.
I had no idea that a blind programming community exists! NVDA is incredible, and I can't believe that I hadn't heard of it before. I hope that more companies get support for screen-reading technologies, it seems like an obvious move to make.
It's not about companies getting support for them. It's about building accessibility checks into the development workflow and realizing that accessibility doesn't cost more money; it simply is a process that almost every framework has. WPF, for instance, if the default controls are used (though it works with custom ones, just gotta remember to include the property values), is just a quick look in the properties and ensuring that all of the UIA values are full. Other frameworks such as WXPython, QT5 Accessibility, and so on, exist for other languages and frameworks.