4 ms·
> "Bring the VBE into this century!" This actually gave me goosebumps... Are there many modern use-cases for Visual Basic? All I can think of is horrible scri
by gitgud 7y ago
> "Bring the VBE into this century!"
This actually gave me goosebumps...
Are there many modern use-cases for Visual Basic? All I can think of is horrible scripting code for Excel, Word and AutoCAD
- pjc50 7y agoYou wouldn't believe how much business value flows through Excel spreadsheets.
- reportgunner 7y agoI would make fun of VBA but it is still helping save lives and catch criminals. https://www.youtube.com/watch?v=DS55cFZdino https://www.youtube.com/watch?v=DS55cFZdino
- yonixw 7y agoVBA scripting engine is built in into windows and can be called from C,C++ and more (there is also built-in old JS engine but probably less popular). Its like python 2 for linux. If you want to give scripting capabilities on windows it the #1 choice.
- markus_zhang 7y agoI think VB is still a fine compiled language and you can find a lot of use cases. On the other hand, VBA is used mostly by people who have to maintain old Office applications and basically live in MS Office. VBA is still the first choice to automate MS Office. That's the reason I want to stay away from MS Office lol.
- jmt_ 7y agoAnyone that inherits any sort of legacy MS Office workflow almost always needs to interact with VBA. Access, Excel, and Word workflows use it excessively as it's the only language you can use for manipulating things "inside" the file. Sure, you can use something like DAO/ADO/ODBC to perform CRUD type operations on the file from some other program. But if you want to, say, attach some code to an event in an Access form, you're stuck with VBA. So a tool like Rubberduck is useful to people developing for legacy Office related code, especially since VBE by default isn't super great. Access seems to be dying out but Excel is still flourishing.