i think that the last two replys are from a narrow perspective on things...
reasons... objective, cold hard factual reasons are as follows...
1- given a choice between BMax (app $100) and vb.net (app $0), both similar coding languages, vb more mainstream OOP, vb more documented... well, what do you think an average indie coder might opt for... i would give the advantage here to vb.net...
2- blitz3d is supposed to be the premier, flagship product... well, where is it's successor... we are left to languish in the middle earth of not having one, searching and hoping for a usable 3rd party 3D module...
3- finally, noone said blitzmax was going in the wrong direction Sash... what i said, and if you'd read it without injecting anything else into it, was that the whole direction that the devs are moving us towards is wrong... Blitz3D was a solid performer... enhance that, make it available to a wider audience (via an sdk) for those who want to use the latest tools to code against it... then go ahead with the 'maxes...
right now all we have is a language that is in direct competition for the hearts and minds with other languages... others that are firmly entrenched in the minds of programmers (c++, vb.net, c#, java)... before blitz3d was unique... bmax doesn't have that compelling uniqueness that B3D had...
why use bmax to code irrlicht based 3D apps, for example, when you can just as easily use c++, or vbnet for free... or java... or delphi...
those of you expecting to see the BMax 3D module by decemeber may be sadly dissapointed... too many things have yet to be finalized regarding the future of directx, as well as this osx dual binary thing for that to happen... and even if it does show up, to assume it will be usable for game development right off the bat, well, that's just being overly optimistic at least...
as far as mark's abilities here, that has nothing whatsoever to do with this disscussion... so that can be left out... we all know what he's given us in the past... that's not even a factor here...
try and detach your emotions from the discussion for a second and take an object, pragmatic view at the existing circumstances as they are right now... your replys would be more relevant to the topic, and be more conducive to providing a valid viewpoint... reardless of the position you take...
--Mike
reasons... objective, cold hard factual reasons are as follows...
1- given a choice between BMax (app $100) and vb.net (app $0), both similar coding languages, vb more mainstream OOP, vb more documented... well, what do you think an average indie coder might opt for... i would give the advantage here to vb.net...
2- blitz3d is supposed to be the premier, flagship product... well, where is it's successor... we are left to languish in the middle earth of not having one, searching and hoping for a usable 3rd party 3D module...
3- finally, noone said blitzmax was going in the wrong direction Sash... what i said, and if you'd read it without injecting anything else into it, was that the whole direction that the devs are moving us towards is wrong... Blitz3D was a solid performer... enhance that, make it available to a wider audience (via an sdk) for those who want to use the latest tools to code against it... then go ahead with the 'maxes...
right now all we have is a language that is in direct competition for the hearts and minds with other languages... others that are firmly entrenched in the minds of programmers (c++, vb.net, c#, java)... before blitz3d was unique... bmax doesn't have that compelling uniqueness that B3D had...
why use bmax to code irrlicht based 3D apps, for example, when you can just as easily use c++, or vbnet for free... or java... or delphi...
those of you expecting to see the BMax 3D module by decemeber may be sadly dissapointed... too many things have yet to be finalized regarding the future of directx, as well as this osx dual binary thing for that to happen... and even if it does show up, to assume it will be usable for game development right off the bat, well, that's just being overly optimistic at least...
as far as mark's abilities here, that has nothing whatsoever to do with this disscussion... so that can be left out... we all know what he's given us in the past... that's not even a factor here...
try and detach your emotions from the discussion for a second and take an object, pragmatic view at the existing circumstances as they are right now... your replys would be more relevant to the topic, and be more conducive to providing a valid viewpoint... reardless of the position you take...
--Mike