Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Server Side

If your app is db-bound then use your favorite language. If it requires a lot of CPU time, you'll probably want a language that compiles to native code. Lots of choices there so look for the most productive one given your performance constraints.

Is your application highly distributed, or in need of fault tolerance outside of the database? Erlang might be an ideal fit. Can you build the entire thing out of Java libraries? Then Java's probably your best bet, but...

If you're building something and expecting tons of of concurrent users then you'll probably have to write most of the code from scratch. So keep that in mind when picking a language.

Client Side

If your client is very GUI-based then most cross-platform toolkits may not feel native enough. You might want to consider writing writing separate clients for Windows, Mac OS X, and Linux, If a purely native feel isn't necessary, you could use your favorite scripting language and GTK+, or wxWindows, or QT. Or Java and Swing or SWT.

If you have a unique, or web-like, GUI then maybe Mozilla's XULRunner would be a good choice.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: