Language choice?

[TheBeege]

This is kind of a silly thing, but I'm having trouble making a decision.

For back-end services, what technology do we want to use? I'm gonna veto Ruby and Node immediately, since they don't support true concurrency, and this is going to be a web app. I'm also gonna veto PHP because I simply find that to be a nightmare. C(++) would be a sledgehammer for a nail in this instance, so I'm going to veto that, as well.

This leaves us with Python, Go, and Java.

Python's major web framework is Django, and there's also Flask. I'm not sure if either of these support concurrency very well. Python does have a very large community, so support is good.

Go has no really main web framework, but it does work well for small REST APIs via go-restful and/or go-rilla. It does support concurrency very, very well. The major issue with Go is the volume of support materials - it's lacking. It's still a relatively new language.

Java supports concurrency and has been around for a very long time, but it has a great deal of overhead when it comes to startup and tear-down. The JVM can be a pain. Java also has a massive user base worldwide.

Given these, I'm leaning towards Java, though I personally favor Go. Thoughts?

[anthonyselkowitz]

Would using Python backend link better to using Python for analytics? I
know there's some support for Java and Python through Jython.

I'm a pretty big R user, but I'd also use Python for data projects.

On Fri, Jul 22, 2016 at 10:34 AM, TheBeege notifications@github.com wrote:

This is kind of a silly thing, but I'm having trouble making a decision.

For back-end services, what technology do we want to use? I'm gonna veto
Ruby and Node immediately, since they don't support true concurrency, and
this is going to be a web app. I'm also gonna veto PHP because I simply
find that to be a nightmare. C(++) would be a sledgehammer for a nail in
this instance, so I'm going to veto that, as well.

This leaves us with Python, Go, and Java.

Python's major web framework is Django, and there's also Flask. I'm not
sure if either of these support concurrency very well. Python does have a
very large community, so support is good.

Go has no really main web framework, but it does work well for small REST
APIs via go-restful and/or go-rilla. It does support concurrency very, very
well. The major issue with Go is the volume of support materials - it's
lacking. It's still a relatively new language.

Java supports concurrency and has been around for a very long time, but it
has a great deal of overhead when it comes to startup and tear-down. The
JVM can be a pain. Java also has a massive user base worldwide.

Given these, I'm leaning towards Java, though I personally favor Go.
Thoughts?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#10, or mute the thread
https://github.com/notifications/unsubscribe-auth/AG18_Fo1JNUgELJsOsUoWPF1nAQjwZw7ks5qYNTugaJpZM4JS0Pr
.

Thanks,
Anthony
Selkowitz

[TheBeege]

Hmm... My understanding of the more data science stuff you're talking about involves work after extracting data from the data source (in this case, the app). It's more focused on interactive, ad-hoc work with data rather than a standing system. These two together mean there's no dependence on the language of the system you're pulling from, as long as you have a way to pull the data. I'm a mild data junky, too, so I'll make sure it's easy to get data out.

[DesireeVanHaute]

I've got no input on this. My only experience with Python was physics 2 at GT and in lab I use matlab- which wouldn't be helpful here.

On Jul 22, 2016, at 8:08 AM, TheBeege notifications@github.com wrote:

Hmm... My understanding of the more data science stuff you're talking about involves work after extracting data from the data source (in this case, the app). It's more focused on interactive, ad-hoc work with data rather than a standing system. These two together mean there's no dependence on the language of the system you're pulling from, as long as you have a way to pull the data. I'm a mild data junky, too, so I'll make sure it's easy to get data out.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.