Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


Bearhugger

Member Since 05 May 2007
Offline Last Active Yesterday, 12:34 AM

Posts I've Made

In Topic: Mac or PC - Really, this is a programming question.

15 November 2014 - 01:26 AM

I do all platforms. I like keeping a Linux for tinkering with and making sure my game builds on it, and while I don't have a Mac I really want one as my next laptop. As a programmer I'm most productive on Microsoft Windows though. Microsoft can do a lot of stupid things at times but they sure know how to treat their developers with the top-dog IDE and great APIs and frameworks that are well designed and easy to use.

 

So of course my environment of choice to get things done is PC and Visual Studio 2013 as my IDE. C++ for the game and C# for the development tools, with an ounce of Python for the Blender export scripts and eventually some Objective-C for the OS X port when I get my hand on a Mac.

 

On Linux I just code the old fashioned way with vi or gedit. If I ever need an IDE I'd probably go with QtCreator. Most of the code specific to Linux builds is about interacting with the XWindow server so that's not very complex code and I never need a debugger for that. The OpenGL renderer can be debugged on Windows with Visual Studio.

 

On OS X I will of course be using Xcode; I'm making a desktop/maybe mobile game so Cocoa/Obj-C it is and I'll probably need a decent debugger since I'm not a Obj-C programmer.

 

I also tried to mess a bit with Android but I'd rather be flipping burgers than be a Java programmer and the NDK doesn't seem to be working really well on Windows and it requires Cygwin so I guess I'll program on Linux.


In Topic: The 2014 Steam summer sale thread.

19 June 2014 - 10:57 PM

I want to get South Park the Stick of Truth but I'll wait to see if it's going to get lower than 33% off.


In Topic: How much time do you put into programming after your day job?

15 June 2014 - 08:30 PM

These days I mostly do artwork and 3D modeling after work. I'm quite the artsy programmer myself, and after spending 8 hours programming per day, I usually don't have the juice to keep programming after work, and I'd rather relax and do some art. I'll do serious game programming on rainy the week-ends if I need to, but I have most of my game (C++) and editor (C#) already coded anyway so when I am coding after work, it's usually just to improve something that's already there, or to refactor my code and place it into reusable libraries that I can use for other projects.

 

Besides, I'm working at a large gaming company, and I'm pretty sure I'm operating under a "all your code are belong to us" contract, so even if I wanted to write a lot of code, it probably wouldn't be a good idea to write a lot of it while being employed there.


In Topic: Is your IDE hot or not?

14 June 2014 - 02:18 PM

I don't care a big deal about font as long as it's monospace and not stylized. (I don't want to read code in Old English!) I care a lot more about the colors than the actual fonts.

 

My editor of choice is Visual Studio 2013 with the dark theme and most default settings. The only change I made was making the XML doc comments another color, and the XML tags within them very dim so when I read the comments I'm not distracted by the XML formatting. I'm a library writer so I write a lot of XML doc in order to produce a clean API reference.

 

Other IDEs I use, I don't use them nearly enough to customize them. I use Qt Creator for Linux-specific code, but I try to write code standard enough to not have to do that in the first place. I only ever use Xcode and Eclipse when writing and debugging OSX/iOS or Android specific code, otherwise I'll just write it in VS 2013 and then use a little program that will wrap the code and send it to be compiled.


In Topic: How Many Mobile Devices Use Java Now ?

12 June 2014 - 01:14 AM

I doubt Google will be stuck in Java 6 land for that much longer, prolly they'll launch their own language or something, maybe they'll get into some sort of agreement with Oracle about JavaME, but my bet is on "Grab another existing language, extend and tailor it to Android, make sure no one will sue us for it."

 

I've been thinking for a few months that they should just grab Mono and show Oracle their middle finger. Of course they would never do that because .NET is a Microsoft technology and Google and Microsoft hate each other like cats and dogs and it would mean Google would use a MS tech, but I can spot at least 3 big advantages to adopting Mono:

 

1- C# is the closest language to Java (not counting J++ and J#) and, thanks to Java's very slow evolution over its years of existence, C# is way ahead of Java in terms of language features. What this means is that C# can do nearly everything Java does. (Speaking strictly about language capabilities; libraries are another topic.) It makes it easy to adopt C# for Java programmers.

 

2- Want to use native? No more annoying JNI and ugly glue code! Just make a C++/CLI project for interop with Android and code your app in native C/C++. I think you wouldn't even have to use a lib for the interop layer. I'm pretty sure there are #pragma instructions that allow you to specify what should be compiled to native and what should be compiled to managed code. So you'd make it native by default and wrap managed code with #pragma.

 

3- J# and it's Java compatibility library make it really ridiculously painless to reuse Java code with no (or almost no) change. It's not perfect because 1- it was an old version of Java and 2- the point of J# was to help developers migrate their apps from Microsoft's defunct Visual J++ platform to .NET which was full of Microsoft-specific language extensions. But Google could take care of making J# support standard Java 6.


PARTNERS