There is a new blog post here. Apparently, they decided to incorporate in Canada and work the project full-time.
I think that's great.
Seems to me it's not as big of a project as twinBASIC (going on 4 years), but still substantial. Let's see where they are in 18 months.
It's exciting to see passion projects like Rubberduck getting full-time attention and proper backing. While it's not quite on the scale of something like twinBASIC, steady progress on community tools is always welcome in the Access and VBA ecosystem.
It's exciting to see passion projects like Rubberduck getting full-time attention and proper backing. While it's not quite on the scale of something like twinBASIC, steady progress on community tools is always welcome in the Access and VBA ecosystem.
I asked an AI: "To a Microsoft Access developer, what are the main differences between MzTools and RubberDuck?"
It gave a lengthy reply, which you can read here.
In summary: Both tools improve the VBA development experience, but they come from very different philosophies. MzTools is a productivity add‑in. Rubberduck is a static‑analysis and refactoring engine that happens to live inside the VBA editor.
"On April 23, 2021, I helped Wayne Phillips introduce the world to twinBASIC at the Access DevCon Vienna conference. I boldly predicted that twinBASIC (along with the Monaco editor) would replace VBA and its outdated development environment by 2025."
"On April 23, 2021, I helped Wayne Phillips introduce the world to twinBASIC at the Access DevCon Vienna conference. I boldly predicted that twinBASIC (along with the Monaco editor) would replace VBA and its outdated development environment by 2025."
I did a little more research, twinBASIC extends and replaces VB6 and VBA compiling to executable. The dll can be used by Access but does NOT replace Access VBA. RubberDuck does not extend or replace VBA only the editor, running as an add-on to Access.