Bytes： Warp wants it all

Cool Bits

1. Check out the Warp Code announcement post if you want a deeper dive on everything they just launched, without me trauma dumping about my youth rodeo career. You can also use code BYTES if you want to try a month of Warp Pro for just $1.

2. React Native 1.0 is officially “on the horizon” – which sounds great, until you realize that the Earth is round 🙃.

3. Nick Khami wrote about building SSR with Vite to create a custom replacement for getStaticProps.

4. @convex-dev/agent is Convex’s new open source component for building AI agents with just TypeScript. [sponsored]

5. Deno’s Fresh framework just released a v2.0 beta with Vite support, so you can now run Fresh as a Vite plugin with all that sweet Vitey goodness baked right in.

6. Dimitri Mitropoulos wrote about stress testing Biome’s noFloatingPromises lint rule – which is like that one time I stress tested my heart by speed running a haunted house while on MDMA.

7. Google just released EmbeddingGemma, an open embedding model designed to deliver high performance for on-device AI.

8. Vercel just shared their Open SDK strategy to “articulate their commitment” to open source, community, portability, freedom of choice, democracy, America, world peace, Taylor Swift, and those weird little stamp tattoos that come in the Cracker Jacks box 🫡.

9. Datadog created a free ebook called 5 ways to reduce container costs, and I’m 90% sure this isn’t a Pyrex vs. Tupperware debate. [sponsored]

10. TkDodo wrote about deriving client state from server state.

11. Lyra wrote an article called You no longer need JavaScript – unless you want to find romantic love and feel accepted by your peers at some point in your life.

12. Jake Archibald wrote about making XML human-readable without XSLT, which he calls an “esoteric corner of the web.” But if you could see my Chrome history, you would know that I was born in the dark esoteric, molded by it.

---

Pop Quiz: Answer

Sponsored by Clerk

What gets logged?

let sharedVariable = "initial";

setTimeout(() => {
  sharedVariable = "updated by first timeout";
}, 500);

setTimeout(() => {
  if (sharedVariable === "initial") {
    console.log("Shared variable not yet updated");
  } else {
    console.log("Shared variable was already updated");
  }
}, 500);

In JavaScript, the execution order for setTimeout callbacks with identical delays aren’t deterministic. This means we aren’t guaranteed that the first timeout callback will execute first (which can be the cause of some nasty and difficult to reproduce bugs). In reality it’s almost always what you’d expect (“Shared variable was already updated”), but it’s best not to rely on that behavior.

Here’s a famous talk by Philip Roberts to learn more about the event loop and how JavaScript handles asynchronous code.

Want us to say nice things

about your company?

Sponsor Bytes

or share it

Built with ❤️ by ui.dev

50 W Broadway Ste 333 PMB 51647 Salt Lake City, Utah 84101