Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Mario Kart 64, running natively on iOS and iPad, with touch controls designed for racing. The Mario Kart 64 decompilation community spent years reconstructing the original game code in C. Harbour Masters turned that into SpaghettiKart, the source port. I built the iOS layer on top. Not an emulator....

chrissotraidis's profile picture

Kahris

1,060 subscribers

51,041 görüntüleme • 3 gün önce •via X (Twitter)

SanatBilim & TeknolojiOyun
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Star Fox 64, running natively on iPhone and iPad. Native ARM64 app. Metal rendering. 2x internal resolution and MSAA in settings. Touch controls. Controller support. Running on real hardware. Not an emulator, and not streaming from a Mac. HarbourMasters built Starship, the native source port. I built StarshipPad on top: the iOS/iPadOS layer, Files import, on-device setup, and mobile lifecycle. The surprise is iPhone: it doesn’t feel like a compromise. It feels like a real way to play. I used Codex 5.6 Sol to do the iOS integration work. Source, build guide, and ROM-free IPA below.
0:56

Star Fox 64, running natively on iPhone and iPad. Native ARM64 app. Metal rendering. 2x internal resolution and MSAA in settings. Touch controls. Controller support. Running on real hardware. Not an emulator, and not streaming from a Mac. HarbourMasters built Starship, the native source port. I built StarshipPad on top: the iOS/iPadOS layer, Files import, on-device setup, and mobile lifecycle. The surprise is iPhone: it doesn’t feel like a compromise. It feels like a real way to play. I used Codex 5.6 Sol to do the iOS integration work. Source, build guide, and ROM-free IPA below.

Kahris

25,681 görüntüleme • 2 gün önce

Ocarina of Time, running natively on iOS and iPadOS for the first time. Not an emulator. Ship of Harkinian has run on Windows, Linux, macOS, Switch, Wii U, and Android. Never iOS. Now it runs on iPad, with iPhone in the build too. The game was decompiled to C and rebuilt as a native ARM64 app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. It isn't stuck at the N64's 240p and 20fps. Widescreen, full resolution, 60fps. This game deserves a controller, so controller support is native. Pair a Bluetooth controller and play the whole thing. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build the iOS layer. Open sourcing it all below.
0:30

Ocarina of Time, running natively on iOS and iPadOS for the first time. Not an emulator. Ship of Harkinian has run on Windows, Linux, macOS, Switch, Wii U, and Android. Never iOS. Now it runs on iPad, with iPhone in the build too. The game was decompiled to C and rebuilt as a native ARM64 app rendering through Metal. No N64 hardware being simulated, no ROM interpreted at runtime, no streaming from a Mac. It isn't stuck at the N64's 240p and 20fps. Widescreen, full resolution, 60fps. This game deserves a controller, so controller support is native. Pair a Bluetooth controller and play the whole thing. Touch, keyboard, and mouse work too. I used Codex 5.6 Sol to build the iOS layer. Open sourcing it all below.

Kahris

1,155,544 görüntüleme • 5 gün önce

I used Codex 5.6 Sol to make the original Diablo actually playable by touch on iPad. Diablo was always point-and-click. Now your finger is the mouse. Tap gold on the floor and your character walks over and grabs it. It's built on DevilutionX, the open-source Diablo engine a group of contributors has maintained for years. It already ran on iOS, with a virtual gamepad. What didn't exist was a version built around the touchscreen itself. Open sourcing it all below.
0:51

I used Codex 5.6 Sol to make the original Diablo actually playable by touch on iPad. Diablo was always point-and-click. Now your finger is the mouse. Tap gold on the floor and your character walks over and grabs it. It's built on DevilutionX, the open-source Diablo engine a group of contributors has maintained for years. It already ran on iOS, with a virtual gamepad. What didn't exist was a version built around the touchscreen itself. Open sourcing it all below.

Kahris

145,520 görüntüleme • 13 gün önce

I used Fable 5 to port Command & Conquer: Generals Zero Hour to the iPhone and iPad! This is the actual 2003 engine compiled for ARM64 natively, no emulator. Campaign, skirmish, Generals Challenge all work with touch controls built for an RTS. Open sourcing it all below!
0:54

