5 ms·

The amount of compiler magic used by SwiftUI is staggering. By itself it's not a deal breaker, but closed source makes it almost impossible to understand what i

by krzat 6y ago

The amount of compiler magic used by SwiftUI is staggering. By itself it's not a deal breaker, but closed source makes it almost impossible to understand what is going on.

deleted 6y ago
[deleted]
trollied 6y ago
The compiler https://swift.org/swift-compiler/ https://swift.org/swift-compiler/ is open source? https://github.com/apple/swift https://github.com/apple/swift Or have I misunderstood your comment?
- djxfade 6y ago
  Swift the language and its compiler is open source yes. However, the SwiftUI framework is not.
MattDamonSpace 6y ago
Weren’t UIKit and AppKit before that closed source?
- krzat 6y ago
  It did not use any compiler magic, and ObjC classes are very hackable.
- djxfade 6y ago
  They still are, and so are SwiftUI
skohan 6y ago
This is one of the main reasons I have migrated to Rust for most new projects to be honest. I've been a big fan of Swift for years in terms of the balance it strikes between expressiveness and safety/correctness. But the way that function builders and property wrappers were somewhat hamfistedly jammed into the language to support SwiftUI has been a big turnoff. Previous iterations seemed like they had a very clear intentionality and priority around preserving the clarity of the language, but I'm less confident about the direction the language is currently taking in that respect. Also the relative fragility of large swift projects with multiple dependencies has been a recurring frustration. It's been refreshing to work with Cargo, and not have to worry about doing surgery on a project every time a language update is released.
yoz-y 6y ago
AFAIU all the magic used by SwiftUI is included in the open source compiler. AKA one should be able to reimplement SwiftUI on top of the OSS Swift language. Granted though, these features are not developed in the open.

5 ms·

The amount of compiler magic used by SwiftUI is staggering. By itself it's not a deal breaker, but closed source makes it almost impossible to understand what i

by krzat 6y ago

The amount of compiler magic used by SwiftUI is staggering. By itself it's not a deal breaker, but closed source makes it almost impossible to understand what is going on.

deleted 6y ago
[deleted]
trollied 6y ago
The compiler https://swift.org/swift-compiler/ https://swift.org/swift-compiler/ is open source? https://github.com/apple/swift https://github.com/apple/swift Or have I misunderstood your comment?
- djxfade 6y ago
  Swift the language and its compiler is open source yes. However, the SwiftUI framework is not.
MattDamonSpace 6y ago
Weren’t UIKit and AppKit before that closed source?
- krzat 6y ago
  It did not use any compiler magic, and ObjC classes are very hackable.
- djxfade 6y ago
  They still are, and so are SwiftUI
skohan 6y ago
This is one of the main reasons I have migrated to Rust for most new projects to be honest. I've been a big fan of Swift for years in terms of the balance it strikes between expressiveness and safety/correctness. But the way that function builders and property wrappers were somewhat hamfistedly jammed into the language to support SwiftUI has been a big turnoff. Previous iterations seemed like they had a very clear intentionality and priority around preserving the clarity of the language, but I'm less confident about the direction the language is currently taking in that respect. Also the relative fragility of large swift projects with multiple dependencies has been a recurring frustration. It's been refreshing to work with Cargo, and not have to worry about doing surgery on a project every time a language update is released.
yoz-y 6y ago
AFAIU all the magic used by SwiftUI is included in the open source compiler. AKA one should be able to reimplement SwiftUI on top of the OSS Swift language. Granted though, these features are not developed in the open.