8,591 karma · joined February 25, 2014
This seems disingenuous at best, or it's a symptom that I've noticed as a user more often that your JDK team seems to have blinders on and dismisses/ignores most other languages even if feature have proven themselves 10 times over.
There's several features Java added or is trying to add, usually 5-10+ years later than Kotlin, and that's ignoring Scala:
* Local type inference
* Switch expressions
* Records, although I found them barely usable because there is no copy() method or with-ers
* String templates unsuccessfully
* A very stripped down version of smart-casting with switch pattern matching
I'm sure there's tech-debt and esoteric compatibility concerns which make evolving Java hard, but from a developer's perspective it's just glacial to evolve and the result is weaksauce.
This really depends on the provider, it's a very fast model with ours
The Dutch government can famously prevent sales of German and Luxembourgish companies yes.
It seems the author has too high expectations of this feature, or vim is using an incorrect path to store this is they want to make it available more reliably
I would argue the surge in vintage clothing ecosystems is an indication there is an unmet demand.
If you just want a quick meal there's more than enough places but you generally order at the counter there, don't sit and wait for a server.
Per the writing, reading AI writing is like having something taste "chemical". Not very specific, but still a very recognizable and bad taste that makes it hard to enjoy and marks the thing as low quality.
Many people suspect it's the year-long migrating to Azure and all their products instead of the things they have been using.
Easily misremembered and meme-able.
They literally asked why they couldn't write JsonObject.of(Map.of(...))
The kotlin stdlib-adjacent json lib does it like this
buildJsonObject {
putJsonArray("providers") {
add("SUN")
add("SunRsaSign")
add("SunEC")
}
}
[1] https://kotlinlang.org/docs/type-safe-builders.html