Are VM-based languages becoming viable for Graphics since the move to GPU computing?
        Posted  
        
            by 
                skiwi
            
        on Game Development
        
        See other posts from Game Development
        
            or by skiwi
        
        
        
        Published on 2013-10-21T07:59:00Z
        Indexed on 
            2013/10/21
            10:17 UTC
        
        
        Read the original article
        Hit count: 277
        
Perhaps the title is not the most clear, so let me elaborate it more: I am talking about VM-based languages, by that I mean languages that run on the JVM (java) and for example C#. Also I am talking about 3D graphics, just to be clear.
Lately the trend has been that most computing is being done on the GPU and not on the CPU, and since times the issue with programming games on a VM-based language is that garbage collecting may happen randomly.
So let's take a look which is responsible for what:
- Showing the graphics: GPU
 - Uploading graphics to the GPU: CPU? Needs to be done every frame?
 - Calculating physics constraints: GPU
 - Doing the real game logic (Determining when to move objects (independent of physics calculations), processing AI): CPU
 
Is my list actually correct? And if it is, is for example Java becoming more viable? Or is uploading the graphics (vertices) still the most expensive operation?
Would like to get more insight into this.
© Game Development or respective owner