I used Fable 5 to port Command & Conquer: Generals Zero Hour to the iPhone and iPad! This is the actual 2003 engine compiled for ARM64 natively, no emulator. Campaign, skirmish, Generals Challenge all work with touch controls built for an RTS. Open sourcing it all below!

Ammaar Reshi

2,001,632 görüntüleme • 28 gün önce

I used Codex 5.6 Sol to build real touch controls for Fallout 2 on iPad. Fallout 2 was the one people kept asking for after RCT2. It's built on Fallout 2 Community Edition, the engine alexbatalov and a lot of contributors have poured years into. CE already runs on iOS, but you move a cursor around like a trackpad. VaultPad drops the cursor. Tap the ground to walk. Tap a door to open it. Tap an enemy to shoot. Combat puts your attack and its AP cost right on screen. Played an hour of it on the couch last night. Source is up below.
0:46

I used Codex 5.6 Sol to build real touch controls for Fallout 2 on iPad. Fallout 2 was the one people kept asking for after RCT2. It's built on Fallout 2 Community Edition, the engine alexbatalov and a lot of contributors have poured years into. CE already runs on iOS, but you move a cursor around like a trackpad. VaultPad drops the cursor. Tap the ground to walk. Tap a door to open it. Tap an enemy to shoot. Combat puts your attack and its AP cost right on screen. Played an hour of it on the couch last night. Source is up below.

Kahris

23,096 görüntüleme • 9 gün önce

CLAUDE TOOK A FULL PC GAME, REBUILT IT FROM THE GROUND UP, AND GOT IT RUNNING NATIVELY ON ANDROID IN 6 HOURS a guy pointed claude at slay the spire 2, a game he owns on steam, and it ported the whole thing to his phone almost completely on its own here's what claude did: > it pulled apart the game and recompiled it to native arm, no emulator, wine, or proton used > wrote the code, ran the build loop, and debugged it directly on the device itself > added full touch controls that feel like a real mobile game, not awkward on screen buttons > and he even built a tool on top to sync save files between his desktop and phone a couple prompts and 6 hours. it handled the extraction, the cross compile, the building and the on device debugging by itself. fully playable, not a single crash yet
0:39

CLAUDE TOOK A FULL PC GAME, REBUILT IT FROM THE GROUND UP, AND GOT IT RUNNING NATIVELY ON ANDROID IN 6 HOURS a guy pointed claude at slay the spire 2, a game he owns on steam, and it ported the whole thing to his phone almost completely on its own here's what claude did: > it pulled apart the game and recompiled it to native arm, no emulator, wine, or proton used > wrote the code, ran the build loop, and debugged it directly on the device itself > added full touch controls that feel like a real mobile game, not awkward on screen buttons > and he even built a tool on top to sync save files between his desktop and phone a couple prompts and 6 hours. it handled the extraction, the cross compile, the building and the on device debugging by itself. fully playable, not a single crash yet

Om Patel

28,504 görüntüleme • 1 ay önce

made a twrp-themed iphone recovery lol, this is not actual twrp, its for ios, running on xnu, but it is running in a ramdisk without a dsc, so I had to manually bringup the touch controller, and init other hardware, for this to work. What should I add to this?
1:00

made a twrp-themed iphone recovery lol, this is not actual twrp, its for ios, running on xnu, but it is running in a ramdisk without a dsc, so I had to manually bringup the touch controller, and init other hardware, for this to work. What should I add to this?

Mineek

29,524 görüntüleme • 8 gün önce

Today i'm Open Sourcing "Rilable" The iOS app that builds Web apps and iOS Apps. I built it with Fable 5 in 10 prompts. (~ $210 in tokens on API pricing) All apps are built with Claude Models, and every app spins up a sandbox (Exactly like Lovable) using Daytona. Database is Convex. The app allows you to build apps that have AI features for this it uses Vercel AI gateway, and iOS apps are using Chorus.com iOS skill (All links below)
0:35

Today i'm Open Sourcing "Rilable" The iOS app that builds Web apps and iOS Apps. I built it with Fable 5 in 10 prompts. (~ $210 in tokens on API pricing) All apps are built with Claude Models, and every app spins up a sandbox (Exactly like Lovable) using Daytona. Database is Convex. The app allows you to build apps that have AI features for this it uses Vercel AI gateway, and iOS apps are using Chorus.com iOS skill (All links below)

Riley Brown

