Adding python support to Excel is like adding a lion to your pack of hunting dogs and then being upset when the lion just goes off and hunts by itself because your dogs are inconsequential to its success.
Ehh I use openpyxl a lot. Makes it easier to visualize data and store measurements and such. Also in my company all the oldies want excel sheets anyways, so it helps.
Your last sentence is the only reason why Python for Excel is viable imo. If there weren't such a glut of legacy workbooks and lack of programmers, Excel wouldn't have much that Python couldn't do better.
Not true at all. The financial world thrives on one-off scenarios for which it would be wasteful to engage programmers every time a new case comes up which is not covered by existing tools. There is a reason EssBase is primarily used through Oracle’s SmartView plugin for Excel.
"How does one patch KDE2 under FreeBSD?" (Russian: «Как пропатчить KDE2 под FreeBSD?», tr. «Kak propatčitʹ KDE2 pod FreeBSD?», [ˈkak prɐˈpat͡ʃitʲ ka dɛ ɛ ˈdva pɐt fri bi ɛs ˈdi]) is an internet meme in Russian Internet culture.
The question was originally posted on the #anime channel of the RusNet IRC network on May 8, 2004. Its text can be translated as follows:
Yeah, I've started packaging my py scripts into single file .exes and sending them to people in my org. Problem is they are often hundreds of mbs for 20 lines of code because of the packages they use.
EDIT: Then again, the packages are what make 20 lines of code useful so I guess thats just the beauty of python.
Yep 100% - portability would be my #1 concern with this. Even python support as an external package wouldn't make much of a difference in the landscape. Theres xlwings, openpyxl already. Unless it becomes built in (either by default or easily enabled) I don't see much changing in terms of actual business use.
To your point: A lot of people, myself included, started with VBA and then learned Python when VBA just wouldn't cut it. If MS truly integrated Python with Excel, it could help spawn a new group of programmers.
VBA was my gateway language too. I needed programmatic control that formulae couldn't give me, and it's been a ride ever since. I can't imagine how much easier things would have been if I could have learned Python instead of that dead language. VBA teaches you that working with classes is hard, and this mindset was probably the greatest impediment to my development as a programmer.
I used to agree 100%, but there were recently a few things where I wanted a quicker and easier view of the affect of some parameter changes. It was pretty trivial but I did it in excel and was pretty happy. I think the real advantage is to (more) quickly input and visual data.
But, I would say 99% of the time, coding is better.
My dad does some pretty intense stuff in excel that should be done in code. He has nested functions and if statements as many as 10 or so deep. It's a debugging nightmare!
Sounds like bad code. Really, nested should go about 3 deep.
I've been guilty of 4 before, but that was only for a search feature that "looped" though a database, so hitting the end meant your search would start from the top again.
Actually, it's one sexy piece of code. I considered printing it out and hanging it in my cubicle, but didn't want to be "that guy" at work.
Anyway, your dad should look into case statements.
I use Excel every day, it's still my go to software for a lot of things. But just because a lot of people are too lazy to learn how to code doesn't change the fact that anything that can be done in Excel can be done in Python at a much larger scale and with significantly better performance.
413
u/decimated_napkin Dec 14 '17
Adding python support to Excel is like adding a lion to your pack of hunting dogs and then being upset when the lion just goes off and hunts by itself because your dogs are inconsequential to its success.