This is what the future looks like

programming is fun

This GitHub feature strikes me as odd. Generated files are important to review!

@JohnPhamous signed up just to see the fog not even buying compute

@RhysSullivan hmm. what if we preserved JSDoc comments in generated .d.ts files? that'd be a great thing to feed into llms.

@Vlad_Smolyanoy @SebJVidal some things are fundamentally difficult to do in a component architecture and easy to do in view controller architecture esp. w.r.t. performance. UIKit is a powerful toolbox.

@hyprturing Boba Guys

@mitchellh True, but why wouldn't you run `brew update && brew upgrade` once a week?

@wunderacle @nodejs oh okay, I guess then just the majors with relevant info is good. and perhaps a link somewhere with "see all versions".

@justalexoki mac doesn't have insert key.

@jarredsumner add openai compatible sdk and bun becomes the ultimate b2b saas runtime

@zack_overflow where does C++ constexpr fits in

@benln Nikita Bier is the Michael Jordan of building viral teen apps

@jordwalke Shrinky header means layout runs on every scroll event. If layout is heavy, frames will drop, no matter if native driver is used or not. Tbh shrinky header would skip frames even in UIKit/SwiftUI, I haven’t seen it implemented in a way where it doesn’t.

@jordwalke react-native-reanimated with react-native-gesture-handler, but yeah, that does skip frames

@jordwalke in RN, there's typically no need to bind to scroll events, so you'd be running scroll views fully managed by iOS in majority of cases. In Flutter, everything goes through 'rendering engine' (Impeller in new versions). Which is sort of like Canvas API on Web. That's limiting.

@jordwalke That sounds correct, but is a difficult requirement to meet in Flutter's architecture. I believe in React Native it would just be a native list where scrolling and rendering is managed by iOS directly on the UI thread (unless overridden).

@jordwalke

@ghoshal @nikitabier wow