Highest Rated Comments
pcuaron39 karma
Will you begin accepting bug reports and feature requests from the whole Excel community?
There’s no way to provide feedback for the Excel/Office team unless you’re a big MSFT partner or an MVP; Excel/Office is one of the products without presence in Microsoft Connect. There’s little software that won’t take feedback from its community, and Excel’s is incredibly large! Besides, you're getting biased feedback if you only listen to part of the userbase.
pcuaron18 karma
The concerns about VBA being insecure, not portable, etc are all valid, but your response seems to be to leave behind the whole VBA affair instead of coming up with something that both solves the problems that VBA solves and doesn't have its shortcomings.
How do I create a UDF with Apps for Office? How do I manipulate charts with it? How do I automate Word or PowerPoint with it?
pcuaron11 karma
Apps for Office is useless for the 95% of the use cases showing up on StackOverflow, OzGrid, MrExcel. Today at about 9am EDT between the last two forums there were about 8000 users online. Are you leaving us all behind?
pcuaron8 karma
How many users does Google Chrome have? They have a public bugtracker. Are there more Excel users than Internet Explorer users? IE has a public bugtracker too!
I don't understand why do I have to befriend someone to send a bug report. Look at this reddit. How many users of this group, among those most interested in the product, do you think will bother submitting anything to a tracker? Most are asking personal questions, or joking, or thanking the team. Very few seem to actually care about the Excel roadmap.
pcuaron74 karma
Given the incredible amount of people coding every day in VBA (look at the forums: StackOverflow, MrExcel, OzGrid, the google groups...),
When will you update the 20 years old VBA Editor to something more modern?
Do you plan to improve the scripting tools, adding things like modern .net operators, string and table methods, etc?
Apps for Office, VSTO and ExcelDNA all address different needs than those of the vast VBA community, which is mostly comprised of analysts scripting trying to solve special cases, or SMBs in which the switch to another technology wouldn’t make sense cost-wise (and who you won’t hear given the lack ways of providing feedback for Excel). We can't use "Apps for Office" for the kind of problems we solve here! Proprietary coding for multiple users in a large enterprise = bad, proprietary coding for analysis = GREAT!
edit: fixed grammar (3 words)
View HistoryShare Link