Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Posts
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
Software stuff. Mostly a loser ranting about everything shit in the (tech) world.
My biggest annoyance with SwiftUI has to be that so many modifiers are for a View, but there’s so many cases where they don’t work. Like .refreshable. It seems to only work on List. It does not work on Chart or VStack. If a modifier does not work on a certain view where it is perfectly legal I want to have it documented and see a warning when running in Xcode. This isn’t rocket science. Having code randomly do nothing without any warnings is extremely bad design.