This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (3)
- # aws (3)
- # babashka (79)
- # beginners (105)
- # calva (10)
- # chlorine-clover (22)
- # clj-kondo (12)
- # cljs-dev (39)
- # clojure (52)
- # clojure-europe (1)
- # clojure-spec (15)
- # clojure-uk (12)
- # clojurescript (47)
- # conjure (93)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # figwheel-main (14)
- # fulcro (30)
- # instaparse (3)
- # kaocha (2)
- # lambdaisland (3)
- # malli (2)
- # meander (6)
- # off-topic (27)
- # pathom (14)
- # perun (1)
- # reagent (15)
- # shadow-cljs (69)
- # slack-help (2)
- # spacemacs (5)
- # test-check (23)
- # vim (9)
https://www.humblebundle.com/books/software-development-oreilly-books caught my eye the other day. Any of those worth the read?
97 Things... is definitely worth the $1 for the first unlock (disclaimer: the author is an old friend of mine). Not sure I'd be interested in most of the others tho' (and I own 97 Things already).
@U04V70XH6 do you mean Kevlin Henney? If so, do you happen to know if he uses / what he thinks of Clojure?
Yeah, Kevlin. I don't know what he's mostly working with these days but, like me, he was a heavy C++ user for a long time. You've encouraged me to ping him and see what he's up to these days 🙂
Mostly I feel he's been focused on language-agnostic testing/process stuff... (reinforced by https://www.slideshare.net/Kevlin/presentations )
Head first design patterns was how I learned design patterns back in uni. It has good examples and is an easier read than the gang of four book
Seconded! At my first programming job after self-learning programming, I got this book as a gift from my mentor when we where writing OOP PHP and it helped a lot to put things in more concrete terms than other "too academic" texts at that time
This book is great. I was programming before and when I jumped to Java boat to be industry-level developer it drifted me through pains of understanding codebases. Also it's a modern textbook.
The Head First series is excellent. I’ve read a few Design Patterns books (ironically not including the original/GoF one), and this one is the best.
heads up people, just got the news that Clojure is dead already, we need to find something else to be productive with. Sorry everyone 😕 https://twitter.com/jamie_allen/status/1248019842877145089
I’ve never understood the point of that kind of tweet. What is the intended result?
Guess the same could be said about a lot of tweets, much is off-the-cuff stuff. Think the intentation was not to say something about Clojure but more say something about Scala, but somehow managed to drag Clojure into it. In the end, 🤷
Trueee though I meant more in general where people post in a service that it’s dying or how people sometimes join channels here and post, “So this project is dead?” Just seems to happen to most communities I’ve participated in.
people have been saying Clojure is dead almost as long as I've been using it. yet, usage continues to increase (see last 12 mon Maven download data)
That’ll show him https://twitter.com/eccentric_jay/status/1249116959129645056 or not… because internet.
I saw 1 guy mentioning it on Twitter in the middle of a sentence talking about Scala, then Clojurians replied. Not worth arguing about that, IMHO.
Not unwise, but what’s the harm in showing a strong counter point? Neither party is dragging it out. Worst case it will be ignored.
Personally I'm not very fazed by people proclaiming the yearly "Clojure is dead" as it's obvious it's not when you're inside the ecosystem/community. Think most people just compared it to JS or any other language that goes through very fast changes year after year (like JS, Rust and others) and think Clojure has to be like that while failing to realize with Clojure it's not needed
When I heard the news, I knew I’d have to write up an implementation of Game of Life