SzamarCsacsi

I love ouzo, but hate licorice.

Classes in JavaScript are just syntactic sugar around prototypes.

It's not the same though, is it? On Instagram and TikTok and the likes, you don't need "ugly filters", because there's instant feedback: clicks, impressions, likes, hearts, comments, whatever. In the film industry, for example, you won't know whether the product will be a success or not until after the fact that you spent a ton of money on it.

Pug is actually awesome. I use it daily with Vue and I just introduced it to a project I was put on recently.

I like this neat little code to filter out falsy values:

  array.filter(Boolean)

Oh, you're right. Been working with Vue lately where the component and Vuex inspectors are packaged into one devtools, that's why I got confused.

Time-travel debugging is miles better than the old way of placing breakpoints. For me, debugging with breakpoints was always a pain. I often skipped through stuff accidentally and had to start all over again from the beginning, or accidentally went inside some third-party library code that I did not intend to, or placed the breakpoint at the wrong spot. It was just slow and inconvenient, unlike React DevTools where you can see every change and step forward or backward, replay events and observe the state at various points without having to put watchers on every variable / expression.

Also you can be an extrovert with severe social anxiety. At least that's what I consider myself, because I don't share any traits with introverts other than being considered shy, because I struggle in social situations.

I'm terrified of deepfakes because they will at some point completely devalue photographic evidence. On one hand, it will make it easier to manufacture evidence and frame people. On the other hand, it will make it easier to get away with stuff despite real photographic evidence by simply blaming it on deepfakes. This is already happening with the whole fake news phenomenon. People's perception of truth will be even more skewed.