JavaScript Metaprogramming - Dave Fancher - NDC London 2022

Metadata, data about data, is everywhere. We seem to intrinsically understand that using data to further describe the data within our systems brings numerous benefits to taming complexity. It follows then that metaprogramming, programming that interacts with the program itself by inspecting or even manipulating its own code can bring similar benefits to our software.
ES6 greatly expands upon JavaScript's existing metaprogramming capabilities with the Symbol, Reflect, and Proxy types. Through some practical examples we'll discuss the role each of these types play within JavaScript metaprogramming and see how they not only affect your code but even drive several modern language features.
Check out more of our featured speakers and talks at
www.ndcconfere...
ndclondon.com/

[@hamzakhiar3636]

I didn't understand the symbols example where can I find the code

[@AmirPlusH]

Source code from Dave’s github: github.com/davefancher/js-metaprogramming-old

[@mafazabrar4349]

This talk is amazing! Leaned a lot about JS and its internals.

[@dearlordylord]

There’s nothing wrong with “delete” semantics of returning true when target is already deleted. It’s a valid point of view on this operation with idempotence in mind. It could have been implemented another way around, yes, but it would’ve meant the same kind of inconveniences but for another set of use cases. 9:57

[@matheuss7348]

The is a problem with the delete returning true when the operation wasn't done is that, if it is already deleted and still returning true to me, it is lying to me. It is saying that, in some usecase which i'm deleting an property means that i'm expecting that property to exists. If not, then, there is something wrong before the delete and it may leads to future bugs. It should throw an error, not returning true to me.

[@dearlordylord]

@@matheuss7348 I don’t remember the context of this comment anymore. But always: it depends