Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Top repositories
clojure’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside clojure’s account where clojure opened or reviewed pull requests in the past 365 days.
Who noticed clojure
Everyone who starred or forked clojure’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 11st place finishes
- Silver
- 32nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 1Owned by clojure now
Repositories
Ordered by gold, then silver, then bronze.
- clojurescriptBest: 1st by stars, 345 stars130
Every award
Top-three finishes of these repositories in completed trending days and weeks, newest first.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Stuck understanding macros vs functions Yes, it's another one of these. I feel like that scene in Seinfeld when Kramer is able to see hidden image in an abstract painting but Mr. Pitt cannot, to his increasing frustration. Case in point, I'm looking for a clear and simple explanation for this and came across this post >My favorite example for this is the lame idiom you see in Java code: if (log.isDebugEnabled()) { log.debug("expensive" + debug + message); } >This is "better" than just log.debug(...) because with the latter, your expensive log message argument needs to be evaluated even if debug is disabled. However, in a language w/ macros, you just say: (debug (str "expensive" debug message)) >and these considerations are already taken care of for you: github.com/clojure/tools.logging/blob/master/src/… then someone goes >Edit: Ohhh! I see! The message isn't evaluated until after! Got it. >I don't understand why this is special? >Why can't you rewrite log.debug to include the check? func debug(m string) { if log.isDebugEnabled() { log.debug(m); } } >What makes macros special in this case? and I'm over here stuck like "what? where? where???" I'm not getting the epiphany and it doesn't help that they linked to clojure and I can't read clojure. So, can we stick with this example? But can someone really ELI5 for me please? --- Let's say we have pseudocode file isDebugEnabled = True; def doSomeStuff(): ... if (isDebugEnabled) { debug("expensive" + debug + message); } ... Then yes, every time we run doSomeStuff() we will check if debug is enabled. I'm with you there, because 1. We enter the function. 2. Encounter the if statement. 3. Check if isDebugEnabled is true or false at the time. 4. proceed accordingly. Now can I please get a by-the-numbers of how macros make this more efficient? Thanks.