swift-evolution
swift-corelibs-foundation
Our great sponsors
swift-evolution | swift-corelibs-foundation | |
---|---|---|
124 | 17 | |
14,989 | 5,180 | |
0.7% | 0.6% | |
9.7 | 8.8 | |
6 days ago | 1 day ago | |
Markdown | Swift | |
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.
swift-corelibs-foundation
-
Mixing Swift and C++
a : https://github.com/apple/swift-corelibs-foundation/blob/main...
I wouldn't want to be the guy relying on this table advancement for this project. The fact that they're rewriting it in pure swift probably says a lot about the quality of the current approach.
b: makes absolutely no difference from a developer perspective. if you want to run threads in swift you're going to use gcd.
c: my take with all apple software tech has been to wait until they've dogfooded their own tech long enough to make it useable. Worked very well for me so far, thank you very much.
- Roast my supposedly impressive iOS developer resume
-
Apple Announces Full Swift Rewrite of the Foundation Framework
Correction: rewrite of PARTS of Foundation
There already was an open-source project to rewrite ALL of foundation, but it had stalled on the shores of having to re-implement everything:
https://github.com/apple/swift-corelibs-foundation
-
Apple's Swift rewrite of its Foundation framework will be open source
The (shitty) old Linux implementation has been on GitHub for years.
-
There is no “software supply chain”
Sigh... The traditional argument is that every dependency is of the same quality and trustworthiness of the language Standard Library.
If I use the SL, then I should also have no problem using some lashed-up chimera that has a dependency hierarchy that spans three continents.
Like I said, I'll do things my way.
For the record, here's a peek at some of the "worthless" packages that I use in my own work: https://github.com/RiftValleySoftware
Also, for the record, here's the Swift Foundation Library: https://github.com/apple/swift-corelibs-foundation
It has plenty of open issues: https://github.com/apple/swift-corelibs-foundation/issues
If every dependency chain can match these, yhen I'll be open to considering them.
As it is, I do use the occasional external package, but I'm picky.
-
A Completely Open-Source Implementation of Apple Code Signing and Notarization
CoreFoundation is (partially?) open-source and cross-platform now: https://github.com/apple/swift-corelibs-foundation
-
Show HN: Particles – the URL contains the whole program code
Partly this is doable because although RFC 2616 specifies a max URL length of 2048 bytes, most browsers allow much longer, with Chrome and Firefox allowing at least 64k chars (that's what they'll display but it seems like more is happily processed), while Safari allows URL strings up to 2GB in size[1]!
[1] https://github.com/apple/swift-corelibs-foundation/blob/b23d...
-
What is missing in the Swift ecosystem?
Regarding your point #3, Swift does indeed have an open-source cross-platform implementation of Foundation. swift-corelibs-foundation
-
Is "import Foundation" always required in Swift code?
Foundation is open source and (mostly) works on Linux. What else do you want to see “opened up?”
-
Apple’s use of Swift and SwiftUI in iOS 15
Foundation is not the standard library of Swift. Swift has its own standard library that is bundled with the language on all platforms that are supported.
And Foundation itself isn't written in Swift, a good portion is written in C.
> A significant portion of the implementation of Foundation on Apple platforms is provided by another framework called CoreFoundation (a.k.a. CF). CF is written primarily in C and is very portable. Therefore we have chosen to use it for the internal implementation of Swift Foundation where possible. As CF is present on all platforms, we can use it to provide a common implementation everywhere.
https://github.com/apple/swift-corelibs-foundation/blob/main...
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.
JWM - Cross-platform window management and OS integration library for Java
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
Unwrap - Learn Swift interactively on your iPhone.
kotlinx-datetime - KotlinX multiplatform date/time library
google-api-objectivec-client-for-rest - Google APIs Client Library for Objective-C for REST
okio - A modern I/O library for Android, Java, and Kotlin Multiplatform.
swift - The Swift Programming Language
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.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
kotlin-wrappers - Kotlin wrappers for popular JavaScript libraries
Vapor - 💧 A server-side Swift HTTP web framework.