It's a work night and I'm in the mood for some opinions then help with a project. If anything I had a certain library I would like to build down the road, and I want to use Java as my platform anyways for a bigger project, and would like to use Java as a means of prototyping/debugging/testing to make mass data management a breeze for a upcoming project and hope it can replace sql lite.
We all know C++/C are great at building portable, slim, good performance applications for your environment, but have many traps for young players wanting to release their applications on a any day machine, which is why I notice a lot of us use functional programming to test out something before spending hours converting that code to C/C++. Just like the big boys, Google. ;) Of course at the end of the day, it's all about what gets the job done. Even if you use Erlang to do heavy number crunching, and you manage to make it out perform it's self with some hacking.
Anyways my question is to everyone is. What is your prototype language? Did you pick it because it's what your most comfortable with? Or do you go out of your comfort zone to learn something new because the language supported your needs for prototyping. Or is it basically, I have no prototype language, you use what language you plan to launch with?
Edited by ajm113, 31 July 2014 - 12:26 AM.