ea-async
kotlin
ea-async | kotlin | |
---|---|---|
4 | 208 | |
1,362 | 47,521 | |
0.2% | 0.5% | |
0.0 | 10.0 | |
about 2 years ago | 4 days ago | |
Java | Kotlin | |
GNU General Public License v3.0 or later | - |
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.
ea-async
-
Fluent: Static Extension Methods for Java
I feel like this misses the reason I like extension methods: discoverability.
With an extension method, I can do `object.` and my IDE will tell me what can be called on object. With a static helper method, it isn't as easy to know what is available. I need to know which helpers actually exist.
Since this doesn't have IDE support, it doesn't help discoverability. I'm not going to get nice autocomplete that shows me what is available. In fact, my IDE is going to highlight it as a bug. If I have a spelling mistake, I won't be able to easily pick it up - I'll assume it's just the normal complaint for all of these fluent extension methods.
That makes this simply syntactic sugar rather than something that actually helps me discover things more easily. It then hurts readability and navigation since I can't easily click through to get the definition of the method.
On a more general note about Java, things like this are one of the reasons I don't love the Java ecosystem. People try to change the behavior of Java in really hacky ways that don't work well. I understand that it's an attempt to overcome shortcomings in the language, but when one looks other languages it becomes clear that Java could have just evolved the language to be better. Java has lots of good things and I'm not looking to argue that. However, when I look at things like this, it makes me think that Java needs to really address the core language.
Instead, we get lots of tools like this which might be nice, but make it really hard to understand what's going on. Electronic Arts created an async/await library that'll do crazy stuff to let you do async/await style programming (https://github.com/electronicarts/ea-async). Yes, Java is doing good things with structured concurrency and Project Loom, but the point is how people keep trying to work around the language. There are so many POJO generators it isn't funny: AutoValue, Immutables, JodaBeans, Lombok, and more I'm probably forgetting. Java records don't fulfill everything (and they're at least a decade late). Java doesn't support expression trees for lambdas so libraries sometimes do crazy hacky things to make that exist.
Java is a great piece of technology, but it feels like people are often trying to overcome issues with the language through really hacky means in a way that I don't see in other languages. Java is getting better about modernizing the language, but it still feels like people are running against the language more than in other ecosystems.
-
What are some forbidden, broken, possibly even black magic stuff that you can do in Java and to that extent, JVM in general?
https://github.com/electronicarts/ea-async via preprocessing the bytecode in the jar or at start time
-
Concrete reasons why one would choose java over node.js?
Like I mentioned in the other comment - EA Async can help there, it brings async-await semantics to CompletableFutures and resilience4j has CompletableFuture decorators that you can apply to get retries, circuit-breakers and all the good stuff they offer.
- Async await in Java
kotlin
- Kotlin 2.0 RC1
-
Implementing an Auto-logout Feature for Android in Kotlin
A basic understanding of Kotlin and programming in general (OOP).
-
Kotlin and Azure Functions - Automating the deployment
Being somewhat allergic to coding in Java (this is a personal thing, if you like Java then good for you) I decided to try out writing the code using Kotlin from JetBrains instead. I'm already using IntelliJ as I work with Apache Spark using Scala, so the tooling was already there and ready to go for this.
-
Top Paying Programming Technologies 2024
25. Kotlin - $78,207
- Fuckjava.com Redirects to Kotlinlang.org
- Kotlin 2.0.0 Beta 2
-
Tests Everywhere - Kotlin
Kotlin testing with Kotest and MockK
- Kotlin 2.0.0 Beta1 is out
-
🎉 Kotlin Multiplatform is now STABLE!
Congrats to our friends at Kotlin. 🚀 After years of growth and development, KMP reaches a pivotal milestone with 1.9.20. We’ve been on team Kotlin Multiplatform since day one, and the best is yet to come! Learn more 👉 https://touchlab.co/kotlin-multiplatform-is-stable
-
Regarding Lenses, Prisms and Optics
Another option could be to check out Kotlin. It's a JVM language that while still object-oriented has may functional syntax features.
What are some alternatives?
Reactive Streams - Reactive Streams Specification for the JVM
solidity - Solidity, the Smart Contract Programming Language
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
scala - Scala 2 compiler and standard library. Bugs at https://github.com/scala/bug; Scala 3 at https://github.com/scala/scala3
Quasar - Fibers, Channels and Actors for the JVM
Flask - The Python micro framework for building web applications.
navigo - A simple vanilla JavaScript router.
puppeteer - Node.js API for Chrome
CreepyCodeCollection - A Nonsense Collection of Disgusting Codes
kotlinx.coroutines - Library support for Kotlin coroutines
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
Express - Fast, unopinionated, minimalist web framework for node.