hutaffe
hutaffe

There was a big fuzz about Apple blogging on their Swift Blog at the time. Anyone noticed that there was no new post since October 2016? 🤔

|
Embed
dgold
dgold

@hutaffe The treatment of Swift, particularly on Mac as opposed to iOS, is puzzling to me. There is almost no up-to-date documentation on implementing Swift for Macs.

|
Embed
hutaffe
hutaffe

@dgold The API docs are mostly fine for my needs, but samples and more advanced stuff is hard to find, that's true. It's yet another symptom of the neglect of macOS in the last couple of years.

|
Embed
hutaffe
hutaffe

@dgold I got back into programming for the Mac last year after a few years on iOS only. If it were my first time and I wanted to do everything in Swift, I would have been lost... No chance to get going!

|
Embed
In reply to
dgold
dgold

@hutaffe that's it exactly (for me). I didn't even want to do something overly complex. I spent a week becoming increasingly frustrated in Swift; I accomplished a similar early prototype result using nodejs/electron in an hour.

|
Embed
hutaffe
hutaffe

@dgold yeah. I don't understand people telling me how easy and accessible Swift programming is. I think it's really really hard to learn and not far off from the complexity of C++. And then there are the frameworks that are not made for Swift plus the language (in parts fundamentally) chaning all the time. Once you got the hang of it, it's fun to use... but the learning curve is exremely hard.

|
Embed
cleverdevil
cleverdevil

@dgold I love native apps on macOS, but the friction you experienced with Swift is precisely why so many people turn to Electron. Hopefully, WWDC this year has some answers!

|
Embed
cleverdevil
cleverdevil

@dgold I love native apps on macOS, but the friction you experienced with Swift is precisely why so many people turn to Electron. Hopefully, WWDC this year has some answers!

|
Embed