Cool Bits
-
Ryan Dahl just shared an update on the Oracle-JavaScript trademark lawsuit – but I’ll probably just wait for Aaron Sorkin to turn it into a courtroom drama with characters who all talk really fast.
-
Dan Farrelly (Inngest’s CTO) wrote this deep dive on The principles of Durable Execution. It could come in handy next time that one co-worker starts talking crazy about distributed systems.
-
ES Module Shims 2.0 just came out with TypeScript type stripping support.
-
CarbonQA provides high-quality QA services that scale. Their US-based testers will break your app repeatedly, work directly in your tools, and do all the manual testing you hate doing yourself. [sponsored]
-
Daniel De Laney wrote about how chat is a bad UI pattern for devtools, which might explain why Claude keeps gaslighting you.
-
Beej’s Guide to Git is the only Git resource you’ll ever need, despite sounding like the name of the treasure map in Goonies.
-
David Cramer wrote about product-market fit. But I’m not really sure what qualifies him to write this post besides co-founding a software company that prints hundreds of millions of dollars a year.
-
Salma Alam-Naylor wrote about how she learned to code with her voice
-
The Angular Documentary just dropped. It’s great, but if we want this thing to get picked up by Hulu or Netflix, we’re gonna need Miško to start a cult or fake his own death (preferably both).
Pop Quiz: Answer
Sponsored by bolt.new
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?
Built with ❤️ by ui.dev
50 W Broadway Ste 333 PMB 51647 Salt Lake City, Utah 84101
Cool Bits
-
Ryan Dahl just shared an update on the Oracle-JavaScript trademark lawsuit – but I’ll probably just wait for Aaron Sorkin to turn it into a courtroom drama with characters who all talk really fast.
-
Dan Farrelly (Inngest’s CTO) wrote this deep dive on The principles of Durable Execution. It could come in handy next time that one co-worker starts talking crazy about distributed systems.
-
ES Module Shims 2.0 just came out with TypeScript type stripping support.
-
CarbonQA provides high-quality QA services that scale. Their US-based testers will break your app repeatedly, work directly in your tools, and do all the manual testing you hate doing yourself. [sponsored]
-
Daniel De Laney wrote about how chat is a bad UI pattern for devtools, which might explain why Claude keeps gaslighting you.
-
Beej’s Guide to Git is the only Git resource you’ll ever need, despite sounding like the name of the treasure map in Goonies.
-
David Cramer wrote about product-market fit. But I’m not really sure what qualifies him to write this post besides co-founding a software company that prints hundreds of millions of dollars a year.
-
Salma Alam-Naylor wrote about how she learned to code with her voice
-
The Angular Documentary just dropped. It’s great, but if we want this thing to get picked up by Hulu or Netflix, we’re gonna need Miško to start a cult or fake his own death (preferably both).
Pop Quiz: Answer
Sponsored by bolt.new
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?
Built with ❤️ by ui.dev
50 W Broadway Ste 333 PMB 51647 Salt Lake City, Utah 84101
发布者