Mᴀᴇꜱᴛʀᴏ (@thinkelastic) header
Mᴀᴇꜱᴛʀᴏ (@thinkelastic) profile picture

No great discovery was ever made without a bold guess.

Joined October 2011
Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)Photo by Mᴀᴇꜱᴛʀᴏ (@thinkelastic)
Mᴀᴇꜱᴛʀᴏ retweeted
#Analogizer WIP PS/2 Keyboard + SNES SNAC support, testing it using the OpenFPGA MSX core by @marcusjordan . I'm developing a customized SNAC PS/2 adapter to use it with Analogizer along Blue212 type of NES/SNES SNAC adapters as you see in the image.
5
27
1,021
Mᴀᴇꜱᴛʀᴏ retweeted
ScummVM thanks to @thinkelastic with #Analogizer support
3
15
781
Mᴀᴇꜱᴛʀᴏ retweeted
Relased Tracker MOD Player for Analogue Pocket & #Analogizer powered with openfpgaOS SDK. Thanks to @thinkelastic github.com/RndMnkIII/ModPlay…
4
18
1,059
Mᴀᴇꜱᴛʀᴏ retweeted
Creating a standalone MOD player for the Pocket & Analogizer, thanks to the openfpgaOS SDK by @thinkelastic
1
19
136
8,082
Mᴀᴇꜱᴛʀᴏ retweeted
Can the Analogue Pocket do raytracing? Check github.com/thinkelastic/open…
1
4
23
1,406
Mᴀᴇꜱᴛʀᴏ retweeted
Replying to @thinkelastic
@thinkelastic allows #Analogizer support on Pocket Doom core. Try a Coop Multiplayer Game?
2
2
15
790
Mᴀᴇꜱᴛʀᴏ retweeted
This is the most effective way to output your Analogue Pocket to your analogue display. The Analogizer 🔉🔊
1
3
14
2,515
Mᴀᴇꜱᴛʀᴏ retweeted
Replying to @PixelCNinja
What should we port next?
7
1
1
4
3,396
Mᴀᴇꜱᴛʀᴏ retweeted
#Analogizer WIP support for Pocket Quake:
11
66
3,565
Mᴀᴇꜱᴛʀᴏ retweeted
It's official! DOOM has gone from running on 36,853 devices to now support for 36,854 devices. The #AnaloguePocket release is courtesy of @thinkelastic
8
13
161
6,433
Mᴀᴇꜱᴛʀᴏ retweeted
Quake has been ported to the #AnaloguePocket courtesy of @thinkelastic 👍 ⚠️ IMPORTANT ⚠️ Check the pinned comment for additional information regarding required files for setting up. Have a Quaketastic day y'all: youtu.be/yJOgFFXE2mI?si=oQVj…
1
3
14
919
Mᴀᴇꜱᴛʀᴏ retweeted
Nice to see @thinkelastic's port getting more love 🤎
1
7
1,112
Mᴀᴇꜱᴛʀᴏ retweeted
I've actually been enjoying the last days of software development. There's a touch of sadness, but there's also something about knowing we're near the end that makes it novel and sweet again.
79
113
26
1,847
181,815
Mᴀᴇꜱᴛʀᴏ retweeted
Zuck Jensen TPU/GPU Game theory convo ZUCK: “Google is giving me early TPU v7/v8. I’m moving big Llama runs there. I want B200 pricing to reflect that.” JENSEN: “Then take the TPUs. If you believe they’ll hit schedule, go all-in.” ZUCK: “I’m serious. I can cut my NVIDIA footprint by a third.” JENSEN: “Good. That frees up CoWoS for customers who want guaranteed delivery. Your allocation drops starting next quarter.” ZUCK: “…Wait. We still need a baseline of H100/B200 for the mainline models.” JENSEN: “And you’ll get some allocation. But not priority. You split your demand — someone else gets the front of the line.” ZUCK: “Jensen, TPU v7/v8 will close the gap. We’ll be fine.” JENSEN: “That’s what Anthropic said before their compiler delays. That’s what OpenAI said before they came back for more H100s. Everyone thinks they can dual-stack. Few can.” ZUCK: “We have the engineering talent.” JENSEN: “You don’t have the calendar. Training windows slip. Debug cycles multiply. And Google will always give Gemini first rights on peak TPU capacity. You’re betting your entire roadmap on your biggest competitor’s generosity.” ZUCK: “We’ll make it work.” JENSEN: “Maybe. But you just ceded two quarters of training speed to labs staying unified on CUDA. They’ll ship next-gen models before you finish porting.” ZUCK: “…We still want 40k B200s.” JENSEN: “They’re sold out. You’re welcome to join the waitlist.” Zuck realizes too late: He played the TPU card too hard. Jensen didn’t blink. Meta is stuck with half their training fleet on an ecosystem still maturing, and their NVIDIA allocation halved. And the labs staying pure CUDA now sprint ahead.
231
334
82
3,670
1,202,407
Mᴀᴇꜱᴛʀᴏ retweeted
This is an awesome DGX use case! Well done! Could we transfer the KV cache directly to Studio SSD via DMA, queuing requests to load when ready for processing? This would pair beautifully with batching for optimal throughput.
Clustering NVIDIA DGX Spark + M3 Ultra Mac Studio for 4x faster LLM inference. DGX Spark: 128GB @ 273GB/s, 100 TFLOPS (fp16), $3,999 M3 Ultra: 256GB @ 819GB/s, 26 TFLOPS (fp16), $5,599 The DGX Spark has 3x less memory bandwidth than the M3 Ultra but 4x more FLOPS. By running compute-bound prefill on the DGX Spark, memory-bound decode on the M3 Ultra, and streaming the KV cache over 10GbE, we are able to get the best of both hardware with massive speedups. Short explanation in this thread & link to full blog post below.
2
1
120
Mᴀᴇꜱᴛʀᴏ retweeted
DGX Spark's strength is batching, not single requests—despite its 'personal' branding. Compare its performance in parallel dev workflows vs. batch=1 chats.
1
1
45
Mᴀᴇꜱᴛʀᴏ retweeted
In the 1980 movie "Airplane", Barbara Billingsley was handed a script that told her to speak jive. Not knowing how to speak it, she went to lunch with the two black actors in the scene (Al White and Norman Alexander) to learn jive. The three of them improvised the whole scene.
146
785
75
10,228
2,479,930
Mᴀᴇꜱᴛʀᴏ retweeted
.@ElasticBox introduces a new open source project #ElasticKube to help manage #Kubernetes within the enterprise blog.kubernetes.io/2016/03/e…
20
31
28-I te invitamos a la openclass online con @oscar_sanjuan_m ow.ly/WTN5q cc @ElasticBox #CloudComputing
2
1