Re: [ANN] Clojure 1.8.0-RC2

Hello, Alex. Thank you for your work. Direct linking is a feature that we wait for a long. We need to obfuscate our code, so direct linking is really helps us. But I wonder, why there is keyword and symbols interning left in the static initalizer in the class: L1 { ldc "clojure.cor

[ANN] avi 0.1.7

Changes: - Rewritten normal mode (based on a state machine). This means that adding all the weird phases of a normal-mode command should be really easy (and all sorts of operators and motions should be coming down the pike!) - The "d" operator now works for all motions previously impl

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

I agree 100% that schema is a great tool, and solves some of the problems I still think the absence of (optional) types is a big missing piece in the Clojure story, because of the following reasons: 1. The ideal time to check types is at compile time - you want immediate feedback if you do somet

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

I think https://github.com/pjstadig/assertions is very useful to assert the values in development, and turn off in production without any penalty. Can't expect libraries to include this though. Shantanu On Tuesday, 1 December 2015 03:19:09 UTC+5:30, Jonathon McKitrick wrote: > > I've read the r

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

+1 to everything said so far. I also found that types are great for articulating a well-known, static set of structures, but almost all of the projects I worked in in a strongly and statically typed language (Java) involved living on the edge of typing _just_ the right level of abstraction - sp

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

I believe that working with maps is a lot like working with locals and function names...nothing will help you with bad naming. So don't do stuff like {:foo 42 :bar 33} when you can do stuff like {:min-age 42 :max-age 33}. Also stick with sane naming conventions. Don't do {:maxAge 42} in some places

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

Gary Trakhman wrote on Monday, November 30, 2015 at 2:26 PM: I'd like to try haskell, but I'm not sure types in general would provide enough benefit to be worth it for small projects and well-written/tested large ones. There’s always https://github.com/Frege/frege-lein-plugin and https://github.

Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

We used to have these things called specifications and documentation but we all know what happened to those :-/ Docstrings are ok but no substitute for really well done docs. Yes they were "hard" to keep in sync w code but clear, comprehensive and succinct technical writing is a lost art IMO.

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

I spend most of my time on application code, I think the tradeoffs are different when shipping public libraries. Obviously, I would prefer my libs to be more slow-moving, more well-documented, more generally useful and well-defined. I want my application code to be quick to change and develop fir

Re: Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

Tools like Schema, core.typed or just plain old docstrings are useful. Of course, the library write must provide these. Some libraries even roll their own documentation solution, eg. the very cool tools.analyzer spec . Thanks, Ambrose

Practical ways to deal with 'bag-of-properties' syndrome, AKA dynamic typing?

I've read the recent comments on 'the end of dynamic languages' and I'm curious what ways you have found for dealing with one of the issues I've heard mentioned frequently: when libraries (or functions in general) pass maps around as arguments or return values, how to go about finding out exact

ANN metrics-clojure 2.6.0 is released

metrics-clojure is a Clojure interface to the DropWizard Metrics library. Release notes: https://github.com/sjl/metrics-clojure/blob/master/ChangeLog.md#changes-between-250-and-260 -- MK http://github.com/michaelklishin http://twitter.com/michaelklishin -- You received this message because you