5 ms·
Most people writing VBA code for excel are only informal programmers. For example, I never took a CS course in my life but learned VBA and programming on the jo
by frgtpsswrdlame 9y ago
Most people writing VBA code for excel are only informal programmers. For example, I never took a CS course in my life but learned VBA and programming on the job. Since then I've learned python and other languages but when I'm doing a home project or something I always come back to python. It's just so easy. I was working on a macro the other day in Excel, it took me a couple hours to get it all working but I'm pretty confident that if I could've coded in python I could've banged it out in 20 minutes or less.
Edit: I suppose my point got a little lost. What I mean is that I highly doubt much Excel code is a "big project." It may feel that way when you crawl through some of the hideous VBA coding I've done but much of this is due to the inexperience of the coder and the realities of VBA. Give me python + 4 or 5 libraries and I could recode anything I've ever made in VBA in 1000 lines or less.
- jnwatson 9y agoUnfortunately, there are several companies and hundreds of divisions of companies run entirely out of excel spreadsheets.
- xapata 9y agoAnd integration with Python will be an enormous help for them.
- bluedino 9y agoNext up, get rid of Access
- PlugTunin 9y agoNo one is proposing that we get rid of spreadsheets. I understand, though: you hate VBA. And by extension, Access. But Excel, with or without Python, doesn't mean it can suddenly be used as a relational database. But you knew that. So, what should replace Access?
- rmbeard 9y agoActually, a number of people are proposing this for certain applications. It is also reasonably likely to happen, at very least the spreadsheet is being challenged which will put pressure on spreadsheet vendors and most definitely cut into their marketshare. Adding Python support to Excel seems to be an attempt to resist this.