> The real issue with CSS is the eternal question of, do I fill my parent or expand to fit children?
This is one of the real issues of GUI tools in general, not just CSS. You run into the same complexity on e.g. UIKit/SwiftUI (Apple) or any other toolkit that tackles the full complexity of defining UI layouts for any screen simultaneously.
Agree that CSS has a bit of extra cruft due to it’s evolution which makes it more difficult to learn and slower to work in than it perhaps could be if the web standards process allowed pruning features more easily
- A giant board on Miro.com with a bunch of notes in frames
Of course the scaling needs are different whether it’s for just a single team or if the data needs to be aggregated into some KPI. In my experience it’s better to keep KPI publishing separate from task tracking, though
Could you add the date of publication to the top of the page on each blog post? (Or year+month.) Looks like they’re there in the blog list, but not on the individual posts?
Would help understand the context on posts that describe tech that has evolved rapidly and probably still will
Wall clock speed does not correlate linear to power consumption (in the general case). To oversimplify, consider decoding singlethreaded on one core versus multithreaded on 8 or 20 cores.
In some special cases multiplying runtime might be enough to achieve some accuracy, but that’s not the whole story.
It would be interesting to see this experiment done so that the decode is done enough times for each format so the power consumption differences could actually be measured on a power/watt meter.
Where did the author use wall clock as a proxy for power consumption? The only time based thing I saw was power usage over time and that is still measuring power usage directly just explaining when in the process the most power was used.
Wow thanks! I didn’t see it when I checked, but needed to scroll down a bit. One of the idiosyncrasies of the App Store not prioritizing exact text matches.
Got working SwiftUI previews on a 50-100k LOC project with many big libs as dependencies, must be hundreds of files but havent counted. SwiftUI code is gaining share of the total UI code, probably around 20-30% now
Mock data is a must.
Need to be mindful of the preview build (+ preview simulator startup) time too, sometimes it will timeout but just building again (now warmer) will make it work
Had some initial issues around processor arch (Intel vs M1/arm), think I’m still running XCode under rosetta otherwise it wouldnt work.
one other solution is to build a sub project that links to a subset of minimum dependencies needed for ui development and build your swiftui stuff there...
it will be lightning fast compared to large xcode project... and it might even be better architecturally too, since you'd have to factor out lower level logic (view models or whatever) anyways
Like sibling comment mentioned, Fusion. Was using it to deliver advertising video VFX work on the daily for a couple of years, it's great. We were a mixed group of After Effects and Fusion (and many more apps) users and I would say generally you can accomplish the same things with both and some tasks are easier in one or the other.
I would recommend downloading the standalone Fusion Studio though, it's included with a Resolve Studio license (~$300 one-time). Managing anything but the simplest project within Resolve's Fusion page seems like a nightmare. Being able to use a separate app that saves its own files is a much more straightforward workflow. Then check out VFX Connect if looking for more sync between the apps.
