Plastic SCM developed Semantic Merge and diffing about a decade ago

Perforce is painful, doesn’t have good cloud offering and does not evolve

We have quite a few cloud options actually, with our Helix Cloud option just releasing last week! https://www.perforce.com/perforce-and-cloud

Probably you should explain why this is better than, let's say, just invoking kdiff3 unattended ;-)

kdiff3 doesn't have semantic capabilities, AFAIK.

And I suppose you can invoke the API from anywhere, without depending on a kdiff3 installed (or any other tool installed locally).

That’s it. Call it programatically from your machine regardless of having anything installed.

Well, we try to use standard libraries for all parsers, not develop our own. We use Roslyn for C#, libclang for C... and the great Eclipse CDT for C++

Tested with the Git repo itself, about 26% less merges need manual intervention: https://gmaster.io/mergedroid/analyze/report/gmasterscm/git

Still alpha.

We first launched C# support, a few weeks later we went for Vb.net and now we step out of the .NET framework to release Java support.

Semantic is a free beta and we're giving unlimited licenses to coders sharing feedback.

We're now starting to work on C and then C++ (both using libclang) and hopefully able to handle the Mac OS GUI request soon too (http://plasticscm.uservoice.com/forums/196398-mergebegins)

Thanks!

Thank you! :)

XML would be great to have, definitely... vote! http://plasticscm.uservoice.com/forums/196398-mergebegins?fi...

yep. we started with c#. java will be there too, later c/c++ and after all that it is a matter of listening to our users and react as fast as we can! :-) I'd love to have javascript soon too.

Our designer was on vacation! :)

You might find this one interesting too: https://news.ycombinator.com/item?id=5520321. It is about the new desktop semantic merge tool...