News for hackers. Stuff that matters.

A comment on Ditching Excel for Python in a legacy industry. Parent comment

Re:Ditching Excel for Python in a legacy industry by pjmlp on Thursday December 31, 2020 @08:38AM (#25592542)
> I appreciate some of the above is also possible in VBA, but if you're writing an entire model in code and not really using Excel at all, my view is it's better to use a more sophisticated programming language.

Which is why many VBA experts eventually adopt VB.NET instead of jumping into a complete foreign language, with the benefit that is actually compiled to native code (JIT/NGEN), if performance is ever an issue.

[ Parent | on HN ]
Re:Ditching Excel for Python in a legacy industry by cutler on Thursday December 31, 2020 @12:45PM (#25594950)
Yes, I was wondering why Python was the automatic choice considering C#.Net has typesafe native APIs for Excel on Windows.
[ Parent | on HN ]
Re:Ditching Excel for Python in a legacy industry by RobinL on Thursday December 31, 2020 @01:32PM (#25595506)
I was more thinking about migrating away from Excel fully rather than interfacing with Excel from Python.

I agree that to interact with Excel programmatically VBA is a better choice (and no doubt C#/VB.NET as well, but I have no direct experience). For what it's worth, for interacting with Excel and Office more generally, I've always though VBA is extremely well designed.

[ Parent | on HN ]