5 ms·
Meh.... I think he's right that there's no good reason _not_ to use Python. But I think he overstates the case. Calling Python "compiled" doesn't seem right -
by jrochkind1 12y ago
Meh.... I think he's right that there's no good reason _not_ to use Python.
But I think he overstates the case.
Calling Python "compiled" doesn't seem right -- he's more right that this doesn't matter, there's no reason not to use something because it's "not compiled".
Calling Python's typing "strong typing", eh, really? He provide a link to a wikipedia article on typing in general, how about a link to anyone else making the case that Python should be considered 'strongly typed', for a particular definition of 'strongly typed'? I'm dubious that it would be any definition of 'strongly typed' that those who think they want it... want. Again, I think a better argument might be: So what, you don't need strong typing for success, because of a b and c.
And the concurrency discussions is just silly. Sure, you can do _all sorts_ of things without multi-core concurrency, you may not need it or even benefit from it, and scaling to multi-process can sometimes work just fine too. But there are also _all sorts_ of cases where you do really want multi-core parallelism, and Python really doesn't have it -- and trying to justify this as "makes it much easier to use OS threads" is just silly. I guess it makes it 'easier' in that it protects you from some but not all race conditions in fairly unpredictable ways -- but only by eliminating half the conceptual use cases for threads in the first place (still good for IO-bound work, no longer good for CPU-bound work).
I think there's a reasonable argument to be made that Python will work just fine for 'enterprise' work. There are also, surely, like for all languages/platforms, cases where it would be unsuitable. By overstating the case with some half-truths and confusions, he just sounds like a fanboy and does not help increase understanding or accurate decision-making -- or confidence in the Python community's understanding!
- wbkang 12y agoStrongly typed is pretty precisely defined and Python is certainly strongly typed.
- acbart 12y agoI agree that there are precise definitions of the phrase "strongly typed", but from my experience if you put 10 computer scientists in the same room, you'll hear 3 different definitions of what it means.
- mdonohue 12y agoDefined as what? The Wikipedia article says the definition is unclear: Languages are often colloquially referred to as "strongly typed" or "weakly typed". In fact, there is no universally accepted definition of what these terms mean. In general, there are more precise terms to represent the differences between type systems that lead people to call them "strong" or "weak".
- jammycakes 12y agoTrue, but the complaint that people tend to come up with is that Python is not statically typed. What they are looking for here are things such as clear, accurate and reliable IntelliSense, and the ability to right click on a method definition, select "Rename", and be assured that the refactoring will be propagated through to every usage throughout your codebase with no false positives and no false negatives.
- crdoconnor 12y agoStrong typing saves you from a whole universe of obscure bugs at no extra cost. Static typing would be nice, but not in a Java or C# or C++ way. The extra verbosity makes it not worth the benefits. Sure, you get slightly more reliable intellisense, but at the expense of a program that's 15-20% longer.
- dgemm 12y ago>>> 1 + "0" Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: unsupported operand type(s) for +: 'int' and 'str' This is what strong typing refers to.
- reinhardt 12y agoIt's not so clearcut. If this is evidence Python is strongly typed, would the following be evidence to the contrary? In [1]: 1 + 2.5 Out[1]: 3.5 In [2]: "foo" * 3 Out[2]: 'foofoofoo' In [3]: [1, 2] * 3 Out[3]: [1, 2, 1, 2, 1, 2]
- agentultra 12y agoIt's not contrary, it's just convenience. One of the weaknesses in Python (if you can call it that) is that everything is an "object." The classes implementing string, list, and integer simply have methods that respond to those operators and rhs types. In [1]: "foo" + 3 --------------------------------------------------------------------------- TypeError Traceback (most recent call last) <ipython-input-1-21582e79f06e> in <module>() ----> 1 "foo" + 3 TypeError: cannot concatenate 'str' and 'int' objects That's because the "special" method "__add__" implemented by the string class will raise TypeError if it gets any object that isn't an instance of a subclass of string. In a way it is kind of funny to call it, "strongly typed," but it does work. Maybe it should be called, "instancely-typed."
- jrochkind1 12y agoOkay, with this definition of 'strongly typed', can anyone come up with an example language that _isn't_ strongly typed? It seems to make 'strongly typed' pretty meaningless, and this definition is probably _not_ what anyone who says they want a "strongly typed" langauge is using, so it hardly counters them to say that python is "strongly typed" under another definition, it's just confusing them with semantics. (Of course, the people who say they want 'strongly typed' may have no idea what they're actually talking about, but wouldn't it be better to educate them then to take advantage of their ignorance to push your pro-python agenda?)
- hyperpape 12y agoI can think of three ways of thinking about the term "strongly typed" once you realize it doesn't mean "statically typed". 1) It's meaningless--it's almost impossible to produce a real ranking of languages on the strength of their types. 2) These dynamic languages are all unityped because they're not statically typed. The fact that runtime tags won't allow certain operations to succeed has nothing to do with types. 3) Strongly typed is a rough and ready way of saying you don't do many implicit conversions. I sympathize with (1). (2) is accurate, but really a terminological point. There's clearly a phenomenon to talk about, even if "typed" is the wrong word. I also sympathize with (3). Python does far fewer implicit conversions than PHP, JavaScript or Perl. It even doesn't do at least one that Java does. So people often say Python is strongly, but dynamically typed. It's a real aspect of the language that you can view as a plus or minus.
- agentultra 12y agoThere are plenty of options for concurrent and parallel operations in Python[0]. It is heavily used in data analytics and the scientific programming communities. Though it does often need a little help from C to take advantage of SMP hardware. [0] https://wiki.python.org/moin/ParallelProcessing https://wiki.python.org/moin/ParallelProcessing
- eliben 12y agoBut Python is strongly typed. A language can be dynamically typed, and strongly typed - no problem with that. More details in http://eli.thegreenplace.net/2006/11/25/a-taxonomy-of-typing-systems http://eli.thegreenplace.net/2006/11/25/a-taxonomy-of-typing...
- slantedview 12y agoPython is compiled in the sense that it produces bytecode, but in being so it lacks the benefits of other compiled languages such as thorough compile time error checking. I've found that this is sometimes why people don't even notice the compiler.
- slantedview 12y ago[OS threads are] "no longer good for CPU-bound work" "Python will work just fine for 'enterprise' work" These two statements conflict.