71,826 görüntüleme • 1 ay önce

Originally released in 1989 on the Apple II, this is a port of Prince of Persia running natively on Flipper Zero Check out the source code here: Download it from Flipper Apps here: It's the full one-hour game, with a remade soundtrack and custom controls just for Flipper Big thanks to: A Touch of Vintage Electronics and Ashton’s Retro Computer Room for the intro footage The Press Play On Tape crew for development of the game apfxtech for the Flipper Zero port ...and to Jordan Mechner for creating the OG game 🐐
0:55

Originally released in 1989 on the Apple II, this is a port of Prince of Persia running natively on Flipper Zero Check out the source code here: Download it from Flipper Apps here: It's the full one-hour game, with a remade soundtrack and custom controls just for Flipper Big thanks to: A Touch of Vintage Electronics and Ashton’s Retro Computer Room for the intro footage The Press Play On Tape crew for development of the game apfxtech for the Flipper Zero port ...and to Jordan Mechner for creating the OG game 🐐

Flipper Devices

33,507 görüntüleme • 4 ay önce

Tesla wouldn't bring Cybertruck to India, so I built my own 😬 (a micro one) Used ESP32 as the controller, designed 3d printed tyres, chassis, shell, and added micro coreless motors that are otherwise used in small drones. Wrote firmware in Rust and took claude's help to write a Bluetooth (BLE) based controller that works over web browser as well as an iOS app. Opted for tank steering with 4WD, which is a lot of fun with the power it has. The car is so powerful/fast that I had to limit the max speed to 30% in my firmware 😅
0:48

Tesla wouldn't bring Cybertruck to India, so I built my own 😬 (a micro one) Used ESP32 as the controller, designed 3d printed tyres, chassis, shell, and added micro coreless motors that are otherwise used in small drones. Wrote firmware in Rust and took claude's help to write a Bluetooth (BLE) based controller that works over web browser as well as an iOS app. Opted for tank steering with 4WD, which is a lot of fun with the power it has. The car is so powerful/fast that I had to limit the max speed to 30% in my firmware 😅

Shantanu Goel

14,393 görüntüleme • 7 ay önce

Someone ran Claude Code on a beach where any device overheats and that spot suddenly turned out to be the best home for the most powerful AI in the world. This is the reMarkable Paper Pro. A paper tablet for notes with no browser and no social media and not a single app. He sat down right on the sand in the open sun and brought up Claude Code on Opus 4.6 over the Claude API on the paper screen and opened his project ~/repos/webs while the waves broke a few steps away. For years every device had the same trouble outside. In direct sun the screen glares and washes out and heats up and instead of your work you see your own reflection. But e-ink does not blast its own light into your face. It reflects the sunlight like the page of a book. And here is what came out of it. The very thing that kills any normal screen outside turned into fuel for this one. The brighter the sun the sharper the picture because it has nothing to glare with and nothing to wash out. And then comes the thing no laptop on a beach will give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it reads like a book in the sun and not a backlight you squint into. The picture only comes alive. In bright light it does not fade but turns sharper and higher in contrast than it ever was in a room. The charge lasts for days. E-ink barely touches the battery so there is no outlet anywhere on the sand and the tablet does not care. It weighs as much as a notebook. The whole setup folds into a beach bag like a pad with a pen on top. Everything on the screen is for real. Claude Code v2.1.110 and Opus 4.6 on the Claude API and the project ~/repos/webs open right on the e-ink in the middle of the sand. In my opinion this is the most unexpected home for an AI this year. Not an office with the blinds drawn and not a monitor cranked to full brightness but a quiet sheet of paper on the sand that open sun only makes better and on it the most powerful Claude writes code right on the page like a pen.
0:33

