Code center > Suggestions
Problem of Priority
Griz:
see I had the mistaken impression that DB was a group project ...
kinda like some open source project where people could brainstorm
and share their ideas and contribute to where it was going.
that's where I went wrong.
I do understand that control of information is power ...
and I haven't seen you exibit much interest in what anyone else
has to say or any willingness to allow anyone but yourself to
determine the course of DB.
you have your own vision/agenda and that's all that matters.
you the man ...
it's your show.
good luck
Numsgil:
Your damn passive aggressive attitude is hella annoying.
I am not stopping anyone from adding something to DB. If you want it to do something it doesn't, tell us and either do it yourself or wait and shut the Hell up. That's what it boils down to.
And so far I've done every specific thing you've requested. "Fix the bugs" you said. I did.
Darwinbots is not a Democracy. It's an incredibly fascinating governing system based on interest. People who are more interested in the program have more say in how it develops. I guess it's Interestocracy. It's how all collaborative efforts sort themselves out. People who have the talent, time and interest to be hardcore form the top power users, and users of less interest form the basic user base. The hardcore users are the ones who shape the project.
Your interest does not even need to extend so far as either writing bots or editing the code. shvarz has had probably a larger impact on how DB developed than most other users.
He's done this by working with us on shaping and refining new features. Giving us a clear biological base we can collaborate with.
So far all you've done is bitch. Alot.
I could see alot of potential use coming from your wiki knowledge. If you'd spend half the time working on developing the wiki (specifically DNA pages, etc.) that you spend on bitching, you'd be more respected in the community and your voice would carry more weight.
"But I don't know that stuff" I can hear you moan. Guess what, most of them are outlined in the DArwinbots included help and readme files. And what you don't know you can ask.
PurpleYouko:
I don't see this as anything to do with vision or agenda.
Like Nums said, it is about time and priorities.
For instance, I can only devote significant time to fixing problems with 2.37 when somebody reports a specific problem. Vague issues with file saves and stuff, while annoying, are not really worth my time to do when I have so many other things going on and when a whole new DB version will be coming out soon anyway. I will get around to it eventually though as I would really like to see the VB side of the project kept alive even after the C++ version is released.
You guys wanted a stable version.
As far as I know, 2.36.7 is now that stable version since nobody has reported a crash in weeks.
I have not worked on 2.4 at all and I don't really think Nums will be doing anything significant with it in the near future.
The C++ version is what we are all dying to see. It should be faster and more stable than any other to date.
DB IS open source. and IS a group project. However Nums and myself are the only people who have actually done any of the programming since Carlo bowed out after 2.11 (mostly Nums lately). Others have helped on the wiki and that is greatly appreciated. Others have contributed knowledge that has helped to shape DB into something potentially ground breaking.
Anybody can have an input. Just try to make it constructive. please.
Griz:
--- Quote ---People who have the talent, time and interest to be hardcore form the top power users
--- End quote ---
yes. that comes thru Numbs, loud and clear.
but you see ...
there is also this idea of bringing others along ...
not excluding those who are not as talented as yourself ...
those who make up the base of support for the success of any program ...
the end Users. the general public, the 'commoners'.
if you want this to be anything other than a pet project for your own
programming amusement ... you have to include them.
[how many users do you figure DB really has?]
and I tell you my friend ...
you aren't worth a shit when it comes to communicationg/interacting
with those folks. that is my own direct experience anyway.
now my talent lies in being a 'troubleshooter' ...
in finding 'problems' and 'shortcomings' ... in any system.
I'm a systems control dude ... that's what I know how to do ...
what I get paid very well for doing in the real world ...
and I'm pretty good at it.
part of that is the writing of procedures to guide those who are not
familiar through the steps they need to take to make something work.
ie ... the User/Operator ... to bring them up to speed, so to speak.
now in the world I live in, I also know enough about the details that
I can also come up with the solutions to the problems I sus out.
in this case, with VB, I don't yet have the expertise to go in and isolate
or tell you preciesly what needs to be changed ...
I don't yet know how to make sense of your code.
you wrote the code, know what it means, what it does, and where it is.
I do not.
and therefore you find it easy to blow me off because I can't point
directly at where it is messed up ...
as if there are no problems that actually need to be addressed.
I get that. believe me, I get that.
you, PY ... a few others, including Bots, btw ...
do have the expertise to actually address and make the changes ...
but you first have to be open to seeing that they exist ...
and willing to do something about it.
and I'm sorry ... I just don't see much interest in this area rom you.
you have your own agenda/priorities.
so tell you what I'll do ...
I'll report in as much detail as possible ...
the bugs if/when/where I find them ...
and do what I can at the wiki to help those coming in cold to at least
see if they can get a version working so they don't throw up their
hands in frustration and give up.
that's not easy, as I still have a lot of trouble myself but ...
will at least pass on what I find as I find and resolve it ...
so not everyone has to reinvent the wheel to get DB happening.
am working on getting the full version of PY's Bot tutorial there ...
and Endy is working on documenting the DNA commands ...
and whatever else a 'new user' just coming in might find to be of use.
so you go ahead and program your ass off ...
and don't worry about the rest of us ...
except to please address what specific problems you can should I
or other bring them up.
we aren't making this stuff up you know.
for a start:L
seems Testlund has reported, more than once, that Day/Night doesn't work
in 2.4.A ...
and I can't get Leagues to load without crashing.
I can't tell you 'why' ...
just that it crashes.
if I can get it to write an error.sim when it does ...
will pass it along.
btw ...
'true virtue fears no critique' ;)
PurpleYouko:
Can you get leagues to work in 2.37?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version