kotlin-spark-api
cf020031308
| kotlin-spark-api | cf020031308 | |
|---|---|---|
| 3 | 1 | |
| 440 | 0 | |
| 0.7% | - | |
| 4.4 | 0.0 | |
| 24 days ago | about 2 years ago | |
| Kotlin | ||
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kotlin-spark-api
-
What are your favorite Apache Spark open source libraries?
https://github.com/Kotlin/kotlin-spark-api this definitely needs to be in the language bindings section 😅
-
Migration from Scala to Kotlin
Kotlin should mostly have no problems being called in Scala. Give kotlin-spark-api a look to figure out how would that work the other way around.
-
From First Principles: Why Scala?
Scala is nice for doing things with Spark compared to say, Java, but I really think that Kotlin can do just as well. The only advantage Scala has with Spark is the syntactic sugar. Once there is an API for Kotlin (beyond the preview version), I will be dropping Scala like a bad habit. Kotlin is also concise, has better IntelliJ support, and better Java interop.
https://github.com/JetBrains/kotlin-spark-api
cf020031308
-
From First Principles: Why Scala?
After a number of years with Python, I started a position working in Scala about 6 months ago. I really wanted to learn something new, and become acquainted with functional programming concepts.
I agree with most of the above. A couple of additional thoughts:
sbt -- I still have a lot of coming up to speed to do here, but the manual is like 500 pages and it's somewhat overwhelming. There are tons of little oddities, like why can't I run `sbt --version` and instead have to do `sbt sbtVersion`?
The functional side is fascinating -- I'm still studying the cats library. I can almost describe a Monad! It's a pretty big mountain, though, and there are times where I have doubts whether the benefits will be worth it. Would love to hear some re-assurance! ;)
The ecosystem for microservices seems pretty closely tied to akka & lagom. These are quite complex in their own right and we've been having trouble with the latter in particular. Curious to learn about alternatives. ZIO?
Re: DSLs. Also not a huge fan of DSLs. One refreshing thing about python is that often configuration can just be in Python itself (as in Django, for example). See also:
[1] https://erikbern.com/2018/08/30/i-dont-want-to-learn-your-ga...
[2] https://github.com/cf020031308/cf020031308.github.io/blob/ma...
[3] https://twitter.com/antonycourtney/status/589238574429515777
What are some alternatives?
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
µTest - A simple testing framework for Scala
Quill - Compile-time Language Integrated Queries for Scala
dotty - The Scala 3 compiler, also known as Dotty.
treelog - Allows logging in a tree structure so that comprehensive logging does not become incomprehensible
PyCall.jl - Package to call Python functions from the Julia language