Someone ran Claude Code on a beach where any device overheats and that spot suddenly turned out to be the best home for the most powerful AI in the world. This is the reMarkable Paper Pro. A paper tablet for notes with no browser and no social media and not a single app. He sat down right on the sand in the open sun and brought up Claude Code on Opus 4.6 over the Claude API on the paper screen and opened his project ~/repos/webs while the waves broke a few steps away. For years every device had the same trouble outside. In direct sun the screen glares and washes out and heats up and instead of your work you see your own reflection. But e-ink does not blast its own light into your face. It reflects the sunlight like the page of a book. And here is what came out of it. The very thing that kills any normal screen outside turned into fuel for this one. The brighter the sun the sharper the picture because it has nothing to glare with and nothing to wash out. And then comes the thing no laptop on a beach will give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it reads like a book in the sun and not a backlight you squint into. The picture only comes alive. In bright light it does not fade but turns sharper and higher in contrast than it ever was in a room. The charge lasts for days. E-ink barely touches the battery so there is no outlet anywhere on the sand and the tablet does not care. It weighs as much as a notebook. The whole setup folds into a beach bag like a pad with a pen on top. Everything on the screen is for real. Claude Code v2.1.110 and Opus 4.6 on the Claude API and the project ~/repos/webs open right on the e-ink in the middle of the sand. In my opinion this is the most unexpected home for an AI this year. Not an office with the blinds drawn and not a monitor cranked to full brightness but a quiet sheet of paper on the sand that open sun only makes better and on it the most powerful Claude writes code right on the page like a pen.

Blaze

89,297 görüntüleme • 1 ay önce

FINALLY time for the big announcement everyone has been begging and waiting for... Here's a VERY EARLY direct hardware capture of Mario Kart 64... RUNNING ON THE SEGA DREAMCAST, of course! This game was literally just BARELY decompiled the other day, with a codebase that is still quite married to the Nintendo 64 platform... but this didn't stop jnmartin: the dark coding wizard who brought us a dynamically lit and bump mapped Doom 64 and Wipeout running at >100FPS on the DC! What you're seeing is the insane progress made by one man in just 3 weeks. As is to be expected, there are all kinds of visual glitches and rendering artifacts, the framerate is all over the place, and there's no audio yet... which is totally typical of any ambitious DC port in the early stages. The DC build wouldn't even get past the menu screen without crashing or running out of RAM until just a few DAYS ago, yet here it is, every level playable WITH multiplayer support already on the DC! Even in this early stage, you can already see the game benefiting from the PVR's crisp 480p output... Each players' little viewport window in 4 player mode is the same resolution as the entire screen was on the N64! Stay tuned for future updates as jnmartin continues his work to bring this classic to our little white box of Dreams!
3:29

FINALLY time for the big announcement everyone has been begging and waiting for... Here's a VERY EARLY direct hardware capture of Mario Kart 64... RUNNING ON THE SEGA DREAMCAST, of course! This game was literally just BARELY decompiled the other day, with a codebase that is still quite married to the Nintendo 64 platform... but this didn't stop jnmartin: the dark coding wizard who brought us a dynamically lit and bump mapped Doom 64 and Wipeout running at >100FPS on the DC! What you're seeing is the insane progress made by one man in just 3 weeks. As is to be expected, there are all kinds of visual glitches and rendering artifacts, the framerate is all over the place, and there's no audio yet... which is totally typical of any ambitious DC port in the early stages. The DC build wouldn't even get past the menu screen without crashing or running out of RAM until just a few DAYS ago, yet here it is, every level playable WITH multiplayer support already on the DC! Even in this early stage, you can already see the game benefiting from the PVR's crisp 480p output... Each players' little viewport window in 4 player mode is the same resolution as the entire screen was on the N64! Stay tuned for future updates as jnmartin continues his work to bring this classic to our little white box of Dreams!

Falco Girgis

55,593 görüntüleme • 1 yıl önce

I think it's time we all get a reality check on Diddy Kong Racing 64 for the Sega Dreamcast, including myself... So here it is: original DKR for N64 vs our ported DKR for DC, direct comparison with FPS counters enabled. The truth is that I've been staring at the FPS meter all weekend, obsessing over every little dip, vectorizing, loop unrolling, and optimizing every little expensive-looking loop I can see in the codebase to win back 0.1FPS at a time... totally losing sight of what the basis for comparison even was from the original... So how long has it been since you've played the original on N64? I'm not talking about via emulation with higher FPS and fancy upscaling. I'm talking about directly, on an actual, physical Nintendo 64. Full disclosure... prolly been half a decade now, for me! Anyway, the devs behind the decomp were kind enough to share with me some of their performance and timing analysis captures... so I figured we'd take a step back and have a little fun! I had no idea it was running at only 20FPS tops, capped at 15FPS for the WizPig races!? I just remember pissing myself at having never seen a game look that good or realistic in my entire life back in 1997 when DKR came out for the N64... All I know is I want to do this game justice... but the truth is that even though we're still cooking, already the Dreamcast runs consistently at 10FPS higher and runs at 4x the screen resolution with progressive scan output... What do you guys think? How's our port comparing?🤔
1:11

