Not the point of the article but just two cents about the JS part:
- 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.
Not sure if the article mentions this later but JS has structuredClone now which should be better than the stringify/parse dance in the example: https://developer.mozilla.org/en-US/docs/Web/API/Window/stru...
> // note: taking `&String` is needlessly restrictive, but one thing at a time
Why? Even the video doesn't explain it, but I feel that's quite important to the article/video.
I confess to feel weird at the idea to need a copy to print something twice
https://news.ycombinator.com/item?id=41770479 > Re paywalls: if there's a workaround, it's ok. ...
> The converse is also true: if there's not a workaround, it's not ok.
After a promising start, it says:
"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.