| Transmission Radio | https://apps.apple.com/app/apple-store/id1633197545?pt=2322962&ct=Mastodon&mt=8 |
| PDF Library | https://apps.apple.com/app/apple-store/id6503659712 |
| Transmission Radio | https://apps.apple.com/app/apple-store/id1633197545?pt=2322962&ct=Mastodon&mt=8 |
| PDF Library | https://apps.apple.com/app/apple-store/id6503659712 |
I suspect it won’t be long before all compiled software (apps) can be decompiled into readable source code.
There’s a large corpus of training data (open source) and there’s a tight verification loop (compile a guess at what the source is and see if it matches).
LLMs will figure out how to decompile small functions, and will gradually learn how to decompile more complex stuff.
I think within 2 years, all iOS apps will effectively be open source.
An analysis of Terry Pratchett's novels finds that a decrease in lexical diversity--a characteristic of dementia--first appeared ten years before his diagnosis of posterior cortical atrophy.
Original paper: https://www.mdpi.com/2076-3425/16/1/94
@helge I think a major problem with SwiftUI is it is a single high level black box.
It doesn't expose any lower layers or building blocks.
In UIKit you can drop down to CoreAnimation. UIButton subclasses UIControl, which subclasses UIView, etc...
There are layers, buttons not working for you? Subclass UIControl.
UIView doesn't expose what you need. CALayer (can even swap the CALayer a view subclass uses).
SwiftUI is more "you get what we give you", "Need more? tough".