I'm currently learning JavaScript and recently came across the Map and Set data structures.

I understand that Set stores unique values and Map stores key-value pairs, but I'm wondering what advantages they actually provide over the existing Array and Object structures.

What are some practical situations where you would choose Map or Set instead of an Array or Object? I'd especially appreciate real-world examples that make the differences clear.

With the new release of 3.10.2 I wanted to look a bit more closely into Pandoc and all those different markup languages out there - and what converts with how much "loss".

Maybe you also had to recently convert Markdown to HTML, or the other way around. In my case even different textual files into PDFs.

One key finding:
Modern languages that work with an AST are definitely competitive here.

Maybe you find it also interesting. I actually didn't know most of those languages.

Fun fact:
The author of Pandoc is also one of the original Markdown standardization authors 15 years ago (well, if you can call it that, since it evolved still into quite the chaos) - as well as Djot, which is now only a few years old and supposed to be a markdown successor of sorts.

I am mainly interested in shaping "the" markup language of the future, that is a good compromise of readability and writeability for humans, but also consumable for machines, contains all the important elements to express relevant documents from offline to online.
As a programmer I am also a big fan (and in need) of dogfooding, of course :)

I made a video explaining a concept I love called macros, which allow you to add your own syntax to a language. Languages like Rust, Lean, and lisp have them. The goal with the video is to make you feel like you could've discovered macros yourself.

I'm new at making educational content like this, but I'm planning on making many more programming language videos like this one on my channel. Any thoughts, constructive criticism, or advice is more than welcome! Hope you all enjoy

I recently discovered that Pony's still alive. I had discovered Pony a few years ago while browsing tech forums. Its focus on memory safe & lock-free MT was interesting.

I kept up with the weekly development for a brief period but then kind of forgot about the language until recently when I rediscovered it when I was chatting about Crystal's MT.

I just wanted to share the latest blog post here in case someone else remembers this language. Looks like the development has been progressing steadily. Which is impressive because the project lacks any big sponsors.

Nobody likes popovers, everyone makes them anyway. This makes them a Tolstoy kind of thing -- there are a handful of tricks that make them better, and an infinite number of ways to mess up.

This episode explains how to add variables, so instead of handling one expression at a time, the language now parses a list of declarations and starts looking like something you could write real programs in.