Yes I'm working on an independent platform. I'm one man, and its mythical month, but we have passion and a great team keeping the boat afloat.
We stick with SMF in the meanwhile due to a few reasons,
- its obscure enough to mitigate most wide range attacks.
- it has direct support and upgrade paths for the last 10+ years.
- it ain't broke. let's not fiddle with it.
- we know how to use it. you guys know how to use it. we all do.
We are moving because:
- we wish to automate most functions
- we can better control seo, and take advantage of structured data, canonical urls, and other tactics
- we need a cross concern platform - not just one for forums
- we want more social integration
- we want better performance, and caching - especially in non-logged in states
- we don't use much of SMF's kitchen sink features, and its horrid in many ways to a developer, making adding cool stuff for you guys ridiculously harder
- we want better security and features, using modern maintained libraries and resources that end up being free to us if we shift towards a composer based mentality
- our wants are always ahead of long term support, or even plugins which end up being more harm than good due to shoddy support or workflows, and persistence (see: footnotes and latex)
- we need to migrate at some point sometime anyways - SMF is not a long term solution, but a quick and easy one that made sense at the time