This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (43)
- # beginners (11)
- # boot (141)
- # cider (48)
- # clojure (82)
- # clojure-canada (1)
- # clojure-dev (1)
- # clojure-norway (20)
- # clojure-russia (6)
- # clojure-uk (12)
- # clojurescript (268)
- # datomic (14)
- # editors (5)
- # euroclojure (5)
- # jobs (2)
- # ldnclj (109)
- # off-topic (7)
- # om (6)
- # other-lisps (3)
- # re-frame (13)
- # reagent (3)
- # sim-testing (5)
- # sydney (1)
I think we should stop asking programming questions here and post them on Stackoverflow instead.
i personally don’t like asking questions in stack overflow, mostly because I don’t like the ux.
Hello! It's nice to be here. I am Meekan, your team's scheduling assistant.
My scheduling brain can match everyone's calendars and offer the best times to meet.
To connect your calendar, say
meekan connect me, or
meekan connect @channel
To start a new meeting, just ask me. Try
meekan we want to meet for lunch next week
meekan help for a list of everything I can do.
Ask me to start a new meeting:`meekan we want to meet for lunch next week`
Other commands available:
For a full list see: http://tiny.cc/meekanhelp
just got bit by a 4th-party library written in Scala 2.9. No updates in 3 years. Can’t compile under 2.10. Between the sbt tire fire and binary compatibility, I may finally be over my residual Scala appreciation. Lift (and CSS selector transforms especially) are nifty, but the rest of it is taking years off my life.
Yeah... I'm doing Clojure/ClojureScript... and Lift plays well with both: https://github.com/dpp/devoxx_pl_2015_scala_clojure
Ah! I knew you’d done a presentation on the combo recently and was failing at google-fu.
Also... I feel your pain about the Scala version fragility issue... I've ranted about it recently: http://blog.goodstuff.im/scala_version_rant
I can either externalize the offending 3rd-party code into a “micro”-service to keep my (still-trivial) Lift app on 2.10, or I can rewrite the app into clojure[script] and keep it in the same JVM. Or a combination. 😉
There are positive reasons to split it, and positive reasons to rewrite it, as well as costs both ways. I just was hoping to defer some of the questions longer.
Scala is still having binary compatibility issues on minor versions? https://clojurians.slack.com/archives/general/p1436475048003868
The pain of 2.7 -> 2.8 still haunts me and was instrumental in us moving from Scala to Clojure 😞
Hmm…. talk by Odersky in March — he says in passing that Clojure solves the problem by shipping source, not binary.
i wonder if fixing the long-standing transitive-compilation bug would affect this argument
Even with AOT’d code, Clojure has often been better than Scala’s record: during the 2.7 -> 2.8 migration, pretty much every single milestone build during the prerelease process broke your entire dev tool chain and you couldn’t update anything until all of the compiler + build tool + testing lib + other libs were all updated to that exact same milestone build. It was hell...
and I love a lot of languages but the only redeeming quality it has is its easier for java hardheads to use is not enough to keep a language alive
Despite my experiences, I still like Scala — the language — and I think it’s an impressive achievement. I think it’s made it possible for several other, newer languages to push the envelope regarding FP.
I had some experiences on a Scala project with implicits that were reminiscent of debugging ruby code