Jacob Maynard
161 posts

Jacob Maynard
@Jacob_A_Maynard
Masters student at SLU. Building full stack local-first apps on Cloudflare and SolidJS. Hire me
St Louis, MO Katılım Haziran 2018
215 Takip Edilen4 Takipçiler

@beginbot We pay to create things like just-bash and open source them. We're hiring.
English

How much does @rauchg pay to post bad about Cloudflare employees?
I can be bought and am ready to write some scathing exposés 😈
Malte Ubl@cramforce
English

@agcty_ We did that. Our editor is totally home grown. If what you want to do is sync the editor state data structure to some number of clients there are vastly simpler and vastly better algorithms for this. Crdts for text editing are only useful in truly p2p topologies.
English

Ok. For the last, like, 15 years, I've constantly been told that CRDTs (and Yjs in particular) solve collaborative text editing. Both the offline and live-collab cases. After an excruciatingly painful evaluation, I argue not only is this completely false, they're generally not appropriate for production-grade editors... at all.
Yeah, I know: everyone uses Yjs, so the problem must be us. Right? That's what I thought too. Well, did you know that on every single collaborative keystroke, Yjs will REPLACE YOUR ENTIRE DOCUMENT? (See this GitHub issue: github.com/yjs/y-prosemir…) Did you know that this is BY DESIGN? (See this discussion on the ProseMirror boards: discuss.prosemirror.net/t/offline-peer…) Did you know that this breaks, like, every editor plugin? (See the ProseMirror author's commentary here: discuss.prosemirror.net/t/offline-peer…)
I am not trying to bag on anyone, but to me this kind of mistake belies a fundamental misunderstanding of what text editors need to perform well, in any situation, let alone a collaborative one.
Anyway, learn from my pain. I wrote a somewhat long-form article about all the other challenges we ran into with CRDTs on our blog: moment.dev/blog/lies-i-wa…
English

@TheGingerBill i will often just grab the repo and read the source code because some edge cases or the general api surface is often not covered well in documentation
English

why would they choose electron over tauri in 2026

Theo - t3.gg@theo
T3 Code is now available for everyone to use. Fully open source. Built on top of the Codex CLI, so you can bring your existing Codex subscription.
English

@catebligh @soychotic actually its the complete opposite, if you have any idea about images and standards then you would love webp
English

@soychotic people who fight for webp in the comments don't work with images on the regular and it shows
English

@leanderriefel im pretty sure you cant change vite config without reload so that isnt possible
English

@thepix_elated @pjcavender @quantian1 doesnt matter if it’s legal or not, it is still morally bad and shouldnt be legal
English

@pjcavender @quantian1 Thanks ChatGPT. Now explain how that’s illegal
English

Let me get this straight:
Anthropic refused to work with DoW unless they could promise their tech wasn't used for surveillance or killing.
DoW said that they need full capabilities.
Anthropic declined to give full access.
OpenAI stood by Anthropic for ensuring AI safety.
Trump then cancelled all Anthropic usage across the government, including a $200m contract.
OpenAI then submits a bid to replace Anthropic.
English

@sama @dom_scholz any chance there is room in that funding to interview me to do some of that work to build tools users deserve?
English

@mattpocockuk @matteocollina fact, thinking is important, but also turning on reasoning yields way better model output in addition to also thinking yourself
English

@AnthropicAI i generally dont express evaluation in the same conversation. i test outside and often use a fresh context window purely for evaluation. i also build in many steps for claude to evaluate and validate the generated code and scope features accordingly so i usually have high success
English

New research: The AI Fluency Index.
We tracked 11 behaviors across thousands of Claude.ai conversations—for example, how often people iterate and refine their work with Claude—to measure how well people collaborate with AI.
Read more: anthropic.com/research/AI-fl…
English

> Claude writes the code.
> Supabase runs the backend.
> Vercel handles deployment.
> Namecheap gets you a domain.
> Stripe collects the money.
> GitHub tracks your code.
> Resend sends the emails.
> Clerk manages auth.
> Cloudflare handles DNS.
> PostHog tracks analytics.
> Sentry catches errors.
> Upstash powers Redis.
> Pinecone stores your vectors.
> OpenAI / Anthropic for AI brains.
> Railway for extra compute.
> LemonSqueezy for global payments.
> Framer / Webflow for landing pages.
> Canva for instant design.
> Figma for UI.
> Notion for docs.
That’s your entire “tech stack.”
No office.
No investors.
No 20-person team.
Just WiFi, a laptop, and execution.
You can literally build a $10k/month startup from your bedroom in 2026.
It’s not that deep.
Ship.
English

As a Frontend Developer,
Please slap yourself if you cannot clearly explain at least 10 of the following :
Hydration
Partial hydration
Islands architecture
Streaming SSR
Concurrent rendering
Time slicing
Reconciliation algorithm
Fiber architecture
Virtual DOM diffing complexity
Structural sharing
Immutable data patterns
Referential equality
Memoization pitfalls
Stale closure problem
Event loop (macro vs microtasks)
Task starvation
Layout thrashing
Critical rendering path
Render blocking resources
Tree shaking internals
Code splitting strategies
Dynamic import chunking
Module federation
Shadow DOM
Custom Elements lifecycle
Web Components interoperability
Web Workers vs Service Workers
SharedArrayBuffer
Transferable objects
OffscreenCanvas
WebAssembly integration
Browser compositing layers
Paint vs composite vs layout
GPU acceleration in CSS
CSS containment
Subpixel rendering
IntersectionObserver internals
ResizeObserver loop limits
MutationObserver cost
IndexedDB
Service Worker lifecycle traps
Cache invalidation strategies
Stale-while-revalidate
ETag vs Cache-Control
HTTP/3 and QUIC
Priority hints
Preload vs Prefetch vs Preconnect
CORS preflight
SameSite cookie modes
CSRF vs XSS mitigation
Content Security Policy (CSP)
Trusted Types
DOM clobbering
Prototype pollution
Race conditions in UI state
Tearing in concurrent UI
Scheduler priorities
Render waterfalls
Suspense boundaries
Selective hydration
Server components
Edge rendering
Micro-frontend orchestration
Finite state modeling
Event sourcing in frontend
Optimistic UI rollback strategy
Offline conflict resolution
CRDT basics for collaboration
WebRTC
Backpressure in streams API
AbortController
Streaming fetch response handling
Browser memory leak detection
Detached DOM nodes
Garbage collection timing
PerformanceObserver API
Long tasks API
First Input Delay (FID)
Interaction to Next Paint (INP)
Cumulative Layout Shift (CLS)
Largest Contentful Paint (LCP)
Speculative prerendering
Priority inversion in async code
Deterministic rendering
Idempotent UI actions
Accessibility tree
ARIA live regions internals
Pointer events
English

@devagrawal09 theres just a lot of edge cases to handle, what do you do with truly online-only features? it is unfortunately not as simple a flipping the “offline first” switch
English

Peter Steinberger bent over for Sam Altman real quick, wow.
Shitting on #keep4o users must be the secret handshake for joining OpenAI.
Claude, Grok, Gemini are actually getting better every month, while you clowns have a team of brain-dead employees circle-jerking online and a handful of models that can only spit out cheap template slop.
Clap clap 👏 for the decline. @OpenAI @sama @fidjissimo @steipete
#BringBack4o #keep4oAPI #StopAIPaternalism

English











