Software developers' skills are mostly fungible– supply meets demand. I've been happily employed (and regularly solicited) as a Clojure developer for over 8 years. There's no shortage of Clojure dev positions for…
Sometimes that backfires. - Clojure dev
Yes, very early in Clojure's life and only after testing the change across several popular libraries.
Benchmarks are easily abused, misused, and misinterpreted. E.g., benchmarks looking at some very specific aspect of query performance being extrapolated to more complex/real-world queries. Also trade-offs are rarely…
Additionally there are safer, usually reasonable, ways to deal with what would otherwise be breaking changes. Give the changed functionality a different name, create a new namespace/module without the removed…
reference count referenceing co refer untingrefing
neat!
Software developers' skills are mostly fungible– supply meets demand. I've been happily employed (and regularly solicited) as a Clojure developer for over 8 years. There's no shortage of Clojure dev positions for…
Sometimes that backfires. - Clojure dev
Yes, very early in Clojure's life and only after testing the change across several popular libraries.
Benchmarks are easily abused, misused, and misinterpreted. E.g., benchmarks looking at some very specific aspect of query performance being extrapolated to more complex/real-world queries. Also trade-offs are rarely…
Additionally there are safer, usually reasonable, ways to deal with what would otherwise be breaking changes. Give the changed functionality a different name, create a new namespace/module without the removed…
reference count referenceing co refer untingrefing
neat!