That's exactly what I said above: most Excel users are non-programmers. Hence Python in Excel would only be used by a subset of Excel power users.
Moreover, having to pay $$ recurring subscriptions for that stack to run open-source software (Python) they could run for free elsewhere mean it'll only be used by commercial/enterprise Windows-stack users who are already locked into some legacy workflow/data built around/glued to Excel. For example, financial users, or users who have some expensive license seat of some enterprise product(s). Means an even smaller subset of users.
Are we? I’m arguing that lua would have been a better choice than python.
Any traditional programming language that you put in excel is going to be a feature mostly for power users, and I think they could pick up lua just as easy as python
Comments
That's exactly what I said above: most Excel users are non-programmers. Hence Python in Excel would only be used by a subset of Excel power users.
Moreover, having to pay $$ recurring subscriptions for that stack to run open-source software (Python) they could run for free elsewhere mean it'll only be used by commercial/enterprise Windows-stack users who are already locked into some legacy workflow/data built around/glued to Excel. For example, financial users, or users who have some expensive license seat of some enterprise product(s). Means an even smaller subset of users.
We're saying the same thing.
Are we? I’m arguing that lua would have been a better choice than python.
Any traditional programming language that you put in excel is going to be a feature mostly for power users, and I think they could pick up lua just as easy as python