today's "searching for mapbox and observablehq on twitter results": a groyper used mapbox to make a racist map and mapbox shut them off, so a bunch of assholes are crying a pedocon is using an observablehq map of historical age of consent to downplay the epstein files 2026 is 2026 in every corner
A new community program is landing Monday. Helpers, you’re gonna like this 👀
working on it! :)
great to be a programmer at google, terrible to be a programmer using google. (sorry 🌶️ but this makes ex-google people marginally more annoying than other ex-faang people)
they bundle every sdk with types for every google service (around 320 of them) github.com/googleapis/g... perusing the @val.town npm module cache usage… 
We're looking for feedback on our new SKILL.md for generated projects! If you're using Tuist's project generation, we'd love to hear your thoughts.
https://community.tuist.... 
Now GitButler has a CLI!
Stacked and parallel branches, smartlog, simple commit editing, easy undo, json output to every command. And it just works in any Git repo.
Check it out:
blog.gitbutler.com/but-cli 🚨 Reminder: legacy prerendering is being retired by plan tier. If you are still using legacy prerendering, migrate to the Prerender extension(s) before your plan’s cutoff date.
Timeline and next steps:
www.netlify.com/changelog/20... 
✨ What's New in ViteLand: January 2026 Recap
◆ Unified redesign across all VoidZero sites
◆ @vite.dev crossed 3 billion npm downloads
◆ @rolldown.rs reached RC status
◆ Lazy Barrel Optimization landed in Rolldown
◆ Oxfmt hit 100% Prettier conformance
◆ ...and more 👀
voidzero.dev/posts/whats-... 
Questions like this surface often in the community.
If something feels off during setup or upgrade, chances are it’s already been talked through in Discord:
pris.ly/discord In v7, files like enums.js aren’t bundled by default, they’re created when you run prisma generate.
Skip that step, and your imports will fail. 
This error has come up a few times in Discord 👇
“Upgrading to Prisma v7 and getting `Can't resolve ./enums.js` when importing from a custom client path?”
It usually means the client wasn’t regenerated after the upgrade. 
if prev[y] != next[y]
move cursor to y
erase line y
write next[y]
X/Y targeting. Surgical. Sub-frame re-render.
There's a lot more that goes into this. Pretty exciting work. JIT Diff: find diff && delta, update delta
Frame N Frame N+1
--------- ---------
? Name ? Name <- same
> hell > hello <- delta
Only line 2 redraws done before refresh
PROBABILITY
P(flicker) = gap / 16ms
0ms = 0%
1ms = 6%
8ms = 48%
16ms = 96%
THE TECHNIQUE
Standard: clear all, redraw all CRTs synced to it
Standard won globally
FRAME BUDGET
30Hz = 33ms
60Hz = 16ms <-- standard
120Hz = 8ms
THE FLICKER PROBLEM
BAD:
ERASE-----gap-----WRITE
0ms 10ms 20ms
^
refresh here = BLANK
GOOD:
ERASE+WRITE
0ms 2ms
^ You have 16ms. Funny how my electrical engineering degree is coming in play here. 60 FPS = 60 Hz (get it?).
THE TIMELINE
0ms 16ms 32ms
| | |
[F1] [F2] [F3][...]
Miss the window = flicker
WHY 60?
US power = 60Hz 1 second = 1000ms
1000ms / 60 FPS = 16.67ms THE MATH I'm building a JIT Differential Rendering engine for a new TUI framework that'll power Command Code.
you have exactly 16ms before your eyes detect the flicker. Instead of clear→redraw, we diff X/Y coordinates and surgically update only changed lines.
Result: sub-frame updates, zero flicker It is a simple as
```
vitest --tags-filter="frontend && !(slow || flaky)"
```
No more scattered workarounds. Your test organization finally matches how you think about your code.
Wanna know more?
Check out the docs
main.vitest.dev/guide/test-t... Every test suite eventually categorizes tests: "skip this in CI," "this one is flaky," "that one needs more time." and so on. Vitest 4.1 (in beta right now) introduces Test Tags: You can now define these categories globally, attach config or behavior and eventually filter what runs.
#ZedEditor