Re: Clojure in Geography meeting #1
The date of Will Cohen's meeting is set: Sat, Oct 3rd, 13:00-15:00 UTC. Please register to the meeting: https://twitter.com/scicloj/status/1305227676731543555 On Friday, 11 September 2020 at 18:45:22 UTC+3 Daniel Slutsky wrote: > We are planning a couple of meetings about Clojure in Geography. > > On the first meeting, we will meet Will Cohen, who is an urban planner and > the author of several Clojure libraries for geospatial analysis. > > https://github.com/willcohen > > Will will give an overview of the state of the geospatial ecosystem for > Clojure/Java in 2020. > > Please mark your preferences. > > https://twitter.com/scicloj/status/1304443223834849290 > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/12c1d62d-a3b2-46e3-ac0a-5d822bf15101n%40googlegroups.com.
Re: Truly, we live in the garden of edn
I can't comment on the whole crazy world of JSON, but it's a shame to think of all the coal-fired watts spent unnecessarily parsing UUIDs. If all you need is a string, there is no dishonor in letting it be a string. > I was made to wonder how the rest of the world lives! > > P.S. Also, never thinking about commas > > P.P.S. Also, sets and keywords and ints and extensibility and characters > and symbols and thank you very much! (: > P.S., Yes! Yes again!! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/76532578-f0f5-4c3c-899d-5771dbf15655o%40googlegroups.com.
Re: Rationale behind github.com/cljctools project
I especially like the "bigger aspirations" - https://github.com/cljctools/readme#bigger-aspirations And your summary of relevant strengths of Clojure. On Sunday, August 30, 2020 at 2:42:25 AM UTC-4, Sergei Udris wrote: > > Thought process behind and goals of the https://github.com/cljctools > project: > > https://github.com/cljctools/readme#rationale > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/e4eb29ef-949a-4d06-88d5-b47ba96d6faao%40googlegroups.com.
Re: Classpath bug re Clojure 1.10.1.645 when using Figwheel.Main
Too fragile. This reminds me of the notion of "situated programming", featured in the talk by Rich Hickey: you and your programs operate in the middle of a bizarre and changing situation. For Clojure, the Java ecosystem is part of that situation. Even if some jars do not overlap today, you will be forced to take a minor update someday that introduces a clash. Or perhaps (quite likely) jars do overlap today, but you will take a minor update someday that causes the classpath to emerge from the hash-map differently and your program won't work anymore. The insight of the theory of "situated programs" is, not to hit a cliff when a perfectly legal quirk arises in the situation. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/4005f2c2-d95d-4612-b2e3-b223b731700eo%40googlegroups.com.
