by 0xedb on 4/16/25, 11:23 PM with 11 comments
by CRConrad on 4/17/25, 9:45 AM
"The rest of this article is exclusive!
This article will unlock in 6 months"
Hovering over the "6 months" bit displays a hint, "Monday, 13 October 2025 at 23:30:00". (ETA: though it doesn't say in which timezone.)
.
As for the bit of content we are allowed to see, it certainly didn't sell me on Rust... but sure confirmed my resolution to avoid JavaScript at all cost.
by kretaceous on 4/17/25, 12:51 PM
- While not part of the ECMAScript spec, there is a Web API called structuredClone for deep copying objects. It's implemented in major runtimes like Node (17+), Bun and Deno. https://developer.mozilla.org/en-US/docs/Web/API/Window/stru...
- I've found a total of one use case for Object.freeze until today. Since exported modules are live bindings and are mutable, exporting a global object which is not intended to change during the runtime (e.g. an application wide config) is a bad idea. Exporting the object after wrapping it in Object.freeze can help avoid unnecessary mutations to it.
by rererereferred on 4/17/25, 12:45 PM
by 7bit on 4/18/25, 10:52 AM
Why? Even the video doesn't explain it, but I feel that's quite important to the article/video.
by poulpy123 on 4/17/25, 10:15 AM
by n8henrie on 4/19/25, 12:09 PM
> The converse is also true: if there's not a workaround, it's not ok.