@siddharth3@drumRazor2813 It would be interesting to see how good these guys can play football. They have lot of attributes for it, but then again the massive size of pitch would be something that totally mess things up
@KevinVanCott No textboxes. Around 20 columns, 200 rows virtualized. Has some custom renderers nothing too fancy. The initial loading (with loader +data arriving) and in general performance is quite good. Only issue is when coming back to already loaded grid
@tannerlinsley@DuaneAdam I’m sure have usage analytics, but feels those who come into tanstack docs would prefer the explicit control (I’m confident mode) and not describe an idea, for that they’d go lovable or so
@tannerlinsley@DuaneAdam I think a good balance would be to have users still pick the tools via old ui, and run ai behind the scenes. Or could give a custom skill / doc that folks can give to their coding assistant
@zack_overflow Had bun team sent a tweet they are trying to porting to rust to get better at segfaults (again everyone knows its biggest problem) people would have been more sympathetic
@zack_overflow I think its because ts team announced they are porting to go, and all were wishing for it to improve in speed anyway.
Whereas for bun, it got leaked in hn, and Jarred defended saying its just mostly a throwaway trial and in a week got merged to main.
@jarredsumner@Shreyassanthu77@thdxr Actually before even the PR you could have put out a tweet we are exploring rust. The hn post found it first, and you had to defend its just nothing and then merging the PR in a week was not a great timeline