µTest
kotlin-spark-api
Our great sponsors
| µTest | kotlin-spark-api | |
|---|---|---|
| 2 | 3 | |
| 480 | 437 | |
| -0.6% | 1.4% | |
| 4.2 | 4.9 | |
| 7 days ago | 15 days ago | |
| Scala | 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.
µTest
-
From First Principles: Why Scala?
Let's clarify some points for folks not so familiar with Scala.
> * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.
Scala just chose a strange naming scheme. Other languages would have just increased their major version instead. The scala minor version is increased every few years and not every month or so.
> * Scala has tons of language features and lets people do crazy things in the code.
Actually, that's not true. Or rather: compared to what language?
Scala has surprisingly few language features, but the ones it has are very flexible and powerful. Take Kotlin for example. It has method extensions as a dedicated feature. Scala just has implicits which can be used for method extension.
> * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest. The overuse of DSLs in Scala is really annoying.
I agree with the overuse of DSLs. Luckily that got much better, but older libraries like scalatest still suffer from that.
> * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use, see the JSON alternatives for examples
I think that just comes from using the library in a non-idiomatic way. In most applications, you will need to use the whole json anyways, and then you use (or can use) circe like that:
{
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
What are some alternatives?
ScalaMock - Native Scala mocking framework
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
Diffy
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
scalaprops - property based testing library for Scala
Quill - Compile-time Language Integrated Queries for Scala
Scala Test-State - Scala Test-State.
treelog - Allows logging in a tree structure so that comprehensive logging does not become incomprehensible
Gatling - Modern Load Testing as Code
PyCall.jl - Package to call Python functions from the Julia language
Scalive - Connect a Scala REPL to running JVM processes without any prior setup
dotty - The Scala 3 compiler, also known as Dotty.