6 ms·
Go with Clojure.(Most Productive Language on JVM) It is designed for concurrency that you will need when designing live streaming web app.
by neat159 10y ago
Go with Clojure.(Most Productive Language on JVM)
It is designed for concurrency that you will need when designing live streaming web app.
- alexAME 10y agoI'll quote the OP for you: > and the static typing of .NET The last time I checked on Clojure everything was quite dynamic, did they change that ?
- BWStearns 10y agoAnytime you're looking at a wish-list of requirements one or some of them might give way for the sake of advances in the other. The OP wants: static typing, concurrency, good tooling, speed/simplicity in a web framework, non-reliance on big IDEs. If OP were to look at using Clojure/Luminus they might find that the combination of everything except the static typing was sufficient to overcome the lack of static typing (also something like Prismatic Schema to mitigate types might help). I haven't messed around with it enough to say, but there is also JVM interop with clojure so one could write the most type-concerned components in Java (or even in Scala). tldr: failing one requirement of many isn't necessarily a reason to not offer an option if it succeeds on many others.
- alexAME 10y agoIf I suggest Ruby even OP explicitly said he doesn't want Ruby, how is that different from your answer? > tldr: failing one requirement of many isn't necessarily a reason to not offer an option if it succeeds on many others. Yes I agree, if the question allows that approach but in this case, it doesn't.