Jake Leventhal retweetledi
Jake Leventhal
218 posts

Jake Leventhal
@JakeLeventhal
CTO building @RiotIQ and Artelo
Florida, USA Katılım Mayıs 2021
61 Takip Edilen64 Takipçiler

@ericzakariasson @leerob Some first impressions/feedback on Glass:
Overall it's quite refreshing and removes a ton of the VS Code noise but it's missing a few key features.
1. Worktrees. This is now my go to method of starting tasks in Conductor that makes starting local work much easier and lower friction.
2. Git integration is very minimal. The most important feature for me in an editor is reviewing diff. I use Cursor instead of Conductor for viewing diff simply because of VS Code's superior diff viewing (character diffs, staged vs unstaged, etc.) and for the Git Graph extension (notably this landed in @zeddotdev recently). Glass currently seems to only let me stage entire files, not hunks, or specific lines, which makes it feel very vibe codey in its current state and not for serious work.
3. Threads within workspaces. This is something that Conductor crushes and it makes it super easy to do multiple things at once within the same task. Need this feature.
4. Pull request reviews. I currently exclusively review PRs via Cursor with the GitHub extension. If Glass doesn't add this I cannot use Glass.
Thanks for reading if you do, also CC @t3code @t3dotchat since the same feedback applies.
English

Holy crap... with the @nextjs 16.2 update the next server is now using 10GB+ of memory and my MacBooks fan is running constantly (before it never even turned on).
What's going on here...

English

@timneutkens @wSokra @rauchg The problem is I cannot reliably reproduce this. Seems to be on and off. Any other advice for reproduction?
English

@timneutkens @wSokra @rauchg After upgrading to Next.js 16.2 (turbopack), performance is noticeably far worse. My dev boot times are exactly the same, but now I have weird caching issues and my dev server reaching nearly 200 GB RAM. My whole team reporting the same.
English

@rauchg I was exciting to try this out, and did my own internal benchmarking in a large turbopack app. From a clean slate on 16.1 (no .next) it took ~15s for the dev server to load. On a cached load, ~5s.
On 16.2... literally the exact same. Are these benchmarks fake?
English

Next.js 16.2 “Snow Leopard” 🐆
i.e.: sheer focus on performance, agentic developer experience, robustness
Next.js@nextjs
Next.js 16.2 • Up to ~60% faster rendering • Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup • Server Function 𝚍𝚎𝚟 logging • Redesigned error page • Better hydration errors • 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay nextjs.org/blog/next-16-2
English
Jake Leventhal retweetledi

@theo Need feature parity to Conductor with the "Spotlight" feature and ability to open worktrees from PRs and Linear issues
English

@tan_stack Maybe I'm not understanding, but to me this looks like the fastest way to distribute a malware skill to 10s of millions of Codex/Claude Code users undetected.
English

You asked for TanStack skills, we built the whole pipeline.
Introducing @tan_stack Intent (alpha)
📦 Ship agent-readable "skills" inside npm packages
🔍 Auto-discovered from node_modules
🔄 Knowledge sync with npm update
📂 Distributed - skills live in library repo
🧩 Composable - mix core + framework-specific skills
🌐 npm, pnpm, bun, yarn, deno
No stale training data. Just npm install!
🔗 ⬇️🧵
English

@zain_hoda did i just get flamed by a guy building a chatgpt wrapper
English

@JakeLeventhal Turns out there are way more of you than I expected. Good for Vercel.
Adam Pippert@AdamPippert
@zain_hoda Of course there is, you forgot the “pretends to know what they’re doing but really doesn’t” segment. Maybe the largest one…
English











