@g0ld2k.bsky.social
Reposted
My SwiftUI wishlist:
1. Truly performant lists and collections.
2. Faster compile times and sensible syntax errors.
3. Ability to control precise behavior of TextFields, focus, and NavigationLinks.
4. An imperative handle API (a la React refs).
5. Xcode previews that actually work.
1. Truly performant lists and collections.
2. Faster compile times and sensible syntax errors.
3. Ability to control precise behavior of TextFields, focus, and NavigationLinks.
4. An imperative handle API (a la React refs).
5. Xcode previews that actually work.
March 12, 2025 at 9:09 PM
My SwiftUI wishlist:
1. Truly performant lists and collections.
2. Faster compile times and sensible syntax errors.
3. Ability to control precise behavior of TextFields, focus, and NavigationLinks.
4. An imperative handle API (a la React refs).
5. Xcode previews that actually work.
1. Truly performant lists and collections.
2. Faster compile times and sensible syntax errors.
3. Ability to control precise behavior of TextFields, focus, and NavigationLinks.
4. An imperative handle API (a la React refs).
5. Xcode previews that actually work.
Reposted
As software developers, we shouldn't treat AI tools much differently than Stack Overflow.
Much like Stack Overflow answers, AI-generated code should be evaluated based on parameters like performance, security, and maintainability.
Much like Stack Overflow answers, AI-generated code should be evaluated based on parameters like performance, security, and maintainability.
January 5, 2025 at 11:42 PM
As software developers, we shouldn't treat AI tools much differently than Stack Overflow.
Much like Stack Overflow answers, AI-generated code should be evaluated based on parameters like performance, security, and maintainability.
Much like Stack Overflow answers, AI-generated code should be evaluated based on parameters like performance, security, and maintainability.