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?
Code that shows these aspects. What broke in Java because of language changes and why. How handling circular dependencies in one language makes code uglier then in the other. Examples of the specs. You did the same with you "I love
programming language" opening.
That I love programming languages and to reason about them is an information about myself that the reader does not know in advance. That choosing a programming language is not easy is public knowledge that the readers already know. At least if they are programmers.That is the point of my post. Asking who the target audience is. And how it is different from myself.
Please do not use code formatting for quotations.
Why not? I think it looks pretty good.Well that bit is certainly not true; passing by certain communities and you’ll be let known theres only one good answer: {lisp,c#,haskell,rust,js,c/++}
If not code, how do you prove these assertions? How do you measure them?
> It's an introduction.
Inappropriate for an analytical argument. Common for infotainment (entertainment masquerading as information).
Read: It's a rant and/or PR.
- The article focuses on the properties of codebases, not individual code snippets. While it would be very valuable to do compare the properties of entire codebases, that is demanding on both the reader and the author.
- Opening the article with a statement like “Choosing a programming language is never easy...” is an acknowledgement of the fact that he is not claiming Go is unequivocally the best in all scenarios. The author is signaling that he is a reasonable person, and while that may seem like fluff it is a necessary component of communicating with a wide audience.
Probably there are languages that have a really expressive syntax that solve problems also in a scalable manner. For instance Python with its list comprehension that are a real code and time saver for software that does a lot with lists. (No coincidence it's so popular with ML.)
A list is much too slow because:
- Not contiguous - No SIMD vectorization - No parallel processing
Lists are mostly used for list of containers (for example storing the arrays inputs of a function)
So I clicked on this one. Started skimming through it, looking for code. Found none. Came back here to share my disappointment.
I'm always confused about articles that talk about code and have little code to show. Are there programmers who enjoy reading them? Or are these articles made for non-programmers?
Another thing that always throws me off is fluff. The article starts with "Choosing a programming language isn’t easy.". What does this add to the article? It immediately makes me think the author stuffed this article for no reason. So I have to skim even faster to not being cheated of my time. Is there anybody out there who thinks having the article prefixed with "Choosing a programming language isn’t easy." makes it more valuable?