@boundless_xyz @sshankar when you have the biggest decentralized GPU market in the world, supporting AI workloads is a no-brainer
English
Nahoc
1.2K posts
Nahoc
@_nahoc
Staff Software Engineer @boundless_xyz — Previously @avalabs — Former beekeeper — SM64 TASer
Canada Katılım Ağustos 2012
1.1K Takip Edilen729 Takipçiler
Nahoc retweetledi
How I look at my wife when she says we havin ribs for dinner
Shiv Shankar@sshankar
The thing you set out to build is rarely the most valuable thing you end up with. Something Bigger is coming with @boundless_xyz.
English
Nahoc retweetledi
The thing you set out to build is rarely the most valuable thing you end up with.
Something Bigger is coming with @boundless_xyz.
English
@_nahoc I can get this in 1-2 tries on ch, this took me well over half an hour of attempts
At 60fps on GH3 Xbox you have to really think about how you’re gonna hit a fast section like this.
At 2000 fps on CH you have way more opportunities to mess up/hit notes late/fuck up
English
Nahoc retweetledi
less packed than quebec costco on Tuesday 2pm
Brent Scher@BrentScher
Hilariously hot outside — my car said 104 when I parked — and the mall is packed. Biggest line is for Florida, where they’re giving out stuffed gators and manatees and have a putting green.
English
Acting like 2006 was 20 years ago lmao
𝓸𝓶𝓰 𝓲𝓽𝓼 𝓓𝓻𝓪𝓴𝓸 ♕ ★🧝🏽♂️@DrakoAfoa
The recording quality of the 2006 camera’s gave the first season of Dexter it’s unique touch.
English
The blog post is out! Here's the surprisingly simple way that TanStack Table V9 can use a little as 10% memory as it used to.
Hint: it takes advantage of Object prototypes
tanstack.com/blog/tanstack-…
Kevin Thomas Van Cott@KevinVanCott
Up to 90% less memory usage? I'm working on a new blogpost to examine the performance improvements of TanStack Table V9 and first up is memory usage. I just created some memory usage benchmarks for TanStack Table V9 vs V8, and it verifies that Table V9 may use up to 90% less memory than V8 on our example with 100k+ virtualized rows. This is kind of a best-case scenario, so I'll need to benchmark even more common table setups in order to be as transparent as possible. This improvement is due in large part to our refactor where we store object functions on a single prototype instead of creating them for every object. APIs like row.getVisibleCells, column.toggleSorting(), etc... now all defined just once on `table._rowPrototype`, `table._columnPrototype`, etc. When I first attempted this refactor, I was worried that it might be a waste of time for an improvement that could be negligible. For common smaller tables, it still kind of is, but for large, virtualized tables where the number of objects created scales linearly with memory usage, it's seeming to make all the difference.
English
