stdVBA VS ExceLint

I do RPA from VBA personally using IAccessiblity. See stdAcc (https://github.com/sancarn/stdVBA/blob/master/src/stdAcc.cls) and an example (https://github.com/sancarn/stdVBA-examples/tree/main/Example...)

You could have just treated everything as variant correct? That's what we do here: https://github.com/sancarn/stdVBA/blob/master/src/stdLambda....

The responses I got was a mix. Some businesses didn't take me seriously because the main language I used was VBA. Some businesses claimed I was too eager and I "didn't have a life". No one seemed to care about the achievements I had made in the languages, like building a DSL in VBA, or this electron app. I did eventually get a job in another engineering firm though, where I spend 90% of my time to this day programming.

Really depends what you actually want to do and how neat (or fast) you want your code to be too... I typically use stdEnumerator and stdLambda from stdVBA.

Sometimes, though more of a library / tool developer here. See stdVBA or stdVBA-examples

That said it is effort. After building stdLambda which brings lambda syntax to VBA, I can tell you that error handling in this class is still trash. It's just a lot of effort to write good error messages, and handle all errors correctly. Still definitely an item on the TODO list, but will it ever be a priority? idk

Otherwise this library poses as an example of how to use stdVBA libraries. Libraries used in this project: stdEnumerator, stdArray, stdCallback, stdCOM, stdICallable, stdLambda, stdRegex.

If you want a solution though see stdSettings. There are both system and user settings. Users are bound by their domain, so should work across organisations :)

Use stdVBA's stdAcc:

Explaining code in such a way that it codes the correct thing is pretty awful though... Let's try to do that for stdTimer.

It is a proper programming language.

For #1, there has been research on linting and automated semantic error or smell detection in Excel (e.g., https://github.com/ExceLint/ExceLint). Some features are live in Excel today!

For #2, Excel now supports Python.

I don't think you need to do any conversions, all of the necessary information exists in the spreadsheet.

With that in mind, has there been any talk of integrating something like ExcelLint as part of the core Excel product to help identify these errors and encourage a set or best practices amongst users?