@fermatslibrary So the entirety of the water body must have cooled down below 4 degrees before any ice appears; that's why deeper water doesn't freeze as quickly as shallow water.
@JLarky Before gitflow, we essentially did the exact same steps, but manually. Gitflow automates all these steps, so we're happy with it, saving a lot of time -- but perhaps we should try abandoning feature branches altogether? Could be even better indeed
@adamhearn Similarly, I found that creating single sized collections is unnecessarily expensive, always taking the vararg collection builder route. It's faster to "Map.empy[...] + (..., ...)", same for Seq, Set
@eatonphil An example of a missing cache abstraction: layered caches. E.g. first cache holds computed data. Second cache holds some computed data derived from the first cache. When a cache entry invalidates, it should do on both; when accessed, both should be 'touched'.
@Krever01 As long as I start from a working example, and be happy with that particular stack (eg laminar, sapui5) I can get very productive. Also I'm blissfully ignorant of most of the js ecosystem
@Hasen_Judi Agree! However, I always prefer rebase over merge as it less messy (than a feature branch which merges main branch in 3 times before being merged itself)
@techsavvytravvy@Feoramund Scala is the only language that comes to mind that offers exactly all of those. JVM, native and js platforms. I'm not saying there aren't other contenders, but those either miss out on features as HK types or have a way smaller ecosystem.
@davesnx I'd say focus on what the language has to offer. The community as a whole, albeit fragmented, is large enough that tooling is quite good and keeps improving. Just pick a productive sub- ecosystem and be productive... Laminar for scala.js is amazing for UI imho
@SaxenaNayan Does the following make sense: while ghiblifying a photo of two boys (both facing right) the top half was "done", but one of them facing left. When the picture was finished, the boy was flipped in the correct orientation! Not just mirrored, different posture. Like it backtracked
@kozlovski Is the decline in Scala code due to dropped features / retired implementations, or is there an active 1-1 rewrite happening from Scala to Java?
@matej_cerny I guess it depends on how functional the rest of the code is? Is it Scala without implicits or Java w/o eyesore syntax? Early returns can be "fine", jumping straight out of three indentations deep is a skill issue