Hacker News Reader

Comment by sacado2 | Hacker News Reader

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.

View on HN

    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.

>That choosing a programming language is not easy is public knowledge that the readers already know. At least if they are programmers.

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/++}

Please do not use code formatting for quotations. Use the old de facto standard of a “> ” prefix.

    Please do not use code formatting for quotations.

Why not? I think it looks pretty good.

Code formatting is difficult to read on mobile because the text doesn't wrap properly. You end up having to scroll horizontally to read it all.

FWIW, not only on mobile.

> What code do you want to show about these aspects?

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).

> This article deals with "big picture" aspects

Read: It's a rant and/or PR.

Reply on news.ycombinator.com