swift-corelibs-foundation VS Publish

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.

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

The (shitty) old Linux implementation has been on GitHub for years.

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.

CoreFoundation is (partially?) open-source and cross-platform now: https://github.com/apple/swift-corelibs-foundation

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...

Regarding your point #3, Swift does indeed have an open-source cross-platform implementation of Foundation. swift-corelibs-foundation

Foundation is open source and (mostly) works on Linux. What else do you want to see “opened up?”

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...

For Swift there’s https://github.com/JohnSundell/Publish which is a framework to create a static site generator. It’s really good.

- I use a static site generator written in Swift: https://github.com/johnsundell/publish (wouldn't recommend it though). - Vanilla CSS - Minimal JS (no frameworks needed)

First thing I thought of was John Sundell's Publish, then make all the articles as posts. A bit of HTML work and have it list it as a sidebar with an order metadata of the markdown. You could then use the LocalWebsitePublishPlugin to make it all accessible offline too - though I haven't tested it so I dont know if it works or not. There are not a lot, but some plugins available too that are helpful, and it's nice to be inside of the same language ecosystem.

There is a SSG that uses Swift: https://github.com/JohnSundell/Publish

I made https://will.institute/ as a place to post stuff after bailing on most social media, the existing content was migrated over from my old Instagram account.

Static site built in Swift with Publish: https://github.com/JohnSundell/Publish

Since I got out of the habit of posting anything on Instagram for a couple years I haven’t really gotten back into it for my own site, but one of these days I’ll put some new pictures up!

The best static site generator in Swift is Publish, but the Swift.org website is much older than that project.

Currently working on something similar, but in Swift, with Publish. Still a long way off since my css skills leave a lot to be desired, lol

If a static website works for you, you can use Publish library by John Sundell.

"There are dozens of us" but seriously, there is some interest from users but most projects done by companies have been abandoned, SwiftUI feels almost like a language divergence, which is frustrating. I'll list what I know about but it's by no means comprehensive.

The good news is that server side on Linux is still working well, Vapor 4 is solid, growing and looks like it has a bright future and Perfect is still going too, though Perfect seems disjointed from the main community. IBM's Kitura and involvement with Swift is over though. Server side seems like it's best future right now, since it's more performant than Javascript and uses less cycles, which can have a lot of cost benefits.

Static site generation looks good too, Publish by John Sundell being the most famous (https://github.com/JohnSundell/Publish) but a lot of others have started springing up lately.

"Swift for Tensorflow" by Google has been shut down. Though that was mostly Google giving advice on how to evolve Swift to work better for ML. It's a shame too, since it felt like Fast.Ai was adopting it and starting to teach it at one point, so the shutdown felt a bit premature, but this is Google after all, shutting things down is what they do.

Swift 5.0+ seems to have stabilized the language quite a bit too(ABI Stability and other things), which is a good thing, as hopefully the tutorials/docs from now on should remain more consistent. The built in package manager "Swift Package Manager" seems to be working better too, though there are still a lot of complaints/missing features, but on the whole I like it.

Swift on Linux seems to be officially supported by more flavors of Linux than it used to be. Meanwhile Swift on Windows works right now but I wouldn't use it in production yet, it throws errors that are the sort that if you ask anyone they will answer "that's normal, ignore that". Some have even gotten modern Swift to run on older MacOS's leveraging LLVM.

Swift WASM seems to have had a big update with Swift 5.4 https://forums.swift.org/t/swiftwasm-5-4-0-has-been-released... though I've not yet tried it having given up on Swift WASM about a year ago.

Youtuber Stega's Gate(https://www.youtube.com/channel/UCBXFkK2B4w9856wBJfCGufg) is building a cross platform game engine in swift.

IntelliJ has a decent alternative to Xcode now too, using Clion with an app made by them(though it's still not as integrated as Xcode, nothing would be).

Getting it to run on android is technically possible, but the workaround it too much, but that's mostly on Google actually, since the support for writing things in C for Android is so depreciated it's a joke.

The Docs are still terrible though, have been to my knowledge since 3.0 became outdated. That said the official books are alright and there are tutorial communities that are pretty good too, but it's shameful that the docs should be that useless.

So yeah, Swift is nearly viable for non Mac things, but there aren't much for libraries outside of backend. Some are tinkering and making cool stuff, but at times it's difficult when even the non app related programming tutorials for those are like "let's do it on MacOS using Xcode".All of that said, it's my favorite language, I want it to have a community similar to Rust's but I don't think Apple supports it the right way for that happen, they seem ok with it staying inside their ecosystem, like they are ok if the community does stuff outside of it, but they aren't helping it or encouraging it, is the general feeling. Ironically I was recommended to Swift initially because of the community that it had at the time, the caveat being "if you want to make apps for Apple's ecosystem", which isn't terrible, but it's not what I want. I'll probably give up on it if it doesn't change in the next year or so and go all in on Rust is likely what will happen, but again it's a shame.