There's a few different markets here:
-The Blitz3D users who are stupid to understand BlitzMax, and want Blitz3D2 with integer handles and a completely procedural interface. This is probably where BRL has made the most money in the past.
-The language-focused people who own businesses and want BlitzMax to keep developing. Mark could charge $1000 for multithreading support, and we would pay it, happily.
-The Max3D faithful, who have no knowledge of what Max3D might be like, but will buy it as soon as it is available, based on their god experience with Blitz3D.
I'm right on the edge of switching to C#, but if I do that, I should switch to DX10, because C# is Windows-only. C++ would still be a terrible move, I think, because it would kill productivity, even after I was completely familiar with it. We are so darn productive as it is right now!
I think in the future we're either going to be C#/DirectX or BlitzMax/OpenGL. If we had some way of doing multithreading it would be much easier of a choice. I am missing out on opportunities with Intel right now because I can only program a single-threaded app. More importantly, our renderer is CPU-limited. Determining the object visibility set is what takes the most time, and that is something that can be easily parallelized.
-The Blitz3D users who are stupid to understand BlitzMax, and want Blitz3D2 with integer handles and a completely procedural interface. This is probably where BRL has made the most money in the past.
-The language-focused people who own businesses and want BlitzMax to keep developing. Mark could charge $1000 for multithreading support, and we would pay it, happily.
-The Max3D faithful, who have no knowledge of what Max3D might be like, but will buy it as soon as it is available, based on their god experience with Blitz3D.
I'm right on the edge of switching to C#, but if I do that, I should switch to DX10, because C# is Windows-only. C++ would still be a terrible move, I think, because it would kill productivity, even after I was completely familiar with it. We are so darn productive as it is right now!
I think in the future we're either going to be C#/DirectX or BlitzMax/OpenGL. If we had some way of doing multithreading it would be much easier of a choice. I am missing out on opportunities with Intel right now because I can only program a single-threaded app. More importantly, our renderer is CPU-limited. Determining the object visibility set is what takes the most time, and that is something that can be easily parallelized.