Is this the first DirectX that can use display lists? Because I was reading the DX10 explanation on Tom's Hardware and it seems that they are either referring to that or the new Geometry shaders? If they are talking about display lists, OpenGL has had those for quite a while.
I agree linux needs standards for many things. Audio platforms. Package formats. Installation methods in general. But this is only if someone wants to make it user friendly and Windows/Mac like. Many people in the community want to see linux continue on it's current path of inovation. Wrather than standardization. Seome see standardization as something that would slow innovation down. But if we standardize loosely on things like making using only alsa, and only rpms or debs for example. I don't believe this would slow the community. If anything it would speed up inovation and application development because then there are fewer ways for things to become difficult to use. More people would adopt the platform, and develop themselves.
Let's take a look at the game industry, the same code is often used over and over, or at least the same algorithms because you can't afford to loose efficiency in your engine. Especially with modern game engines where the best cards on the market still choke... FarCry? Doom3?. Sharing of code in games is not required, but as an earlier post said, why reinvent the wheel?
Is this the first DirectX that can use display lists? Because I was reading the DX10 explanation on Tom's Hardware and it seems that they are either referring to that or the new Geometry shaders? If they are talking about display lists, OpenGL has had those for quite a while.
I hope that this doesn't make the next couple of generations of coders sloppy ones because they have immense resources at their disposal.
I agree linux needs standards for many things. Audio platforms. Package formats. Installation methods in general. But this is only if someone wants to make it user friendly and Windows/Mac like. Many people in the community want to see linux continue on it's current path of inovation. Wrather than standardization. Seome see standardization as something that would slow innovation down. But if we standardize loosely on things like making using only alsa, and only rpms or debs for example. I don't believe this would slow the community. If anything it would speed up inovation and application development because then there are fewer ways for things to become difficult to use. More people would adopt the platform, and develop themselves.
Shopping list: 1: Server(X-BOX) $150 Check...
Let's take a look at the game industry, the same code is often used over and over, or at least the same algorithms because you can't afford to loose efficiency in your engine. Especially with modern game engines where the best cards on the market still choke... FarCry? Doom3?. Sharing of code in games is not required, but as an earlier post said, why reinvent the wheel?