3 ms·
I'll bet he starts to care if floating point arithmetic introduces errors into his results. You can only push off the complexity for so long if you want to do
by emodendroket 9y ago
I'll bet he starts to care if floating point arithmetic introduces errors into his results. You can only push off the complexity for so long if you want to do things that aren't trivial.
- Turing_Machine 9y agoCan you think of a (non-contrived) example where automatic promotion to float is going to cause a non-trivial error when computing (say) a household budget? "You can only push off the complexity for so long if you want to do things that aren't trivial." There are a lot of things that aren't "trivial" that nonetheless don't require a totalitarian type system.
- emodendroket 9y agoIsn't the biggest non-programmer audience who has any interest in writing Python scripts scientists? I don't think it's totally contrived to imagine that floating-point precision is an issue in such cases.
- sametmax 9y agoFun fact: half of the professional programmers I met in my life don't even try to do anything for floating point precision issues. You are living in your bubble. The bubble of people who knows what they are doing. Get out, you'll be surprise how much amateurish the world is. Yet it runs.
- emodendroket 9y agoYes, everything looks like it works, but occasionally it's completely wrong. I don't think just chugging along is desirable in all circumstances. But even if I accept your premise, that just says to me that Python is a good choice for people who don't really know how to program and don't care to learn too much.
- KirinDave 9y agoI'm really not a fan of this argument. No one is arguing for a banishment of the concept of a competency PMF. We're just saying, "If you use these newer techniques and tools and patterns, you get more bang for your buck." The common response is, "But then I have to learn something new." But this is the curse of technology, and pretty much inevitable. Some learning needs to occur because tech changes so fast.
- Turing_Machine 9y ago"If you use these newer techniques and tools and patterns, you get more bang for your buck." But you don't, necessarily. Dealing with type wankery takes time. And no, it has nothing to do with "learning something new". Languages that tout "type safety" have been around since at least Pascal (47 years old)... arguably even before that, with some of the Algol variants. Yet they've never made it to mainstream acceptance. It's not even about hype -- Pascal was pushed HARD, by just about every university. Where is it now? Turbo Pascal had a small degree of success, but that's only because it chucked a lot of real Pascal's rigidity out the window.
- KirinDave 9y agoSo... Can you clarify this? "Pascal is no longer popular. Pascal had a static type system. Therefore, static typing has failed?" If so, I counter: the last 3 years have been a series of breakthroughs both in terms of technology and social acceptance of typed programming. TypeScript is the rapidly growing language, Haskell's never been more boring to use, Scala's edging out Clojure even though it has very fragmented community leadership. C++ has adopted a lot of powerful new features and you're seeing functional programmers speaking at C++ conferences because the folks there can use it. Java has more capable and composable lambdas than Python. Systems not using these techniques are plagued by security flaws, while those that are work on stabilizing performance under various workloads. It's never been a better time to be using a strong, static type system..
- Turing_Machine 9y ago"Can you clarify this? "Pascal is no longer popular. Pascal had a static type system. Therefore, static typing has failed?"" I would make it "Pascal was never popular", but yes. "If so, I counter: the last 3 years have been a series of breakthroughs both in terms of technology and social acceptance of typed programming." This isn't the first rodeo for many of us. "Compile-type static type checking will solve all of our problems" is an idea that's come around repeatedly. Outside of a few niche applications, it never works, or even catches. As for the supposed booming popularity of TypesScript... dude, TypeScript doesn't even make the top 30 on GitHub. It's less popular than assembly language and Visual Basic.
- Turing_Machine 9y agoFloating point precision isn't even a problem for most scientists, at least not the ones dealing with real-world data. It's pretty rare to have measurements that are accurate to more than a few decimal places.
- lmm 9y ago> Can you think of a (non-contrived) example where automatic promotion to float is going to cause a non-trivial error when computing (say) a household budget? Having your share of holiday costs come out as NaN is fiddlier than getting an exception at the point where you actually divided by zero.
- Turing_Machine 9y agoBoth of those are runtime errors, though. The "type safe" guys like to pretend that their approach can catch all that stuff at compile time. It does catch a certain class of error, but at the cost of making the code take much longer to write. That doesn't work in a world where your competitor is iterating five times while you're still building the first one. Excellent way to get your milkshake drunk, that.
- lmm 9y ago> Both of those are runtime errors, though. Sure, the point is that using integer arithmetic for integer calculations gets you better error reporting that saves you time when tracking odwn other bugs. > The "type safe" guys like to pretend that their approach can catch all that stuff at compile time. It does catch a certain class of error, but at the cost of making the code take much longer to write. That doesn't work in a world where your competitor is iterating five times while you're still building the first one. My experience is that I can iterate a lot faster if the compiler's able to help me catch errors faster. It doesn't slow down writing the code; almost anything I'd write in say Python translates directly into the same Scala. (I guess the language pushes me into defining my data structures a little more explicitly, but that's something I'd want to do in Python anyway if only for documentation reasons).
- emodendroket 9y agoDefine "much longer to write." I don't think that claim is true.
- KirinDave 9y agoYes, we had non-trivial floating point errors in Level that appeared after multiple divide operations in an early version of the product. We stopped using it.