I think it's time we all get a reality check on Diddy Kong Racing 64 for the Sega Dreamcast, including myself... So here it is: original DKR for N64 vs our ported DKR for DC, direct comparison with FPS counters enabled. The truth is that I've been staring at the FPS meter all weekend, obsessing over every little dip, vectorizing, loop unrolling, and optimizing every little expensive-looking loop I can see in the codebase to win back 0.1FPS at a time... totally losing sight of what the basis for comparison even was from the original... So how long has it been since you've played the original on N64? I'm not talking about via emulation with higher FPS and fancy upscaling. I'm talking about directly, on an actual, physical Nintendo 64. Full disclosure... prolly been half a decade now, for me! Anyway, the devs behind the decomp were kind enough to share with me some of their performance and timing analysis captures... so I figured we'd take a step back and have a little fun! I had no idea it was running at only 20FPS tops, capped at 15FPS for the WizPig races!? I just remember pissing myself at having never seen a game look that good or realistic in my entire life back in 1997 when DKR came out for the N64... All I know is I want to do this game justice... but the truth is that even though we're still cooking, already the Dreamcast runs consistently at 10FPS higher and runs at 4x the screen resolution with progressive scan output... What do you guys think? How's our port comparing?🤔

Falco Girgis

51,979 görüntüleme • 6 gün önce

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.
0:47

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 görüntüleme • 2 ay önce

while we don’t know for sure if the iPhone mirroring feature will come to the Apple Vision Pro, I sure hope it does. for now, it's available on Mac—i tested it and it's amazing! here’s how you can experience it on your Mac today: 1. make sure both your iPhone and Mac are running the latest beta versions of iOS 18 and macOS Sequoia. 2. position your iPhone near your Mac. 3. an icon titled "iPhone Mirroring" will appear on your Mac's Dock. 4. select the "Continue" button on your Mac. 5. unlock your iPhone when prompted. 6. on your Mac, click the "Get Started" button. 7. with your iPhone locked, open the "iPhone Mirroring" app on your Mac. this feature is a game-changer, and i can’t wait for the day it hopefully comes to the Vision Pro!
0:25

while we don’t know for sure if the iPhone mirroring feature will come to the Apple Vision Pro, I sure hope it does. for now, it's available on Mac—i tested it and it's amazing! here’s how you can experience it on your Mac today: 1. make sure both your iPhone and Mac are running the latest beta versions of iOS 18 and macOS Sequoia. 2. position your iPhone near your Mac. 3. an icon titled "iPhone Mirroring" will appear on your Mac's Dock. 4. select the "Continue" button on your Mac. 5. unlock your iPhone when prompted. 6. on your Mac, click the "Get Started" button. 7. with your iPhone locked, open the "iPhone Mirroring" app on your Mac. this feature is a game-changer, and i can’t wait for the day it hopefully comes to the Vision Pro!

Justin Ryan

70,266 görüntüleme • 2 yıl önce

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below
17:28

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 görüntüleme • 1 ay önce

Someone ran Claude Code on an e-ink notebook and the slowest screen in the world suddenly turned out to be the best home for an AI that already thinks one word at a time. This is the reMarkable Paper Pro, a paper tablet for notes with no browser and no social media and not a single app. He went into it over SSH and brought up Claude Code on Opus 4.8 on Claude Max and typed right into the terminal on the paper screen: "hello reddit, this is ssh terminal on rmpp". For years this screen got slammed for one thing. E-ink is too slow and it draws with a delay and it ghosts and it is no good for real work. But Claude itself puts out a thought one word at a time. And here is what came out of it: the very thing that killed the paper screen for normal software lined up perfectly with the pace of the AI. There is no more lag because there is nothing left to lag. And then come the things no monitor can give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it feels like reading a book and not staring into a backlight. Nothing distracts you. Not a single notification and not a single tab and just a cursor and an agent that writes code while you simply watch the page. The charge lasts for days. E-ink barely touches the battery so Claude can grind on a task all night long and the tablet is still alive by morning. And it weighs as much as a notebook. The whole work setup now fits into a bag like a notepad with a stylus on top. Everything on the screen is for real: Claude Code v2.1.162 and bypass permissions on and Opus going off to think on max effort right on the e-ink. In my opinion this is the most unexpected home for an AI this year. Not a farm of graphics cards and not a wall of monitors but a quiet sheet of paper on a coffee table where the most powerful Claude writes code one word at a time like a pen.
0:52

