swift-evolution
PeopleInSpace
| swift-evolution | PeopleInSpace | |
|---|---|---|
| 155 | 9 | |
| 15,857 | 3,347 | |
| 0.2% | 0.7% | |
| 9.8 | 8.0 | |
| 7 days ago | 11 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
- 链接器错误的一波三折
-
Swift 6.3 Released
Here are the evolution proposals that landed in 6.3:
https://www.swift.org/swift-evolution/#?search=6.3 -
Why Objective-C
>[1] https://github.com/swiftlang/swift-evolution/blob/main/propo... -- apologies to the authors, but even as a previous C++ guy, my brain twisted at that. Inside Swift is a slim language waiting to get out... and that slim language is just a safer Objective C.
These kinds of features are not intended for use in daily application development. They're systems-language features designed for building high performance, safe, very-low-level code. It will be entirely optional for the average Swift developer to learn how to use these features, just in the same way that it's optional for someone to learn Rust.
-
Swift is a more convenient Rust
https://github.com/swiftlang/swift-evolution/blob/main/propo...
https://github.com/swiftlang/swift-evolution/blob/main/propo...
https://github.com/swiftlang/swift-evolution/blob/main/propo...
https://github.com/swiftlang/swift-evolution/blob/main/propo...
All of these changes improve the ergonomics of async/await. Fewer hops and a better alignment of when one would expect a hop to occur.
https://github.com/swiftlang/swift-evolution/blob/main/propo...
async defer is nice too but it's not in the 6.2 public release AFAICT.
- Swift: Nonexhaustive Enums
-
The end of the kernel Rust experiment
The practical reality is arguably more important than beliefs. Apple has, as it turns out, invested in trying to make Swift more suitable for kernel and similar development, like trying to automate away reference counting when possible, and also offering Embedded Swift[0], an experimental subset of Swift with significant restrictions on what is allowed in the language. Maybe Embedded Swift will be great in the future, and it is true that Apple investing into that is significant, but it doesn't seem like it's there.
> Embedded Swift support is available in the Swift development snapshots.
And considering Apple made Embedded Swift, even Apple does not believe that regular Swift is suitable. Meaning that you're undeniably completely wrong.
[0]:
https://github.com/swiftlang/swift-evolution/blob/main/visio...
-
Bjarne fix your freaking language
Swift gained limited support for “typed throws” in Swift 6.0 (2024).
https://github.com/swiftlang/swift-evolution/blob/main/propo...
I say limited because the compiler doesn't (yet, as of 6.2) perform typed throw inference for closures (a closure that throws is inferred to throw `any Error`). I have personally found this sufficiently limiting that I've given up using typed throws in the few places I want to, for now.
-
Swift SDK for Android is Here: Build Native Android Apps with Swift
Vision document (in review)
-
The Swift SDK for Android
> Can I now build my app in Xcode with an Android target and use that binary in the Play Store?
No. The vision document[1] lays out the direction of travel. Currently the focus is on shared business logic and libraries, rather than full native applications (although that's certainly a goal, albeit a very long term one).
[1]: https://github.com/swiftlang/swift-evolution/pull/2946/files
-
SwiftMocking: Rethinking Test Doubles with Modern Swift
What makes SwiftMocking unique isn't just its API, but its architectural foundation. Built on Swift 5.9's parameter packs, phantom types, and macros, it represents a complete rethinking of how test doubles should work in a type-safe language.
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?
KEEP - Kotlin Evolution and Enhancement Process
pomodoro-scheduler - This is a simple and configurable pomodoro timer [Moved to: https://github.com/emenjivar/pomodoro-timer]
swift - The Swift Programming Language
kvision - Object oriented web framework for Kotlin/JS
kotlin-wrappers - Kotlin wrappers for popular JavaScript libraries
knbt - Kotlin NBT library for kotlinx.serialization