As an example, I made a spreadsheet that queried WoW’s auction house API and showed me items, their crafting components, prices and profits from crafting, that was then easily interactable and extendable in the GUI. Doing the same thing in python would have been great up until the point where I want to display the information… getting python to output a proper front end GUI is definitely a more time consuming exercise than using Excel’s built in functionality
Keep in mind Python can interact with spreadsheet formats. So it is very possible to input your data in a spreadsheet , load that data into Python, then dump it into a spreadsheet. Easiest is CSV but I have done direct too.
What approach depends. If you know a spreadsheet really well, then taking it quite a ways makes a lot of sense. On the other hand when one gets to the point of writing more then 100 lines of VBA and especially into the 500 range, it may be time to use another approach. Same when execution times are very long or data very large. Working with large VBA code bases is kind of nutty but people often get too deep into the I have a hammer so every problem looks like a nail thinking. I have had to work with code like that myself.
That is the thing. I would not do anything advanced in a spread sheet. Just not productive. I would use Python.
As an example, I made a spreadsheet that queried WoW’s auction house API and showed me items, their crafting components, prices and profits from crafting, that was then easily interactable and extendable in the GUI. Doing the same thing in python would have been great up until the point where I want to display the information… getting python to output a proper front end GUI is definitely a more time consuming exercise than using Excel’s built in functionality
Keep in mind Python can interact with spreadsheet formats. So it is very possible to input your data in a spreadsheet , load that data into Python, then dump it into a spreadsheet. Easiest is CSV but I have done direct too.
What approach depends. If you know a spreadsheet really well, then taking it quite a ways makes a lot of sense. On the other hand when one gets to the point of writing more then 100 lines of VBA and especially into the 500 range, it may be time to use another approach. Same when execution times are very long or data very large. Working with large VBA code bases is kind of nutty but people often get too deep into the I have a hammer so every problem looks like a nail thinking. I have had to work with code like that myself.