3 ms·
Use cases are different, so I don't see any way to have a general "this is best" winner. Dynamically typed languages, for example, might always be popular with
by tyingq 6y ago
Use cases are different, so I don't see any way to have a general "this is best" winner.
Dynamically typed languages, for example, might always be popular with users that are highly technical, but not necessarily from a comp-sci background. Say you're a Unix admin, and have to automate a bunch of work. A strongly static typed language is going to be verbose and feel heavy to you. And you don't really care about performance, since the scripts can run in 1 second or 1 minute, and either gets the job done.
On the other side of that, if you're a developer on a largish project, a dynamically typed language might feel loose to you, complicate your unit tests, or drive hard to diagnose bugs. Or perhaps the performance trade-off isn't workable.
- hellofunk 6y ago> Dynamically typed languages, for example, might always be popular with technical, but not comp-sci type users. Some of the most hardcore "comp-sci" theorists I've ever encountered work only in Scheme, a dynamically typed language.
- tyingq 6y agoYes, and I'm sure there are Unix admins that love statically typed languages. They were examples, and not absolutes.
- hellofunk 6y ago> They were examples, and not absolutes. Well, to be fair, you did use the word "always" which makes things sound... absolute. > always be popular with users that are highly technical, but not necessarily from a comp-sci background
- tyingq 6y agoAlways be popular. The "popular" part makes it not absolute. And I feel like the statement is true. That demographic does tend to gravitate to dynamically typed languages. I edited the phrasing to make it more clear though. Apologies for anything that sounded overly authoritative. Just my opinion.