Tim Caswell retweeted
Starting August 10, Vercel's CDN will stop stripping the 𝚂𝚎𝚛𝚟𝚎𝚛-𝚃𝚒𝚖𝚒𝚗𝚐 response header and pass it through to the browser.
Report backend metrics like database query time, and they show up in the network panel and the Performance API.
vercel.com/changelog/server-…
Tim Caswell retweeted
“All are invited to participate in a unified fast to express gratitude for religious liberty and to pray that it be strengthened throughout the world,” wrote Church President @OaksDallinH and his counselors in the First Presidency.
thechurchnews.com/members/20…
Tim Caswell retweeted
When Opus 4.5 came out, it was a one-way door to a new way of engineering. Agents now do most of our coding.
Knowing the inherent flaws and over-confidence of LLMs, we sent a clear message to our teams. Vibing and mission-critical infrastructure don’t go together.
We’re sharing some of our early internal guidance in how we’re “agenting responsibly”, prioritizing security, durability, and availability at all times.
vercel.com/blog/agent-respon…
Tim Caswell retweeted
i'm looking for someone truly obsessed with web performance to join the Next.js team
no need for prior framework experience, just strong React skills and real product performance wins :)
if you love squeezing every millisecond out of the web, please reach out 🙏
Tim Caswell retweeted
An absolute giant of a man. Legendary kindness and service.
I miss him already 😞
With sorrow we announce that Russell M. Nelson, beloved President of The Church of Jesus Christ of Latter-day Saints, has died. He was 101 — the oldest president in the history of the Church.
For more information on the life and ministry of President Russell M. Nelson, see below:
newsroom.churchofjesuschrist…
Tim Caswell retweeted
We’ve made all CDN serving on Vercel 10% faster (P75), while reducing memory by 15%.
Learn the behind the scenes of applying Bloom filters to this problem, while serving 1T monthly requests.
vercel.com/blog/how-we-made-…
Tim Caswell retweeted
With exponentially compounding AI technologies promising new ideas and new possibilities in coming years, we confront profound questions:
• What it means to be human?
• Who and what will define perceptual “truth”?
• Emotional relationships between humans and AI (including AI companions)?
• How we understand divine principles of work, faith and reasoning, even relationship with the Divine?
I spoke about these issues today at the Religions for Peace World Council Meeting held in Istanbul, Türkiye. I called for religious actors to action in three AI-centered areas which affect faith, ethics, and human dignity.
First, be clear, and help society understand, AI is not and cannot be God. No set of utilitarian AI algorithms should determine or speak for our most treasured human values and spiritual experiences.
Second, help chart a future where AI genuinely contributes to the common good, including human thriving and common prosperity, for people everywhere.
Third, commit together to ensure AI’s moral compass is not dictated solely by technology or the small group developing the technology. All those committed to faith-based morals, ethics, and values are needed in this conversation.
Our most precious truth, comfort, revelation, guidance come when we personally commune with the Divine. Spiritual truth and light come from understanding who God is in creation and the universe. For children of God, platforms and technologies cannot substitute for authentic Divine connection and relationship.
Tim Caswell retweeted

Tim Caswell@creationix21 Jun 2025
United States
United StatesConnected via United States Android AppAccount-level information, not a live location or per-post device.
In case it's not clear where I stand on what men should do:
- we should love and help marginalized people as Jesus taught
- women should be respected and supported as peers
- raising a family is an honorable sacrifice and you absolutely should love them – at Arkansas, USA
Tim Caswell retweeted
I met @mikeal at NodeCamp 2010 in Marin County, CA. We never grew very close, but I remember being impressed at his ability to lead.
The conference was an "unconf", which means that we all decided collectively which tracks we would have and who would be presenting.
Mikeal was there to lead the conversation and stitch it all together like a pro. He had built the well-known request library, so he had some clout. I was working on a library called "strata" at the time, which nobody was using, and almost nobody there knew who I was (except @creationix did!).
I'm grateful to Mikeal for stepping up and leading many of the conversations and initiatives in the early Node.js days. He was one of the pioneers of the server-side JS ecosystem.
RIP to a real legend of open-source and Node.js @mikeal
As he would, he appropriately over-engineered his memory beyond death and solicited pull requests. Here is mine. While I'm not sure further PRs can be merged, I'm sure they are still appreciated
github.com/mikeal/cancer-dia…
Tim Caswell retweeted
Racket - the Language-Oriented Programming Language - version 8.17 is now available from download.racket-lang.org
See blog.racket-lang.org/2025/05… for the release announcement and highlights.
#lisp #racketlang #scheme
Tim Caswell retweeted
The @TC39 Stage 1 Enum proposal by @typescript's @rbuckton solves all three of these problems 👍
github.com/tc39/proposal-enu…
I think I've figured out why I don't like enums in TS.
There's nothing particularly wrong with them. You can use them and they work fine.
But they go against three heuristics that I use when writing code:
- WYSIWYG - no hidden behavior, keep things simple, as few layers between you and the outputted code as possible. Keep it "JavaScript with types".
- Maximize portability - write once, run anywhere. Enums can't be used in Node. const enums have some restrictions about where they can be used.
- Listen to the maintainers - if enums were proposed for TS now, they wouldn't be added. If the maintainers moan about a feature, stray away from it.
So, they make me feel a little queasy.
Tim Caswell retweeted
DDoS protection explained by @vercel's cracked engineering team. vercel.com/blog/protectd-evo…
Tim Caswell retweeted
Nice little article on how Zig interops with C. Amazing, the ease with which you can use C external libraries. A good read!
Tim Caswell retweeted
Node.js v23.6.0 is out! 🥳🎉
This release enables the flag --experimental-strip-types by default.
Node.js will execute TypeScript files without additional configuration!
⚠️ This feature is experimental, has limitations and is subject to change.
nodejs.org/en/blog/release/v…
Tim Caswell retweeted

Mitchell Hashimoto@mitchellh7 Jan 2025
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
“Zig’s Comptime is Bonkers Good.” It is. And I think other languages should seriously consider comptime. Its utility is so broad. Ghostty would be significantly worse or messier without it. scottredig.com/blog/bonkers_…
Tim Caswell retweeted
Are you using @vercel Blob? If yes, help us make it better:
By default, our SDK adds random suffixes:
put('file.png', File) => $storeId.public.blob.vercel-storage.com/file-xxxxx.png
We're thinking about making this feature an option rather than the default.
What do you think?
44%Keep it like that
56%Make it an option
18 votes • Final results Tim Caswell retweeted
if you're working with JSON in size constrained environments, check out rando by @creationix
JSON.stringify -> rando.stringify
JSON.parse -> rando.parse
in my tiny example it went from 731 chars to 512 chars
























