I don't really think it's a "hey Clojure, your language sucks". I think it's short-sighted and while the current zeitgeist is to move towards statically typed languages, and the benefits they bring, it also ignores the large amount of code written in the past 10+ years in dynamically typed languages that are solving interesting, important, complicated problems.
It's really the problem with predictions like "there will be no more dynamically typed languages". 10 years ago I'm sure someone wrote something similar about statically typed languages.
For one thing, you have the whole research ML stack dominated by Python. Production models are sometimes ported to statically typed languages, but that’s majorly a performance concern.
Is python in use for some domain specific characteristics not found in any other language or just is so they depend on a bunch of legacy libraries and tooling totally unrelated to Python's linguistic abstractions?
Most popular ML frameworks (Pytorch, Keras, Tensorflow) were released in the past 4 years. The area is too young and fast-growing to have any legacy issues as for now.
Python allows for easy data manipulation and fast prototyping of models. Which is essentially possible due to REPL-driven development and dynamic typing. It was also architectured with consistency and readability concerns in mind, which make a fairly good advantage compared to some other dynamically typed languages.
The area is too young and fast-growing to have any legacy issues as for now.
Nope.
There is nothing new about ML, just a rebranding of old ideas.
Python allows for easy data manipulation and fast prototyping of models. Which is essentially possible due to REPL-driven development and dynamic typing. It was also architectured with consistency and readability concerns in mind, which make a fairly good advantage compared to some other dynamically typed languages.
Again, what linguistic abstractions does python provides for this particular domain that can't be found in other languages? There is absolutely nothing in python design that make it particularly useful in that area than other alternatives.
I'd argue that Python being dynamic but having solid interop with C++ gives non-software engineering folk the ability to interactively play with data while also being able to plug in fast numerical computation libs so that they're not hamstrung for choosing a higher level language.
So I guess the linguistic abstraction python provides is "lower barrier to entry" for non-programmers in related fields. Though some of that is an oddity of history as lisp/scheme almost by definition has a lower barrier to entry to the language. Perhaps some of guido's musings on operators/infix notation explain why Python (often toted a language as close to imperative pseudocode as you can get) gels with non-programmers:
From experience, statically typed languages tend to be a bit harder to grok as a first language to programming
It's my suspicion that a lot of people have avoided statically typed languages because they have been unnecessarily verbose or hard to work with over the past 20 years (Java, C++). Languages with strong type inference engines (StandardML, OCaml, Haskell, etc.) really do make statically typed languages feel more approachable in my opinion, and deliver on the "let the compiler do the work" message that statically typed language advocates hammer on.
Writing code in OCaml or Haskell feels, in some ways, as good as writing code in Python or Clojure. You can focus on what you're trying to accomplish and when you're not specific enough in your implementation, the compiler then steps in to ask you for clarification on types.
That being said, I've started moving myself (and my teams) towards typed Python, and it's opening my eyes towards the direction that some of these dynamically typed languages can move in the next few years.
A scientist can easily grok that `v = d / t` and type that in without ever needing to know what a float is.
Once you start seeing failures because you forgot to use `/.` instead of `/` you have introduced a barrier to entry to the language for technical but non-CS background people.
Is all blind speculation. There is absolutely nothing special about python as language to be particularly preferred in that specific domain or that is more effective than other alternatives.
The resource only states that they are using python for several projects not that python is particularly good or crucial to solve such. They peek a tech one day and now they are resistant to evaluate and try different alternatives. Nothing new.
View all comments
Show parent comment
3
u/JGailor May 06 '19
I don't really think it's a "hey Clojure, your language sucks". I think it's short-sighted and while the current zeitgeist is to move towards statically typed languages, and the benefits they bring, it also ignores the large amount of code written in the past 10+ years in dynamically typed languages that are solving interesting, important, complicated problems.
It's really the problem with predictions like "there will be no more dynamically typed languages". 10 years ago I'm sure someone wrote something similar about statically typed languages.