6

Anyone ever tried Embedded Swift?

I should have posted this as a joke but, guess what Apple does NOT use when developing Embedded Swift stuff for their Secure Enclave firmware...

Yep, they don't use Xcode! 🤣🤣🤣🤣

(ok, I know, not surprising, but love the irony!)

Comments
  • 2
    No dogfooding at apple, I guess.
  • 1
    @spongessuck in one of the sessions they told that they use embedded swift for their own chips or something.

    Xcode doesn’t have templates for embedded swift, that’s probably why they use something else.

    Xcode is for gui apps and cli apps.
  • 2
    I only like common swift

    https://en.wikipedia.org/wiki/...
  • 1
    @Lensflare actually it technically (with plenty of thorns) does embedded. I'm adopting it to bare metal coding for a hardware project. It is no easy task and definitely shows the insanely buggy nature of Xcode... but it is in theory a generic IDE that executes against external tool chains.

    (what?! Xcodesucks sticking up for Xcode? Sign of the apocalypse; what's next? dogs and cats living together?)
  • 0
    @iiii Re: What's wrong with C and C++ to be using Swift of all things?

    My C conventions have carried through C++ and ObjectiveC. If I am going to convert them over to Swift, I would rather not try to maintain them in two very different languages, especially one that does not generally allow you to use pointers / hardware addresses
  • 0
    @kiki Re I only like common swift

    Have to agree, lovely.
  • 0
    @iiii I had ObjectiveC shoved down my throat but it was not really horrible... just pointless. C++ and multiple inheritance was so much more powerful but...

    So I would agree... different for the sake of being different is not better. A treatise of Apple engineering that they clearly do not observe.

    Next we delve into the folly of closures!
  • 0
    I agree that objc was a horrible abomination.

    It’s like the worst of C and Java combined and a syntax that is not only ugly but also annoying.
  • 0
    @Lensflare Re: ObjC abomination

    I did not find it quite so objectionable. I was forced into it for a project and while it felt like leaving a 6-speed sports coup w/ racing clutch to drive a 4-door Mercedes; it was at least a Mercedes I guess🤷🏻‍♂️.

    Apple did their best to restrict drifting (so to speak) but I found ways to mod my ride without risk of malfunction. I found I could have a very full personal library that crossed assembly, C, C++ and ObjectiveC. But with Swift, I am at the complete mercy of Apple, and all the hype, or so it seems.
  • 0
    @xcodesucks if you like, you can use objc as a bridge between C/C++ and Swift.

    > But with Swift, I am at the complete mercy of Apple

    I don’t really get this point. Swift is available for all major platforms/os.
Add Comment