[chrisbuchholz]

I feel you misunderstood the article.

To my understanding, his point is that we need database persistence, automated RESTful APIs, triggers and responses and better ways to do UI layout, but what we got was Swift which doesn't address any of these things. The things we actually need.

So we end up with a new language which we have to spend time mastering, and when we are done doing that, we still need to fix those problems we had before we got Swift, so what is the point? Why do we need Swift?

That's how I read the article anyways.

[pohl]

That makes it sound as if a modern language sans the baggage of C was not needed. It was.

[mpweiher]

Hmmm...to me it makes it sound like a modern language without the baggage of C was and is needed, but Swift is not that language.

[pohl]

[language] does not solve [problems not solved by languages].

Film at 11.

[mpweiher]

Welcome to Tautology Club! If Tautology Club is the sort of thing you like, you will like Tautology Club. Alternatively, you will find that you like Tautology Club if that is the sort of thing you like.

In other news, you might have checked some of the other posts here that explain why some of these problems are, or at the very least can be language problems, before letting loose the snark.

For example https://news.ycombinator.com/item?id=8377860

[pohl]

"My smartphone didn't palliate my hemmoroids" is no tautology.

[mpweiher]

But "[language does not solve] [problems not solved by languages]" is.

[nbevans]

Your example is a link to yourself and two footnotes that link to articles written by yourself. Are you a joker?