XLIDE: VBA without excel
github.com
XLIDE: VBA without excel
1–10 of 31 posts
Re: XLIDE: VBA without excel
#2Wonder how extensively VBA is used in today's Excel. I know that macros are considered dangerous but would love to know if there are exceptions for that rule.
On the other hand I wonder why aren't they run in such a sandbox where the most destructive action they can do is to wipe the sheets.
Re: XLIDE: VBA without excel
#3Wonder how extensively VBA is used in today's Excel. I know that macros are considered dangerous but would love to know if there are exceptions for that rule. On the other hand I wonder why aren't they run in such a sandbox where the most destructive action they can do is to wipe the sheets.
https://www.incometax.gov.in/iec/foportal/downloads/income-t...
You need a genuine licensed excel to run the file and prepare returns. Thankfully you can file same returns online on the portal for free so they get a safe pass that way.
Re: XLIDE: VBA without excel
#4Gonna have some fun with this!
Re: XLIDE: VBA without excel
#5Wonder how extensively VBA is used in today's Excel. I know that macros are considered dangerous but would love to know if there are exceptions for that rule. On the other hand I wonder why aren't they run in such a sandbox where the most destructive action they can do is to wipe the sheets.
The world lives on Excel macros. The amount of “shadow it” where the business logic allowing big businesses to run is encoded is unfathomable.
Re: XLIDE: VBA without excel
#6Very cool in theory. Unfortunately it's just 12klocs of a vibe-coded week-end project.
Edit: it's actually 50klocs since the pyOpenVBA dependency is from the same author and has been made the week-end before.
Re: XLIDE: VBA without excel
#7Wonder how extensively VBA is used in today's Excel. I know that macros are considered dangerous but would love to know if there are exceptions for that rule. On the other hand I wonder why aren't they run in such a sandbox where the most destructive action they can do is to wipe the sheets.
I'm not at liberty to talk more about the details, but last year I worked on a project to modernize a process that critically relied on a VBA macro to handle billions (yes, with a B).
> they run in such a sandbox
What makes them interesting is that they can talk with the outside world: API calls, databases, the terminal named after a former Democratic primary candidate...
Re: XLIDE: VBA without excel
#8Very cool in theory. Unfortunately it's just 12klocs of a vibe-coded week-end project. Edit: it's actually 50klocs since the pyOpenVBA dependency is from the same author and has been made the week-end before.
Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
Re: XLIDE: VBA without excel
#9Very cool in theory. Unfortunately it's just 12klocs of a vibe-coded week-end project. Edit: it's actually 50klocs since the pyOpenVBA dependency is from the same author and has been made the week-end before.
Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. https://news.ycombinator.com/newsguidelines.html
> especially of other people's work.
Claude ain't “other people” so I don't think this applies.
By the way, the guidelines proscribe AI-generated comments, so I don't see why AI-generated posts should be treated differently.
Re: XLIDE: VBA without excel
#10Wonder how extensively VBA is used in today's Excel. I know that macros are considered dangerous but would love to know if there are exceptions for that rule. On the other hand I wonder why aren't they run in such a sandbox where the most destructive action they can do is to wipe the sheets.
My first exposure to professional programming was writing VBA and SQL (yes, together) at a massive manufacturing facility that had really old equipment. Now with AI it's much easier to replace the code but VBA still has a stranglehold on legacy systems.