←
↑
↓
→
You can use arrow keys to navigate in the map.
Loading tree...
-
however
score: 10
Choosing a language to write a trading application that will use Spark and Kafka and will possibly need to run on AWS Lambda is hard...
-
-
because
score: 1
supported by AWS lambda, great love for data science community,
- 0 branch
- ‒
-
-
because
score: 1
both OO and functional, lots of the current crop of data tools appear to lean heavily to it i.e. spark, built for high concurrency
- 0 branch
- ‒
-
because
score: 2
JavaScript
-
because
score: 1
We currently use it on both the frontend and backend and while it has flaws they are known flaws that have known solutions
- 0 branch
- ‒
-
-
-
because
score: 0
functional darling, and not the strongest of arguments but "i would like to"
-
but
score: 1
we need a dedicated keyboard just to type the parenthesis...
- 0 branch
- ‒
- 0 branch
- ‒
-
-
because
score: 0
It's functional, cool, modern and apparently easy to learn. It has a lot of libraries already written and community seems to be growing quite fast
-
but
score: 1
It's not supported in AWS lambda (more or less)
- 0 branch
- ‒
- 0 branch
- ‒
-
-
but
score: 1
it is old, showing its age and i refuse to use eclipse ever again, not an argument more rant
- 0 branch
- ‒
- 6 branch
- ‒
- 0 branch
- ‒
The argument is too complex. You can switch to list view.
Neutral support and objection rate.
last update:
loige
loige
