[DragonByte Tech]

Originally Posted by shimei

There's a menu and a home link.

I could not find the home link at all when I visited your site

Originally Posted by shimei

I must say, updating your testing environment when a problem presents itself on a new update seemingly would solve a lot of these back and forth issues.

Sure, but please also bear in mind that it takes a long time to update my testing environment every time there's an update, vB5 release a lot of Alpha and Beta versions that should never be used in a production environment or on a live site, and also the fact that as a business it's virtually impossible to make money for vB5.

I hope you, in your professional life, do not rely on a single 3rd party company to make good decisions that enables you to make money improving their product. I have done so in the past (when we tried to make mods for vB5), and it was a nightmare.

If you think it's just me, that I'm the only coder that don't want to deal with vB5, then why not look right here on vB.org?
vB3 add-ons: 1,438
vB4 add-ons: 1,959
vB5 add-ons: 73

If vB5 is a platform that supports modification development, then why would there be so few vB5 mods? Purely in terms of numbers, vB5 has 3.72% of the amount of modifications vB4 has. 5.0.0 Gold was officially released four years ago, on 21 February 2013. Four years to make 73 mods, that's quite the slow rate of development, if you were going to say "but vB4 has been out for longer".

On a more personal note, development for vB5 is needlessly complicated, and I don't like working with the platform. Compared to literally every other platform I have worked with (vB3, vB4, XenForo, Zend Framework, Laravel, Symfony), vB5 is easily the worst in terms of whether I am enjoying my time coding.
I hope you can understand and sympathise; coding isn't just "coding", each platform is almost like its own dialect of a language, and there are some dialects you can understand much more easily than others.

All of that being said, I do understand where you're coming from. You paid for a product and it isn't receiving new feature or bugfix updates except for when new vB5 versions necessitate it. It's also true that even if a new non-beta version of vB5 was released, I would not update my testing environment unless someone reported an issue I couldn't fix by asking enough questions.

I hope I have at least helped you understand why I've not been rushing to update whenever vB5 releases a new Alpha or Beta version. I do still intend to keep supporting the vB5 mods in terms of bugfixing whenever someone reports that a new version has broken the existing functionality.


Fillip