@rtalalay The bigger mystery is why so many Who stories do work so well. Most stories introduce you to a new set of characters to care about, many introduce you to a whole new world. To have a well-paced story with fun twists, a sense of jeopardy and a satisfying pay off is a tough job.
@mirkoebert My rule of thumb is that the length of a variable's name should be proportional to the size of the scope in which that variable is known.
The length of function's name should be inversely proportional to the size of the scope within which it is known.
I think it's a real lost opportunity that as an industry we haven't standardised on "bobbin" as the name for a group of strings, especially as in a localization file.
@rozkminia first example:
1. first parens - calls constructor (because constructors take presendence over companion object invokes)
2. second parens - calls "invoke" on the instance, returning a function
3. third parens - calls the returned function, thus executing the println("2")
Meta's new #Threads app is 100% native, without any #ReactNative. They used #Compose and #Kotlin for the #Android app, but very little #SwiftUI for their #iOS as they reused lots of existing ObjC and UIKit codebase from Instagram.
https://t.co/iA4x2Z2CQW
https://t.co/Hh5WuSLT5q
📣🚀 The Compose Multiplatform 1.5.0 Preview is out!
Compose Multiplatform 1.5.0-beta01 brings significant functional and performance improvements for iOS, along with other Compose Multiplatform capabilities. Here are some highlights:
✅ The ability to create Dialog and Popup composables in common code
✅ iOS-like scrolling physics
✅ Support for iOS-specific insets in the WindowInsets API
✅ Support for the Dynamic Type for iOS
✅ Simplified iOS resource management
✅ Support for 120Hz Apple devices
✅ Test framework fixes for desktop
Try it out and share your feedback with the JetBrains team!
➡️ https://t.co/DyGuVqsIrj