Unwrap VS swift-corelibs-foundation

Happy too! So my main resource is Hacking With Swift (https://www.hackingwithswift.com), specifically the 100 days of SwiftUI Course. It takes you over Swift and SwiftUI. I've paired this with the official Swift site (https://www.swift.org) so I can dig into the language more, and Apple Documentation where appropriate to get used to using the tools.

In terms of finding it, it was a bit of a shot in the dark. I did some poking around and this popped up the most, specifically because I was looking for iOS specific materials. I'm sure if you want to make cross platform apps there's probably a whole host of great resources!

Thanks to Paul Hudson at Hacking With Swift, I recently learned that what I thought was a bug in SwiftUI is actually a feature. Paul says in one of his 100 Days of SwiftUI videos - which I highly highly recommend for anyone wanting to learn Swift and/or SwiftUI - even the most experienced iOS developers are often gobsmacked by this quirk of the code. I knew right away what he was talking about - I had encountered it myself, turned in a feedback report to Apple, and found a work-around. But according to Paul, it's not a bug, it's a feature! He encourages his viewers to spread the word, so that's what I'm doing.

The two I can think off of the top of my head are Paul Hudson's web site https://www.hackingwithswift.com and the old Ray Wenderlich site which is now called Kodeco https://www.kodeco.com/home.

Another good resource is Standford's CS193p - Developing Applications for iOS using SwiftUI which is online at https://cs193p.sites.stanford.edu.

Should be more than enough to get started.

Paul Hudson is pretty good at not forgetting the Mac: Hacking With Swift but TBH things are pretty similar, sometimes you need to replace UI... with NS... and import another framework but if you have something in mind to build for the Mac just start doing it, the rest will come.

Hacking with Swift website has a lot of resources (https://www.hackingwithswift.com

disclaimer: no channel, just an observer

Is YouTube the only medium you're considering?

For business, my understanding is that people now find success mainly though multi-channel and upgrade channels, so you would have some shorts/tic-toks, substack, instagram, twitter, ... (Which suggests some IDE support for the various artifacts being repurposed...) The goal seems to be to convert ~0.5% of the free folks to the $200 upsell: the batch of books, the online course (esp. if constantly updated). See e.g., Kat Norton, https://www.hackingwithswift.com, ...

While my personal preference runs to no-fluff-just-stuff, success seems to lie in motivating people with each step, with curiosity and enthusiasm, in part because that targets people who want to do X, but find themselves blocked (in part from frustration, loneliness, ...). It's probably a lot easier to unblock people who are just confused and frustrated, than to give focused people real insight. It may be more valuable as well, to lift all boats.

Anything Paul Hudson (https://www.hackingwithswift.com)

Hacking with Swift. is free and comprehensive.

Check out Hacking With Swift it’s what I used to get started

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