3 ms·
Listed without no further text on the Clojure's bad parts: "Dynamic typing". That's very very debatable, don't you think mr. Ward?
by talles 12y ago
Listed without no further text on the Clojure's bad parts: "Dynamic typing".
That's very very debatable, don't you think mr. Ward?
- jlward4th 12y agoDefinitely. Which is why I labelled that section as my opinions. :)
- talles 12y agoTouche :) I guess I just felt bad to see all those great bulleted itens with some nice phrasing around and then to see my dear Dynamic Typing there, alone, without any adjective. No love, no hate, simply emotionless "Bad" :(
- jlward4th 12y agoGood point. I should have put more details in there. I prefer static typing with good type inference because it allows me to have a compiler validate a lot of my code pre-runtime. Otherwise I'm left with tests and actually running all of the code to do that validation. The value of this for large code bases has been worth the tradeoffs in my experience. But since this is one of the most debated things in programming I don't expect to sway anyone. I'm happy to leave this as an item of "it depends" / personal preference.
- weavejester 12y agoClojure does have optional static typing via core.typed. It's still in active development, and the tooling around it is still rough around the edges, but it's a more sophisticated type system than Java's.