Where do you stop then?

vB requires MySQL, etc...

I know thats just getting silly. Its just my point is that - well, its irrelevant. Why is it worth less and treated differently? At the end of the day someone has had to work to do it. That shouldn't make it any less valuable if it brings functionality to the user.

Anyhooo - moot point and all. We have differing views on the plausibility of creating and managing LITE versions.
Ive done it - it sucks. I am sure there are many instances when it would be no big deal, but I'm telling you - keeping code in 2 differing systems is a nightmare. I used vb lite as an example. I'm sure there were other reasons behind killing the project - however I can my boys Buzz Lightyear that maintaining 2 differing versions was a key factor as it can be more time consuming and mentally draining than not.

Regardless - no big deal. Just 2 different views on a subject :)

No doubt, but a good civil debate is heathy.

It's work no matter how ya slice it all the way around. Coding, marketing and support.

Buy your marketing and work your code. But I don't think we're gonna get to buy anything here. ;)

Regards

Forget it. You are too far on the other side of the fence to meet anyone half way. You're way is right and everone else's is wrong, no matter what logical and sensible reasoning that is put forth. There is no way you can fully understand the problems something like this would cause here, unless you have had to deal with it on a daily basis like we have. You are looking at it with blinders on, my friend. Blinders with dollar signs on them.

Pot meet Kettle.

Kettle meet Pot.

:rolleyes:

both are black :)

Actually, yes.

Cute.

That's usually what that means. ;)

Boofo, I am game to discuss lots of different possibilities (and have been doing so) to give the community what it is asking for while on the other hand you shout fire and brimstone at the thought of doing something different.

No I can not fully understand the problems 'this' would cause around here. In fact - no one would know if it would even cause any problems (reminds be of a certain y2k bug scenario). All I know is that a community should not be driven by a moderator on a mission but rather the community and customers that make up the site as a whole.

Furthermore - you can put your tar away as I'm over getting painted with it. I personally could give a toss about making money off of my modifications (however it is nice to offset some of my costs). I don't make up the majority of this poll, however I am clearly in the camp I am in for the simple reason that it makes sense to most.

I may not be the sparkliest kettle on the stove, but I make a damn fine cup of Joe ;)

Unfortunately this Poll suggests that voters are emphatically on the far left or far right of this issue, with no provision provided for compromise.
Had it been a Yes / No / Maybe Poll, with a provision to change vote during Poll discussion session, there may have been less # of radical Y/N votes and a greater majority in the Maybe's leading to a more positive discussion towards finding a compromise acceptable by a large majority.

It is in everyones interest to find an amicable arrangement between vB/management, the customer and the coder needs.

Paraphrase The Geek ...
"a community Poll should not be driven by a moderator on a mission but rather the community and customers that make up the site as a whole".

... unless the Poll has been initiated by a mod on a mission.

This thing about running Polls alongside ongoing discussion has been very interesting. Any Polls 101/tipsN tricks info out there?