Documentation request - reasons why to use instead of Bridge

[mcintyre321]

I've dabbled with Bridge.net in the past, and remember it being a good platform. Could you explain a bit more in the readme about the motivation for h5, in particular what shortcomings bridge.net has that this addresses. From reading the readme I see that the loss of Retyped is a downside to h5, but I don't know all the upsides.

[theolivenbaum]

Hi @mcintyre321 - thanks for the advice, I'll try adding more info on the readme.

I've been using Bridge also for quite some time, and I decided to fork it early this year to be able to update, optimize and fix bugs on it. I think the biggest advantage besides the netcore3.1 update (which brings proper multiplatform support) is actually having a single repository for the entire code-base, which makes it is much easier to develop and improve the code.

For the Retyped support - to be honest my experience there was very disappointing, due to the missing javascript files in the packages, and no version information on the package meaning we had to hunt which version was matching it. We since then decided it was much easier to manually write wrappers ourselves on top of the libraries we use (like we did for https://github.com/curiosity-ai/plotly-sharp).

[mcintyre321]

So it's because bridge don't have (or can't execute) their roadmap quickly enough? i.e. 3.1 isn't in their plans?

Will you contribute back, or is this a hard fork?

[theolivenbaum]

It's a hard fork. I've discussed with their team before regarding how to collaborate, but they've had no resources for a while to support Bridge, and I didn't want to do incremental changes, but a significant cleanup on the code, repositories, project structure, etc. which would have been impossible without active collaboration with them as they own the repositories and CI/CD infrastructure.

I think net core has been on their roadmap for over 2 years now.

I do try to contribute bug fixes back to them as possible.