undefined | Better HN

0 pointsanyidiot14y ago0 comments

Yes, C# is way better for games because you can write mixed format display buffers, but Java isn't that bad as long as its JITed. It limits you to post 2.2 droids, but if doesn't have 2.2 on it, it probably has the shitest of graphics hardware anyway.

I dont get your other complaints though. Show me a developer guide for a console platform that doesn't have outright lies in it and I'll show you my unicorn.

There is a single cross-platform engine, btw, its called Unity, and if you can live with its constraints, then off you go.

Its not in the platform creators best interest to make it compatible with other platforms. So dont hold your breath for write-once that doesnt suck.

0 comments

SomeCallMeTim14y ago

Not fond of C# or Unity, really, but there are plenty of cross platform game engines at this point; see my other post. [1]

Java is still annoying to me, even JITed. It's most of the cruft of C++/OOP without the speed. I'm a Lua fan, and a conversation here isn't likely to sway me. ;)

And it's not just mistakes; it's huge areas of the APIs that are missing or confusing or just plain poorly designed. I've developed for a lot of consoles (not current gen, but XBox/PS2 and older), so I know what you mean about docs being WRONG. But for the most part they let you do what you needed. Android just doesn't in some cases.

Try to do low-latency (or even reliable latency!) audio on Android and get back to me, for an example that Google is basically ignoring.

[1] http://news.ycombinator.com/item?id=2827513

j / k navigate · click thread line to collapse