4 ms·
I don't want to be negative about this article, but reading over it left me with a little bit of disappointment. I was hoping for an in depth dive into how Swi
by ivl 7y ago
I don't want to be negative about this article, but reading over it left me with a little bit of disappointment.
I was hoping for an in depth dive into how Swift performed on a RPi compared to other languages (say, C relative to Swift on x86, then the same for ARM), and a little on how well Swift interacts with the Pi's hardware. But it was just a quick guide on setting up a Pi, installing Swift, and making a quick 'Hello, World' program. The only lines of interest came at the very end:
> Now that Swift is installed, there’s so much more that you can do. To control hardware — like LEDs, motors, and relays — you can use the help of a library for hardware projects on Linux/ARM boards called SwiftyGPIO. Have fun experimenting with Swift on the Raspberry Pi!
That said, SwiftyGPIO looks like a fun little library that I think I'm going to look into more and play around with.
- elpakal 7y ago"In-depth" wasn't mentioned anywhere in the title though. The author also defines hardware vs software... Clearly an introduction, and props to him for trying.