News for hackers. Stuff that matters.
Re:Is Typed Clojure worth the trouble? by dmead on Monday June 22, 2015 @09:35AM (#9758156)
that is static typing FUD. if it takes you a few days or weeks to learn to use the type checker and it saves you from expensive runtime errors later, then whats the problem?
Re:Is Typed Clojure worth the trouble? by chimprich on Monday June 22, 2015 @09:54AM (#9758295)
The problem is the overhead in adding typing. The time taken to learn the type system is a one-off but static typing has running costs in slowing down development, discouraging exploratory programming, extra cognitive load in reasoning about the type system, and "false positives" in disallowing otherwise correct programs. It does nearly eliminate a class of bugs - this is wonderful, but the bugs it does eliminate tend to be ones that are fairly obvious to find.
Re:Is Typed Clojure worth the trouble? by cantankerous on Monday June 22, 2015 @10:45AM (#9758650)
What about the cognitive load of chasing down things like null reference errors, which in some strongly typed languages don't even exist? And no, they're not always fairly obvious to find, especially when you're fixing somebody else's code.
Re:Is Typed Clojure worth the trouble? by Skinney on Monday June 22, 2015 @11:01AM (#9758778)
The keyword being "some". I've rarely had any problems with null/nil reference errors in Clojure, because nil is treated both as false and as the empty list, so most of the time you do the right thing in case of nil. You also don't call methods on objects, but send values to functions, which eliminates a large source of NPE right there.

Clojure is also a compiled language. So things like calling a function with the wrong arity, and calling a variable/function that doesn't exist are caught at compile time. This is, by far, the most common runtime bugs I've experienced in Javascript and Python, due to spelling mistakes in and out of refactoring.

Re:Is Typed Clojure worth the trouble? by JadeNB on Monday June 22, 2015 @12:09PM (#9759279)
> most of the time you do the right thing in case of nil

I can't remember where, but I was just reading something yesterday to the effect that a solution that works most of the time is worse than a 'solution' that never works: at least you'll notice the latter quickly, whereas you might not notice the former until it's buried so deep in your code that you've forgotten the hidden assumptions it involves.

Re:Is Typed Clojure worth the trouble? by sebastianconcpt on Tuesday June 23, 2015 @09:15PM (#9768965)
Well can't be taken seriously. Real life works most of the time. Only theoretical thought experiments could work all the time. Can you show me a clock that worked more than 10K years? They are still trying to invent one (and we're not having it yet)
Re:Is Typed Clojure worth the trouble? by JadeNB on Wednesday June 24, 2015 @01:48AM (#9769871)
I agree, and Skinney made a similar point yesterday (https://news.ycombinator.com/item?id=9759571). However, I think that an excessively literal reading misses the spirit of the quote (as I (probably mis)remember it). I elaborated in my reply https://news.ycombinator.com/item?id=9760336 .

Incidentally, your question about the 10K-year clock (to which I think it is impossible to give an answer today even if one exists today, since I think clockmaking has not yet been practiced for 10K years!) reminds me of anecdote #3 in http://www.netfunny.com/rhf/jokes/91q3/oldanecd.html .

Re:Is Typed Clojure worth the trouble? by Skinney on Monday June 22, 2015 @12:50PM (#9759571)
By that logic, most object oriented languages like Java, C# and C++ are fundamentally flawed as calling a method only works most of the time.

Besides, code in general only work most of the time. Static typing does not protect you from bugs.

Re:Is Typed Clojure worth the trouble? by the_af on Monday June 22, 2015 @02:32PM (#9760268)
> Static typing does not protect you from bugs.

But it does. It doesn't protect you from all bugs, but nobody claimed it did.

Re:Is Typed Clojure worth the trouble? by Skinney on Monday June 22, 2015 @03:18PM (#9760582)
True, should have specified what I meant. The thing is, static typing doesn't necessarily protect you from more bugs than a dynamic language. For instance, Clojure is less prone to NPEs because you don't call methods on objects, and because a lot of your program manipulates datastructures, and nil is treated as an empty datastructure. Of course, a language like Rust, which doesn't have null, does protect against NPEs. It's all relative.
Re:Is Typed Clojure worth the trouble? by Skinney on Tuesday June 23, 2015 @02:00AM (#9762862)
Reading this again make me realize that I'm wrong. Static typing will safeguard you against certain types of bugs that a dynamic language don't. The point I was trying to make was that a static language doesn't necessarily protect you against a certain type of bug, which you may rarely experience in a dynamic language.
Re:Is Typed Clojure worth the trouble? by JadeNB on Monday June 22, 2015 @02:42PM (#9760336)
I didn't call anything flawed, fundamentally or otherwise; but I take your point.

I think that there is an important distinction between 'almost-there' solutions.

Suppose that you have a piece of code that is specified to work in a certain way. Because code, and the hardware on which it runs, is made (at least indirectly) by humans, it will fail under some conditions; it only satisfies its specification. I think that we are all comfortable with this kind of "works most of the time".

By contrast, consider 'smart' products—for example, the auto-complete on your phone. This also, after a bit of training, works most of the time, and can make some brilliant inferences. However, I think that most people can agree that the "most of the time" for auto-completion is qualitatively different from the "most of the time" for specified software: it is reasonable to rely on the latter, but not, or at least not nearly as much, on the former (http://www.damnyouautocorrect.com).

Re:Is Typed Clojure worth the trouble? by JadeNB on Monday June 22, 2015 @10:29PM (#9762316)
Oops, I an important word out:

> Because code, and the hardware on which it runs, is made (at least indirectly) by humans, it will fail under some conditions; it only satisfies its specification.

This sentence was supposed to end "it only satisfies its specification some of the time." I was not going for Knuth-ian irony about proving vs testing (https://en.wikiquote.org/wiki/Donald_Knuth#Sourced).

Re:Is Typed Clojure worth the trouble? by Skinney on Monday June 22, 2015 @03:22PM (#9760604)
I know you didn't, but if you have a language have a core semantic that only works "most of time," and "most of the time" is worse than "never," then you have a language that is worse than not having a language at all, which means that it is fundamentally flawed. Yes, I probably did enjoy my logic courses at the university too much.
Re:Is Typed Clojure worth the trouble? by outworlder on Monday June 22, 2015 @02:58PM (#9760442)
But they are. As in, they fail to handle the null case properly.
Re:Is Typed Clojure worth the trouble? by erdeszt on Monday June 22, 2015 @10:38AM (#9758600)
Do you have any evidence to prove this? I've read a few papers that disagree with your opinions...
Re:Is Typed Clojure worth the trouble? by yogthos on Monday June 22, 2015 @04:40PM (#9761036)
That's the thing though, there are lots of papers that support both sides of the argument out there. For example, take this http://macbeth.cs.ucdavis.edu/lang_study.pdf large scale study of GitHub projects. In the study, Clojure is right up there for correctness with hardcore statically typed languages like Haskell.

There's plenty of software written in both typing disciplines in the wild. Yet, nobody managed to conclusively demonstrate that software written in statically typed languages is produced faster and with less overall defects or that it has lower maintenance cost. The very fact that we're still having these debates says volumes in my opinion.

Majority of arguments regarding benefits of static typing appear to be rooted squarely in anecdotal evidence.

Re:Is Typed Clojure worth the trouble? by erdeszt on Tuesday June 23, 2015 @05:31PM (#9767972)
I agree with this comment of yours but the first one has a few overstatements and that prompted my reply. Also if you feel that strong types slow you down I suggest you try some gradually typed language where you can start out without types, do the exploring and add the types when you know what you want. I've tried this in TypeScript and it was a fairly good experience.
Re:Is Typed Clojure worth the trouble? by chimprich on Wednesday June 24, 2015 @07:38AM (#9770897)
It wasn't my intention to overstate the benefits of dynamic typing, just to point out that static typing isn't just a free lunch. I think yogthos sums up the situation pretty well.
Re:Is Typed Clojure worth the trouble? by yogthos on Friday June 26, 2015 @10:43PM (#9788891)
Clojure also takes this approach with core.typed as well https://frenchy64.github.io/2015/06/19/gradual-typing.html

I personally haven't found a place where this is necessary yet, but who knows what might happen in the future. :)

Re:Is Typed Clojure worth the trouble? by Skinney on Monday June 22, 2015 @11:08AM (#9758829)
Probably based on personal experience. For me, whenever I start a project from scratch I usually start with the most dynamic environment I can find, then hack away until I have something that resembles the functionality I need, before locking it down. In the beginning of a project I don't care if something is 100% correct, I just want to see what my idea looks like, and what I actually need. I don't want to deal with synchronizing my types with a database schema, or make sure the JSON I send to the server satisfy the type system. I really don't care about interfaces or abstract classes or whatnot, I just want to retrieve the value I know to be in the object I got. Then, when I have a working'ish prototype, I can start nailing it down with types, assertions, tests and contracts.

Of course, people are different. Some people do all of this on paper before writing a single line of code. Others plan by making types and interfaces, then proceed to implement those. I just like making prototypes.

Re:Is Typed Clojure worth the trouble? by dllthomas on Sunday June 28, 2015 @04:05PM (#9794865)
"Some people do all of this on paper before writing a single line of code. Others plan by making types and interfaces, then proceed to implement those. I just like making prototypes."

Of these, I sound the most like you - think just a little, then sit down and start coding to get a feel for things.

Yet I find a good type system essential (or at least conspicuously missing when I write Python). There is a notion that, if one has static type checking, one has to get the types right before writing code. There's no reason that has to be the case. Get a sketch, start writing code, refine your sketch. With type inference, the sketch can even be somewhat incomplete and still help me find where my assumptions clash.

Re:Is Typed Clojure worth the trouble? by jbeja on Monday June 22, 2015 @05:06PM (#9761194)
Don't know why people are downvoting you, your approach is perfectly valid.
Re:Is Typed Clojure worth the trouble? by sebastianconcpt on Tuesday June 23, 2015 @09:12PM (#9768951)
That's a really important point. Lots of time sunken in confirming the compiler that could have been used in exploratory programming. Humans are fundamentally explorers not conformists.

Nice duality you exposed right there!

Re:Is Typed Clojure worth the trouble? by jstuxx on Tuesday June 23, 2015 @11:54AM (#9765472)
More like its FKF (Fear of the Known and Familiar). Most (if not all) programmers have experience with static typing and most of those experiences were not pleasant hence why a lot of people don't like static typing. People start to hate it even more when it gets shoved down their throats i.e. "You must absolutely must use static typing otherwise your software is unreliable and buggy".

Static typing requires discipline, it is no magic cure for bugs which will automatically make your programs correct, same way forcing everything to be in class in Java does not automatically make readable, modular and reusable code, its just restrictive and annoying.

The disciplines required for static typing to be effective can be employed in dynamic typing however merely having a static type system does not mean the discipline will be developed. In order for a static type system to not be restrictive (like Java's or C++'s) it has to be flexible i.e. it has allow types of varying degrees of vagueness. If I am an inexperienced programmer with no discipline nothing stops me from picking the vaguest type possible and making a complete mess. Type errors do not prevent all bugs, in-fact they prevent only a minimal subset of bugs, most bugs are related to logic errors involving an ill-thought out algorithm or data errors related to invalid data provided by the user which often can only be caught by dynamic type systems.

Re:Is Typed Clojure worth the trouble? by dllthomas on Saturday June 27, 2015 @03:22PM (#9791246)
There are too many things wrong with this comment for me to address any subset of them coherently...

I'll leave it at responding to the bit I do agree with, which is that many people have had poor experiences with poor checkers for poor type systems.

Re:Is Typed Clojure worth the trouble? by sebastianconcpt on Tuesday June 23, 2015 @09:09PM (#9768941)
That's a good observation