swift-evolution
Splitties
Our great sponsors
| swift-evolution | Splitties | |
|---|---|---|
| 124 | 3 | |
| 15,003 | 2,445 | |
| 0.7% | - | |
| 9.7 | 7.8 | |
| about 15 hours ago | 7 months ago | |
| Markdown | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
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.
swift-evolution
-
Byte-Sized Swift: Building Tiny Games for the Playdate
[A Vision for Embedded Swift](https://github.com/apple/swift-evolution/blob/main/visions/e...) has the details on this new build mode and is quite interesting.
> Effectively, there will be two bottom layers of Swift, and the lower one, “non-allocating” Embedded Swift, will necessarily be a more restricted compilation mode (e.g. classes will be disallowed as they fundamentally require heap allocations) and likely to be used only in very specialized use cases. “Allocating” Embedded Swift should allow classes and other language facilities that rely on the heap (e.g. indirect enums).
Also, this seems to maybe hint at the Swift runtime eventually being reimplemented in non-allocating Embedded Swift rather than the C++ (?) that it uses now:
> The Swift runtime APIs will be provided as an implementation that’s optimized for small codesize and will be available as a static library in the toolchain for common CPU architectures. Interestingly, it’s possible to write that implementation in “non-allocating” Baremetal Swift.
-
Borrow Checking Without Lifetimes
I may be out of my depth here as I've only casually used Rust, but this seems similar to Swift's proposed lifetime dependencies[1]. They're not in the type system formally so maybe they're closer to poloneius work
[1]: https://github.com/apple/swift-evolution/blob/3055becc53a3c3...
-
Functional Ownership Through Fractional Uniqueness
Swift recently adopted a region-based approach for safe concurrency that builds on Milano et al’s ideas: https://github.com/apple/swift-evolution/blob/main/proposals...
- Swift-evolution/proposals/0373-vars-without-limits-in-result-builders.md
- The Swift proposal that removed the ++ and –- operators (2017)
-
Crafting Self-Evident Code with D
No, it's not. Refcounting CAN be a garbage collection algorithm, but in Swift it's deterministic and done at compile time. Not to mention recently added support for non-copyable types that enforces unique ownership: https://github.com/apple/swift-evolution/blob/main/proposals...
- Statically link Swift runtime libraries by default on supported platforms
- (5.9) What is the point of a SerialExecutor that can silently re-order jobs?
-
Mac shipments grow 10%, as all major PC brands see downturns.
You can stackallocate buffers with unsafe Swift but it's not exactly fun to use. https://github.com/apple/swift-evolution/blob/main/proposals/0322-temporary-buffers.md
-
Can someone explain how Task really works in terms of threads (I couldnt ask all the questions with the swift team today)?
If the docs do not suffice, read the concurrency proposals of Swift Evolution. The authors describe the semantics in a very detailed way there.
Splitties
-
Useful utilities, extensions, base classes
https://github.com/LouisCAD/Splitties don’t use it because I think it leads to dependency bloat but there you go
-
Future of single activity with multiple fragment!!!
I've successfully used single activity with multiple fragments in the past. In one app we even dropped the fragments and inflated custom views (fueled with splitties: https://github.com/LouisCAD/Splitties when compose was in early stage) with screens logic implemented as suspendable functions.
-
Kotlin Team AMA #3: Ask Us Anything
XML is not the only way to use Android Views. With Kotlin, you can get pretty compelling results: https://github.com/LouisCAD/Splitties/tree/main/modules/views-dsl#ide-preview
What are some alternatives?
compose-multiplatform - Compose Multiplatform, a modern UI framework for Kotlin that makes building performant and beautiful user interfaces easy and enjoyable.
kable - Kotlin Asynchronous Bluetooth Low-Energy
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
multiplatform-compose - A demo to show usage of Jetbrains Compose in Android and iOS.
kotlinx-datetime - KotlinX multiplatform date/time library
kotlin-multiplatform-libsodium - A kotlin multiplatform wrapper for libsodium, using directly built libsodium for jvm and native, and libsodium.js for js targets.
okio - A modern I/O library for Android, Java, and Kotlin Multiplatform.
kotlin-libui - Kotlin/Native interop to libui: a portable GUI library
PeopleInSpace - Kotlin Multiplatform project with SwiftUI, Jetpack Compose, Compose for Wear, Compose for Desktop, Compose for Web and Kotlin/JS + React clients along with Ktor backend.
kotlin-wrappers - Kotlin wrappers for popular JavaScript libraries
swift-algorithms - Commonly used sequence and collection algorithms for Swift
kotlinx.html - Kotlin DSL for HTML