Search this blog

14 January, 2010

Links Explains also some of the choices I made here.

Java 7 performance optimizations: escape analysis (some is already in Java 6, as is the new G1 collector)

Disney PTex texture mapping library released under BSD license. Texturing without explicit UV mapping.

Eric Lippert's Fabulous Adventures in Coding. A lot of nice and entertaining information about the details of the C# language and compiler.

My current two favourite flash indie/art games: Windosill and Canabalt

Demo Tube 2 from Atom's Blog.



Anonymous said...

Great doc. But, after have read it, haven't you the idea the best solution, specially with multi-core systems, is... straight C?

Unknown said...

I believe the document is arguing for a change in how we use OOP languages, not necessarily switching to procedural languages like C.

OOP is still very useful for some larger program structure, they are talking about the cost of bringing the overheads of OOP down into the inner loops of a program. There will always be a tradeoff between abstractions to help improve code reusability/maintainability/clarity/structure, weighed against performance "on the metal".

You wouldn't write photoshop in assembly, but you might write some of the filters in it. To give a metaphor.

Good blog DEADC0DE, I always enjoy reading your posts.

DEADC0DE said...

Even if I hate C++, I don't see how C could really help. It's really an array-of-structures versus structure-of-arrays problem, and I'd say any language I've seen so far has types that prefer the former to the latter. Actually you might argue that switching to SOA is easier in C++, because you can do it "transparently" by crafting class allocators or handles or similar devices...