Tinker aims to handle posttraining ML infra for everyone — what's holding users back?
PatrickToulme · x · 2026-09-22
PatrickToulme asked cHHillee on X what prevents him from using Tinker for all his posttraining needs — speed, cost, scalability, correctness paranoia, or flexibility? Tinker's hope is to handle all the ML infrastructure for posttraining for (approximately) everyone. The question kicked off a substantive discussion on the moats of posttraining-as-a-service.
More from Infra
- COLIBRI: pure-C zero-dep engine streams 2.8T-param MoE models from disk on consumer hardware — bibryam · 2026-09-22
- Sentdex benchmarks openjev: 169ms on Dell GB10 vs 137ms on RTX 3090 — Sentdex · 2026-09-22
- PyroDash cuts inference cost 96% by having a 4B model call the big one only when needed — jiqizhixin · 2026-09-22
- Underdog's Husky Inference Engine Claims 4.5x Speedup Over MLX, 730 tok/s on MacBook — jimmykoppel · 2026-09-22
- Full-Parameter RL on TPUs: peano_ai Runs 310B MiMo-V2.6 Across 1,000+ TPUs — simonguozirui · 2026-09-22
- Cloudflare Python Workers go generally available after two-year preview — Simon Willison · 2026-09-22