vB3 hacks as opposed to vB2 hacks - are you going to do the boost with your hacks?

[KuraFire]

We all know vB2's code, more or less. We know the engine, the system, we know all the ins and outs to it.

Some of us also know all about vB3's code, the fact that not a single line of code from vB2 seems to have resurfaced in vB3, the fact that the engine is so much more powerful, extensive, modular, complete. The fact that there is a ton more stuff to keep in mind when making vB3 hacks.

Nice little facts. But here comes the issue.

vB3 is a major improvement over vB2 in every aspect, down to the tiniest little things. Are you going to make your hacks for vB3 have the same boost in quality?

And with that, I mean: are you going to make your hacks be 100% Phrases based, work with all the new techniques used in vB3 itself, or will you just make sure that your hacks from vB2 are rewritten so that they work on vB3?

Or will you start off with just converting your hacks to make them work, and then after that, slowly, when you learn the code and system of vB3 some more, begin to make vB3 hacks that fully utilize the Power of vB3 in every aspect?


Me, I'm preparing about 20 major hack releases, each of which being written with the quality feel of vB3 in mind. Complete with XML-based data files (phrases, templates, settings), installer files (Hack Tracking Log installers, see my sig), flexibility unlike anything we've ever seen in any vB2 hack before, caching techniques, reusability, modularization to the max, etc.
All this takes a LOT more time (work, effort) to do, as there is a lot more planning and coding to do to keep things flexible, but I think vB3 deserves the type of hacks that feel up to par with vB3's own code, and not vB2's code.
Of course, on top of this I'm also developing systems that will make vB3-hacking a lot easier for everyone from n00b to pro, as well as some vB3 `Hacking Standards` that should guarantee maximum usability and flexibility when followed...

So, what are your hacking plans?