This will literally never happen. Ping me in five years and tell me I was wrong. (via https://stefan-lesser.com/2018/06/20/on-apples-love-affair-with-swift/ …)pic.twitter.com/mdqKwMJDae
-
The problem is that any solid language should give 'me' full control if I need it. I want this mem allocated here and released there and I want it exactly like I said. Any compiler that can't do this or use 'tricks' can go to trash when trying to make highly optimised code.
Right. The less control you have over allocation and the less idiomatically you can write data-oriented code, the more of a pain a language becomes. Conversely, most people writing apps don't care about the cost of per-object heap allocation; they just want the convenience of OOP
-
-
Is Swift using ARC for memory management or a "proper" GC? I found ARC surprisingly expensive with Obj-C, and the required hand-holding to get the ARC overhead down to an acceptable level is IMHO more hairy than the old manual memory management...
-
Swift uses ARC (https://docs.swift.org/swift-book/LanguageGuide/AutomaticReferenceCounting.htm …), and AFAIK it’s not possible to opt out.
End of conversation
New conversation -
-
-
And the last nail in the coffin :) Any, I repeat any language for game development should be very easily mixed with C++. ObjC does this brilliantly.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.