Re:Java 21 VirtualThreads vs. Clojure Lazy Seqs (from Clojur...
by bafe on Friday October 06, 2023 @03:52PM
(#37795426)
Couldn't agree more! It's particularly disappointing when you need to work on an older java codebase after finishing a Kotlin project. You'll constantly miss features
[ Parent
| on HN ]
Re:Java 21 VirtualThreads vs. Clojure Lazy Seqs (from Clojur...
by vips7L on Saturday October 07, 2023 @08:32AM
(#37801181)
> You'll constantly miss features
Like what?
Re:Java 21 VirtualThreads vs. Clojure Lazy Seqs (from Clojur...
by bafe on Saturday October 07, 2023 @11:38AM
(#37802617)
Nullable types, module level functions, context receivers, nicer type signatures for functions, a better standard library (e.g map works directly on lists without the stream.map crap)
Re:Java 21 VirtualThreads vs. Clojure Lazy Seqs (from Clojur...
by vips7L on Saturday October 07, 2023 @09:40PM
(#37807103)
Personally, these features are not something I feel like I would constantly be missing. I don't constantly feel like I'm missing them after switching from JavaScript, at least for not having to call .stream(), context receivers (which Java provides with ScopedValue), or signatures for functions.
I'll give you nullable types, though I personally don't struggle with null at all.