Someone ran Claude Code on an e-ink notebook and the slowest screen in the world suddenly turned out to be the best home for an AI that already thinks one word at a time. This is the reMarkable Paper Pro, a paper tablet for notes with no browser and no social media and not a single app. He went into it over SSH and brought up Claude Code on Opus 4.8 on Claude Max and typed right into the terminal on the paper screen: "hello reddit, this is ssh terminal on rmpp". For years this screen got slammed for one thing. E-ink is too slow and it draws with a delay and it ghosts and it is no good for real work. But Claude itself puts out a thought one word at a time. And here is what came out of it: the very thing that killed the paper screen for normal software lined up perfectly with the pace of the AI. There is no more lag because there is nothing left to lag. And then come the things no monitor can give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it feels like reading a book and not staring into a backlight. Nothing distracts you. Not a single notification and not a single tab and just a cursor and an agent that writes code while you simply watch the page. The charge lasts for days. E-ink barely touches the battery so Claude can grind on a task all night long and the tablet is still alive by morning. And it weighs as much as a notebook. The whole work setup now fits into a bag like a notepad with a stylus on top. Everything on the screen is for real: Claude Code v2.1.162 and bypass permissions on and Opus going off to think on max effort right on the e-ink. In my opinion this is the most unexpected home for an AI this year. Not a farm of graphics cards and not a wall of monitors but a quiet sheet of paper on a coffee table where the most powerful Claude writes code one word at a time like a pen.

Blaze

421,977 görüntüleme • 1 ay önce

QVAC SDK 0.14.0 is live. This release makes the on-device stack faster on mobile, ships the developer-agent path, and takes local text-to-speech to 31 languages. Main highlights: - OpenCode and OpenClaw. The first official OpenCode plugin, plus a maintained OpenClaw compatibility path, both built on managed mode and qvac serve. Point a coding agent at a local model with far less setup and far fewer surprises. - Brain-computer interface transcription, on the SDK. Take recorded neural signal data and decode it into text, fully on-device, no cloud. Stream it in chunks through a simple API. In 0.14 it runs GPU-accelerated on iOS. - Text to Speech in 31 languages with our Supertonic3 upgrade. VOICE AND SPEECH - Supertonic3 multilingual TTS, 5 languages to 31. - Chatterbox and Supertonic now run on the Android GPU, with lower memory use (especially on iOS), quantized s3gen Chatterbox support, and a fix for Chatterbox occasionally emitting random speech. - Whisper transcription now runs on the iOS GPU. Parakeet runs on the Android GPU, with steadier real-time streaming. VISION AND OCR - VLM multi-tile batching: high-resolution Pan and Scan images are encoded in one pass instead of tile by tile, for faster vision throughput. - OCR on ggml (EasyOCR and DocTR) reaches full speed parity with the onnx path, across Metal, OpenCL, and Vulkan. PLATFORM AND RELIABILITY - Dynamic compute backends on Linux: one build picks the right backend at runtime, and opens the door to ROCm and CUDA support without per-backend builds. - Thinking tokens are kept out of the model context, so reasoning no longer fills the KV cache. SDK 0.14.0 is now leaner and faster to start. Let’s build.
1:51

