Alot of users who say " dont talk to us.. just keep
working" have no urgent need or interest in using bmax
in a serious project.
I wouldn't presume too much on the behalf of others. Maybe it's the other way around, except ofcourse they appreciate that doing, is more important than saying - particularly since their professional project hangs in the balance.working" have no urgent need or interest in using bmax
in a serious project.
Those who do, are now pressured to wait and see, or move on to somthing else.. and thats where communication is really needed.
Well that's pretty much the way the world turns, isn't it? If you had a professional .Net project that had gotten out of hand, and needed to be refactored, your options would be: "Do it manually", "Wait for Microsoft to update Visual Studio", "Use a third party solution". Microsoft telling you that refactoring might be part of VS 2007 isn't going to help with the problem now. Starting to believe Bmax was a bad investment.
Believe what you want. Anyway, welcome to the real world on this one. If you run a business, or in any way sell a product or a service, you're going to have to deal with those whining childish hatemongers because they're paying your bills.
Yeah? How many bills do you reckon 80 bucks pay? About @#!* all. I've not been in the Blitz community as long as some, but I can't recall in the 3-4 years I've been blitzing ever noticing a greater sense of despondency in the community.
It's inevitable once you get enough users. You can't please everyone all the time, thus deductive logic dictates that as the size of all users grow, so does the subset dissatisfied users. They are however a minority - very vocal, but a minority none the less.You'll notice that despite all the vieled threats to leave or switch platform, few actually do.
It would be much easier from a serious developers standpoint to know when his tools will be available to him.
It's a poor craftsman who blames his tools. This way the developer can make executive decisions about software developments.
You should not make executive decisions about unknown quantities. I thought I was going to release a product September 1st.... now I do not know when it is going to be released because I do not know when the gui is going to be released. I continue to lose money every day and it would pacify me (and a lot of others) to know EXACTLY what types of progress are being made on a somewhat regular basis.
Why? It won't make you somehow lose less money. A pig does not grow fatter from being weighed often. I come here every day with hope in my eyes that someone from BRL has posted something, something......
And almost without exception, every day they do. They might not post exactly what you want, but they do post, and do so often. Mark Sibly has more than 3 times as many posts as you, twice as many code archive submissions and an infinite ammount of worklogs more. my superiors are happy knowing that I am still alive and that progress is going good.
Well that's one interesting difference between your superiors and BRLs whining, childish hatemongers. You say you've been here long enough to remember the last time this issue popped up? I've been here long enough to remember when BRL where very forthcoming with information. I can even remember one time when Claire posted that Mark was resting on her couch because he'd spent the last 3 days writting the DirectPlay bit for BlitzBasic. Ever wonder why Claire stopped posting informal private stories like that? Ever wonder why BRL stopped thinking an informed userbase was a good idea? I'll tell you why.Mark once made the mistake of mentioning that he had planned a DX9 update for Blitz3D (you can still see the worklog for it). As you're probably aware, plans changed and everyone was @#!*ed off. Mark had broken his promise, they whined. You see becuase in the rampant gang mentality that seems to be so prevailent here, people are not allowed to change their minds. If you say something, even as a remark, you'd better be prepared to follow through on it, or else.
Want to know the real scary part? The DX9 story isn't even unique, you could probably quite litterally give 100 examples of this.
Sow the wind, and you shall reap the whirlwind. Better not to sow anything at all.