swift-evolution
PeopleInSpace
Our great sponsors
swift-evolution | PeopleInSpace | |
---|---|---|
124 | 9 | |
14,989 | 2,781 | |
0.7% | - | |
9.7 | 8.5 | |
6 days ago | 5 days 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.
PeopleInSpace
-
Kotlin Multiplatform: Android + BE (ktor)
I'm already using this structure with one of my projects and I found the experience really pleasant. There are good examples of doing it, one of them being: https://github.com/joreilly/PeopleInSpace
-
Is there extra benefits of using Koin instead of Dagger Hilt in KMM?
It does work with iOS. You just have to structure it in a way that'll work well. See the People In Space repo to see how it works with iOS
-
Your opinions on the current state of the Kotlin Multiplatform and Kotlin/JS
I mostly walked into the setup. My team already did a lot of heavy lifting. I will try to piece together something for the structure/template. Meanwhile, lot of samples are already present here : https://kotlinlang.org/docs/multiplatform-mobile-samples.html Specially https://github.com/joreilly/PeopleInSpace
- I developed an Android App and now want to go Multi Platform - What's the smartest way to do it? 🤷♀️ (Flutter? Kotlin Cross Platform? Or something else?)
-
View Model Doesn’t Have To Depend on ViewModel
Here's a project using it.
- [Kotlin/JS] Design Kotlin + ReactJS Web app with Material Designing components
-
Kotlin Team AMA #3: Ask Us Anything
For DI take a look at Koin. It's a pragmatic lightweight dependency injection framework for Kotlin developers with multiplatform support. PeopleInSpace sample project uses it.
-
How to start with Ktor + React?
You might be interested in this project https://github.com/joreilly/PeopleInSpace
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.
kvision - Object oriented web framework for Kotlin/JS
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing (navigation) and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.)
kotlinx-datetime - KotlinX multiplatform date/time library
moko-resources - Resources access for mobile (android & ios) Kotlin Multiplatform development
okio - A modern I/O library for Android, Java, and Kotlin Multiplatform.
Ktor-OpenAPI-Generator - Ktor OpenAPI/Swagger 3 Generator
kotlin-wrappers - Kotlin wrappers for popular JavaScript libraries
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing functionality and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.), inspired by Badoos RIBs fork of the Uber RIBs framework
swift-algorithms - Commonly used sequence and collection algorithms for Swift
kable - Kotlin Asynchronous Bluetooth Low-Energy