QVAC SDK 0.14.0 is live. This release makes the on-device stack faster on mobile, ships the developer-agent path, and takes local text-to-speech to 31 languages. Main highlights: - OpenCode and OpenClaw. The first official OpenCode plugin, plus a maintained OpenClaw compatibility path, both built on managed mode and qvac serve. Point a coding agent at a local model with far less setup and far fewer surprises. - Brain-computer interface transcription, on the SDK. Take recorded neural signal data and decode it into text, fully on-device, no cloud. Stream it in chunks through a simple API. In 0.14 it runs GPU-accelerated on iOS. - Text to Speech in 31 languages with our Supertonic3 upgrade. VOICE AND SPEECH - Supertonic3 multilingual TTS, 5 languages to 31. - Chatterbox and Supertonic now run on the Android GPU, with lower memory use (especially on iOS), quantized s3gen Chatterbox support, and a fix for Chatterbox occasionally emitting random speech. - Whisper transcription now runs on the iOS GPU. Parakeet runs on the Android GPU, with steadier real-time streaming. VISION AND OCR - VLM multi-tile batching: high-resolution Pan and Scan images are encoded in one pass instead of tile by tile, for faster vision throughput. - OCR on ggml (EasyOCR and DocTR) reaches full speed parity with the onnx path, across Metal, OpenCL, and Vulkan. PLATFORM AND RELIABILITY - Dynamic compute backends on Linux: one build picks the right backend at runtime, and opens the door to ROCm and CUDA support without per-backend builds. - Thinking tokens are kept out of the model context, so reasoning no longer fills the KV cache. SDK 0.14.0 is now leaner and faster to start. Let’s build.

QVAC

23,973,950 görüntüleme • 1 ay önce

100 MAC MINIS ON ONE METAL SHELF. IN THE CLOUD, EACH OF THOSE RENTS FOR $120 TO $500 A MONTH. that clip is a homemade rack: wire shelving packed with mac minis, each running macos, wired into one cluster. why macs and not a normal server? two reasons. you can only build, sign, and notarize ios and mac apps on apple hardware. cloud providers know it and charge for it. and apple silicon sips power and runs near-silent, so you can stack a lot of them on a shelf in a room, not a datacenter. the rent they're escaping: a single mac in the cloud runs ~$120 to $500 a month (macstadium up to aws) one engineer documented saving $4,000+ a month by self-hosting mac minis instead of cloud ci runners a used or new mini is a few hundred dollars once, then a few dollars of electricity what a shelf like this actually runs: ios and mac build farms, render jobs, app and device testing automation, and increasingly local ai inference. own the boxes, rent nothing. the uncomfortable part: the cloud was never the only option. it was the convenient one. the people who did the math bought the shelf. the honest caveat: it's real capex up front, real heat and power, and you become the sysadmin. no rented rack means no one to call at 3am. worth it at scale, overkill for one build a week. no rack rental, no per-hour metering, no fleet you don't own. save this before your cloud invoice renews again.
0:25

100 MAC MINIS ON ONE METAL SHELF. IN THE CLOUD, EACH OF THOSE RENTS FOR $120 TO $500 A MONTH. that clip is a homemade rack: wire shelving packed with mac minis, each running macos, wired into one cluster. why macs and not a normal server? two reasons. you can only build, sign, and notarize ios and mac apps on apple hardware. cloud providers know it and charge for it. and apple silicon sips power and runs near-silent, so you can stack a lot of them on a shelf in a room, not a datacenter. the rent they're escaping: a single mac in the cloud runs ~$120 to $500 a month (macstadium up to aws) one engineer documented saving $4,000+ a month by self-hosting mac minis instead of cloud ci runners a used or new mini is a few hundred dollars once, then a few dollars of electricity what a shelf like this actually runs: ios and mac build farms, render jobs, app and device testing automation, and increasingly local ai inference. own the boxes, rent nothing. the uncomfortable part: the cloud was never the only option. it was the convenient one. the people who did the math bought the shelf. the honest caveat: it's real capex up front, real heat and power, and you become the sysadmin. no rented rack means no one to call at 3am. worth it at scale, overkill for one build a week. no rack rental, no per-hour metering, no fleet you don't own. save this before your cloud invoice renews again.

RetroChainer

21,055 görüntüleme • 15 gün önce

