For clarity, this is not https://www.foundationdb.org/ Which Apple acquired years ago and then released it open source.
Ah, so Deno KV is using an open source database? I didn't realize that.
Apple is rewriting Foundation in Swift
21–30 of 263 posts
Re: Apple is rewriting Foundation in Swift
#22What a dumpster fire Swift turned out to be. My first experience with it saw compile times go up more than 10x from the previous objc code base. Everytime more and more of apple's libraries were replaced because all the objc stuff was considered obsolete the compile times got worst and worst.
Its not like I dislike the language either but I think compile times matter so languages should not pretend like that doesn't exist. I can forgive Rust its giving you more than just type checking but Swift does not offer the same things yet it takes just as long or longer to compile.
Re: Apple is rewriting Foundation in Swift
#23Long overdue -- there's a very noticeable difference in runtime errors with Swift libraries vs the rest. This is especially true of AVFoundation, which is an absolute mess of hidden and undocumented state. Swift optionals and enums will go a long way to fixing that.
This will not directly affect AVFoundation, or any other framework which is not Foundation itself.
Re: Apple is rewriting Foundation in Swift
#24Well, this is one more step toward a fully Swift-only platform. Very soon it will not be possible to publish an app on iOS not built with the house language. For those who don’t know, using C/C++ and opengl was easily done on iOS for many years, as llvm/clang was the official compiler.
Bad take.
Swift heavily relies on LLVM. As long as you have LLVM IR, your support isn’t going anywhere. Not to mention Apple continues to be an outsized contributor to LLVM and clang (largely because they started and open sourced the projects)
Re: Apple is rewriting Foundation in Swift
#25What a dumpster fire Swift turned out to be. My first experience with it saw compile times go up more than 10x from the previous objc code base. Everytime more and more of apple's libraries were replaced because all the objc stuff was considered obsolete the compile times got worst and worst. Its not like I dislike the language either but I think compile times matter so languages should not pretend like that doesn't…
They both compile slowly because they have similarly complicated type systems. What do you use in Rust that Swift doesn’t yet provide?
Re: Apple is rewriting Foundation in Swift
#26Well, this is one more step toward a fully Swift-only platform. Very soon it will not be possible to publish an app on iOS not built with the house language. For those who don’t know, using C/C++ and opengl was easily done on iOS for many years, as llvm/clang was the official compiler.
You're going to be relieved when you find out Swift has been using LLVM this entire time.
We’ll see.
I have a bad feeling about this.
Re: Apple is rewriting Foundation in Swift
#27What a dumpster fire Swift turned out to be. My first experience with it saw compile times go up more than 10x from the previous objc code base. Everytime more and more of apple's libraries were replaced because all the objc stuff was considered obsolete the compile times got worst and worst. Its not like I dislike the language either but I think compile times matter so languages should not pretend like that doesn't…
They both compile slowly because they have similarly complicated type systems. What do you use in Rust that Swift doesn’t yet provide?
Catch data races at compile time?
Re: Apple is rewriting Foundation in Swift
#28Re: Apple is rewriting Foundation in Swift
#29[flagged]
What a weird usage of that word…
Re: Apple is rewriting Foundation in Swift
#30What a dumpster fire Swift turned out to be. My first experience with it saw compile times go up more than 10x from the previous objc code base. Everytime more and more of apple's libraries were replaced because all the objc stuff was considered obsolete the compile times got worst and worst. Its not like I dislike the language either but I think compile times matter so languages should not pretend like that doesn't…
They both compile slowly because they have similarly complicated type systems. What do you use in Rust that Swift doesn’t yet provide?
There are a very large list of foundational capabilities so that it’s not practical to respond with a concise answer. One example is automatically closing resources on behalf of the caller thanks to lifetimes. Another example is the best compiler feedback of any mainstream language.