ulan

8 ms·

1. 1.▲
   by ulan 4y ago

   I guess the authors used a raw allocation in the example code to show the simplest possible use-after-free. Any software with complex object ownership written in a language without GC has to balance between user-after-free (freeing an objec
2. 2.▲
   by ulan 6y ago

   Author here. Fingerprinting is a valid concern. The API explainer has a section about it: https://github.com/WICG/performance-measure-memory#fingerpri... It is important to keep in mind that the API only accounts for t
3. 3.▲
   by ulan 6y ago

   Author here. The new API excludes the objects allocated by extensions, so the results should be more stable and actionable compared to the existing tools. I filed a feature request for DevTools heap snapshot to do the same: https:/&#x
4. 4.▲
   by ulan 16y ago

   I like how the author contrasts monads with applicative functors and demonstrates why monads are more powerful.