JNMARTIN HAS BROUGHT US CHRISTMAS EARLY THIS YEAR!!! His port of Star Fox 64 to the Sega Dreamcast is officially complete and was just released! Here's 9+ minutes of spliced direct hardware captures, featuring footage from every mission running on an actual physical DC at 480p! I have to say, the game feels incredibly smooth and responsive on the DC and controls extremely well. Also... as you can see, at twice the resolution with progressive scan, she looks gorgeous even with my cheap-ass HDMI cables and USB capture card. While jnmartin had the game up and running on DC within (literally) 2 days, there was an enormous amount of time and energy invested into faithfully recreating the experience graphically, implementing various bugfixes, and hunting for performance gainz... the man has never been satisfied with anything short of amazing with his ports, and it really shows. Like his Mario Kart 64 port, Star Fox 64 is also using my SH4ZAM library to hardware accelerate the math and linear algebra routines for DC; however, unlike last time, he's gotten so good at performance gainz that I barely did anything at all on that side, other than writing a few little inline SH4 ASM routines to cover some operations that I didn't already accelerate within the API... Suffice to say, though, that everything from the vertex TnL pipeline, to audio decoding, to gameplay-related trigonometry routines has been optimized for the SH4's FPU... jnmartin even got to bust out the SH4's MMU to accelerate the translation of of the segmented address scheme used by the game on N64 (which was apparently some suggested memory management model in the N64 docs) into the DC's virtual address space--which previously had to be done in software... So even more gainz! Sorry, though... but pretty sure this is why the game won't work in the Flycast emulator currently... whoops! 🤣 Shout-out to darcagent for contributing DREAMCAST RUMBLE PACK SUPPORT (among other things) to the release. Rumble support has historically been a pain-point within our KallistiOS homebrew DC SDK, as many 3rd party rumble packs are non-compliant and either do what they want with certain rumble commands or screw up the entire maple bus when they receive something they have decided not to fully implement... Great job getting that shit sorted out and tested with so many packs. All of my exotic (and cheapo) 3rd party rumble devices that I was able to test with seemed to work great! Finally, lets give SonicDcer a round of applause for being the lead dude behind the original N64 decompilation--as it was his original work that allowed for any of this to even be possible. He also continued to offer support and advice throughout the entire porting process, like a total chad. Here's the link to the official GitHub repo with instructions for building a Dreamcast image from a StarFox N64 ROM:
9:03

JNMARTIN HAS BROUGHT US CHRISTMAS EARLY THIS YEAR!!! His port of Star Fox 64 to the Sega Dreamcast is officially complete and was just released! Here's 9+ minutes of spliced direct hardware captures, featuring footage from every mission running on an actual physical DC at 480p! I have to say, the game feels incredibly smooth and responsive on the DC and controls extremely well. Also... as you can see, at twice the resolution with progressive scan, she looks gorgeous even with my cheap-ass HDMI cables and USB capture card. While jnmartin had the game up and running on DC within (literally) 2 days, there was an enormous amount of time and energy invested into faithfully recreating the experience graphically, implementing various bugfixes, and hunting for performance gainz... the man has never been satisfied with anything short of amazing with his ports, and it really shows. Like his Mario Kart 64 port, Star Fox 64 is also using my SH4ZAM library to hardware accelerate the math and linear algebra routines for DC; however, unlike last time, he's gotten so good at performance gainz that I barely did anything at all on that side, other than writing a few little inline SH4 ASM routines to cover some operations that I didn't already accelerate within the API... Suffice to say, though, that everything from the vertex TnL pipeline, to audio decoding, to gameplay-related trigonometry routines has been optimized for the SH4's FPU... jnmartin even got to bust out the SH4's MMU to accelerate the translation of of the segmented address scheme used by the game on N64 (which was apparently some suggested memory management model in the N64 docs) into the DC's virtual address space--which previously had to be done in software... So even more gainz! Sorry, though... but pretty sure this is why the game won't work in the Flycast emulator currently... whoops! 🤣 Shout-out to darcagent for contributing DREAMCAST RUMBLE PACK SUPPORT (among other things) to the release. Rumble support has historically been a pain-point within our KallistiOS homebrew DC SDK, as many 3rd party rumble packs are non-compliant and either do what they want with certain rumble commands or screw up the entire maple bus when they receive something they have decided not to fully implement... Great job getting that shit sorted out and tested with so many packs. All of my exotic (and cheapo) 3rd party rumble devices that I was able to test with seemed to work great! Finally, lets give SonicDcer a round of applause for being the lead dude behind the original N64 decompilation--as it was his original work that allowed for any of this to even be possible. He also continued to offer support and advice throughout the entire porting process, like a total chad. Here's the link to the official GitHub repo with instructions for building a Dreamcast image from a StarFox N64 ROM:

Falco Girgis

30,965 görüntüleme • 7 ay önce