Explore >> Select a destination
|
You are here 
|
pewpewthespells.com | ||
| | | | |
haim.dev
|
|
| | | | | A guide to statically linking Swift library into a Rust application. | |
| | | | |
www.jessesquires.com
|
|
| | | | | On macOS 14 Sonoma there is a regression in Swift 5.9 which causes Swift scripts that import Cocoa frameworks to fail. This issue was first reported by @rdj.... | |
| | | | |
nickcharlton.net
|
|
| | | | | There's a couple of (client) projects which I maintain which have been in existence for quite a while (one still has full iOS 5 support and hopefully we'll be able to drop that soon), but they're still well maintained and have reasonable test suites that have followed them through rather well. Sadly, Xcode can be a bit difficult and this time was no exception - although it did take a long time before the issue was seen. | |
| | | | |
fzakaria.com
|
|
| | | Bazel is a pretty amazing tool but it's definitely full of it's warts, sharp edges and arcane knowledge. The appeal to most who adopt Bazel is the ability to memoize much of the build graph if nothing has changed. Furthermore, while leveraging remote caches, build results can be shared across machines making memoization even more effective. This was a pretty compelling reason to adopt Bazel but pretty soon many noticed, especially on their CI systems, lots of unecessary data transfers for larger codebases. ?? If the network is poor, the benefits of remote caching (memoization) can be outweighed by the cost to download the artifacts. | ||
