This article deals with "big picture" aspects, not specific syntactic details, so there is no reason for it to include code.
Backward compatibility, compilation speed, circular dependencies, small vs big specs, etc. What code do you want to show about these aspects?
> The article starts with "Choosing a programming language isn’t easy.". What does this add to the article?
It's an introduction. It's a very common writing technique. You don't start with the core content of the article, you start with a paragraph or a sentence about why you wrote the article in the first place. You did the same with you "I love programming language" opening.
Backward compatibility, compilation speed, circular dependencies, small vs big specs, etc. What code do you want to show about these aspects?
> The article starts with "Choosing a programming language isn’t easy.". What does this add to the article?
It's an introduction. It's a very common writing technique. You don't start with the core content of the article, you start with a paragraph or a sentence about why you wrote the article in the first place. You did the same with you "I love programming language" opening.