Also, this article sounds like it's not entirely serious?
8 Considerations on Choosing a Programming Language
11–20 of 44 posts
Re: 8 Considerations on Choosing a Programming Language
#12Re: 8 Considerations on Choosing a Programming Language
#13Stopped reading after "strong typing is better than weak typing". Well, it is not. He/she rules out perfectly valid programming languages because of this personal opinion nowhere near a fact ( http://stackoverflow.com/questions/125367/dynamic-type-langu... ). In fact, it directly contradicts his/her second point. I understand the author wants to drift it towards Scala, but make an effort and choose the right argument…
Well, it is my opinion in fact, and that's why it says a "%100 opinionated view" in the subtitle.
There are many other persons with the same opinion: http://stackoverflow.com/a/43072/731933 http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about... http://www.teamten.com/lawrence/writings/java-for-everything...
If we were to discuss everything in this article, starting with dynamic vs static typing, we'd still be here 3 months from now :). Which is why it is opinionated.
Re: 8 Considerations on Choosing a Programming Language
#14I understand the article comes from scala-academy, but I think by offering a more objective viewpoint of different languages and the standards they impose, scala can show what niche they provide. I don't believe it is the niche of "Everyone is hiring a Scala programmer", but it should be (quoted from the article) "...implicits, underscore notation, flexible imports, multiple classes per file, multi-line strings, pattern matching, traits with variables, etc." If this article was about these points, with relations to other languages, that could be some quality content!
For everything else, either the article misrepresented other languages, or simply remained apathetic to their application.
Re: 8 Considerations on Choosing a Programming Language
#15Stopped reading after "strong typing is better than weak typing". Well, it is not. He/she rules out perfectly valid programming languages because of this personal opinion nowhere near a fact ( http://stackoverflow.com/questions/125367/dynamic-type-langu... ). In fact, it directly contradicts his/her second point. I understand the author wants to drift it towards Scala, but make an effort and choose the right argument…
I'm the author. Well, it is my opinion in fact, and that's why it says a "%100 opinionated view" in the subtitle. There are many other persons with the same opinion: http://stackoverflow.com/a/43072/731933 http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about... http://www.teamten.com/lawrence/writings/java-for-everything... If we were to discuss everything in this article, starting with dynamic vs static typi…
Re: 8 Considerations on Choosing a Programming Language
#16Stopped reading after "strong typing is better than weak typing". Well, it is not. He/she rules out perfectly valid programming languages because of this personal opinion nowhere near a fact ( http://stackoverflow.com/questions/125367/dynamic-type-langu... ). In fact, it directly contradicts his/her second point. I understand the author wants to drift it towards Scala, but make an effort and choose the right argument…
I'm the author. Well, it is my opinion in fact, and that's why it says a "%100 opinionated view" in the subtitle. There are many other persons with the same opinion: http://stackoverflow.com/a/43072/731933 http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about... http://www.teamten.com/lawrence/writings/java-for-everything... If we were to discuss everything in this article, starting with dynamic vs static typi…
Re: 8 Considerations on Choosing a Programming Language
#17Stopped reading after "strong typing is better than weak typing". Well, it is not. He/she rules out perfectly valid programming languages because of this personal opinion nowhere near a fact ( http://stackoverflow.com/questions/125367/dynamic-type-langu... ). In fact, it directly contradicts his/her second point. I understand the author wants to drift it towards Scala, but make an effort and choose the right argument…
Only in situations where other effects outweigh the fact that compile-time errors are much less bad than run-time errors.
Re: 8 Considerations on Choosing a Programming Language
#18Earlier quoted context omitted.
I'm the author. Well, it is my opinion in fact, and that's why it says a "%100 opinionated view" in the subtitle. There are many other persons with the same opinion: http://stackoverflow.com/a/43072/731933 http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about... http://www.teamten.com/lawrence/writings/java-for-everything... If we were to discuss everything in this article, starting with dynamic vs static typi…
You may want to move Delphi out of the list of dynamically typed languages. It is just as strongly typed as C# or Java.
Re: 8 Considerations on Choosing a Programming Language
#19If I could downvote articles, I would have downvoted this one. It's like an upbrand, long-form youtube comment.
Re: 8 Considerations on Choosing a Programming Language
#20Stopped reading after "strong typing is better than weak typing". Well, it is not. He/she rules out perfectly valid programming languages because of this personal opinion nowhere near a fact ( http://stackoverflow.com/questions/125367/dynamic-type-langu... ). In fact, it directly contradicts his/her second point. I understand the author wants to drift it towards Scala, but make an effort and choose the right argument…
I'm the author. Well, it is my opinion in fact, and that's why it says a "%100 opinionated view" in the subtitle. There are many other persons with the same opinion: http://stackoverflow.com/a/43072/731933 http://blog.jooq.org/2014/12/11/the-inconvenient-truth-about... http://www.teamten.com/lawrence/writings/java-for-everything... If we were to discuss everything in this article, starting with dynamic vs static typi…
At the very least you should address the implications of strong vs. weak typing, and you should probably address the strength and nature of the type systems, also. After all, saying that both C and Haskell are statically largely misses the point.