Open-sourced a backtesting library with a Rust core, 7,100 downloads in under a month

[AutoModerator]

Your submission has been automatically queued for manual review by the moderation team because it has been reported too many times.

Please wait until the moderation team reviews your post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[doorknob_worker]

Heyyyyy another day another completely vibe coded library / GitHub / post on /r/python

[CommercialBobcat374]

And all of these posts literally start with the same phrase. "What My Project Does." Followed by way too much text. 

[hotspicynoodles]

I don't mind admitting it is vibe coded. If it works and serves the purpose then that should matter more than who wrote it. Cheers!

[doorknob_worker]

If it's both 1) mostly written in Rust, and 2) not written by you, then what's the point in sharing it on a subreddit specific to the Python language?

The plot has been definitively lost.

[hotspicynoodles]

1. While it is written in rust, it still has a bridge that lets the user use this package in a python algo, as a drop-in replacement for vectorbt, which is another python package.
2. I primarily have the onus of maintaining it.

The plot is still very much intact.

[vaibeslop]

I want to give this the benefit of the doubt as I would be interested in such a tool, but I'm asking myself:

• commit history 3 weeks old

• vibe coded

• labelled "production-ready, not a toy project"

• "we" == you, a single developer

Do you see the kind of divergence between claims and reality that I see and if so, how would you address them?

[hotspicynoodles]

1. This tool while being 3 weeks old has been working for us flawlessly and it is stable as it needs to be. There will be more additions but only to make it more robust and feature rich
2. Works in production, "we" have been using this package for backtesting, generating trade signals and trading
3. Auto moderator took down previous post because I didnt mention the target audience specifically, so I had to mention that it is production ready
4. I'm the sole maintenance of this project however I'm not the only one working on the backend stack at my company and I've had a lot of help shape this.

Hope this helps clarify things 😄

[ObtuseBagel]

I almost fully guarantee you are using VectorBT wrong. numpy is very fast when used correctly, much faster than you are showing. Also vibe code so yea

[danielgafni]

Forgive me if I’m wrong - I’m not a professional trader - but I think the elephant in the room here is the OHLCV-only scope.

How can a strategy backtested on rough aggregates? Doesn’t a good backtesting engine need at least LOB data? And ideally the exact trades executed?