My Clojure take on a* was kinda of a journey. I thought I understood the algorithm several times while implementing it. It took me a few passes, now I'm quite happy about the results. Impressive how concise it is compared to the imperative version in other languages. Here if you want to see https://gist.github.com/reborg/c3372428c6ccd7d93289fb7a3a9ec...

You should have a look at : https://github.com/TristeFigure/shuriken/blob/ffbff58b19d555....

That is a very sexy snippet.

I love well written clojure code

I assume @hemanth is happy for the project README to appear on the blog of a recruitment agency. Along with the rest of the blogs that seem to be copy pasted from the original location. Should I guess functional-works obtained permission from all the original copyright holders?

Original article is here: https://github.com/hemanth/functional-programming-jargon/blo...

Functional works does not mention the MIT license and thus is allegedly infringing on his copyright.

They link to the original source though. And the author seems to be hemanth himself. So perhaps this is all false alarm.

yeah, we reached out directly to Hemanth and got a written consent to re-publish as long as the attributions were visible enough - he is credited as the author, plus there is a link for the original source at the bottom.

As with all articles on our blog that are not written by us, the authors can reach out to us at any time if they want to make any changes to the article and we'll be happy to comply. As well, they can make the changes by themselves at any point.

Regarding the MIT license, we didn't think of mentioning it on the blog - but thank you for head's up, we'll look into it.

We absolutely receive permission before we publish anything. With final approval coming from the author before anything goes live.

We have a platform that givs visibility to the great work that’s being done in the functional space.

>We have a platform that givs visibility to the great work that’s being done in the functional space.

Wow, that's disingenous. That's nothing like what you do. You have a platform that promotes your brand by copying and pasting other people's content into a worse presentation with your logo in a sticky navbar stuck to the top of the page.

You guessed correct. We ask each author for prior permission to rebublish. Although around 50% of the posts you see have been contributed directly by the authors which we then will approve before they go live on our site. We actively curated posts we feel our audience of 50,000 functional programmers will find interesting but only publish those that we have the permission to do so.

Happy to review the code, but I'm having trouble understand which snippet you're referring to.

Ops, didn't think about that! Added Clojure to the title. Thanks for raising. (author here).

Nicely written. I enjoy the same positive pragmatic feeling using Clojure every day. I'm not sure if there are contexts in which this initial ease is NOT going to payoff (maybe it depends on my limited experience observing large dynamically typed codebases evolving over time).

Having started some Haskell lately, I have the impression that also statically typed FP (not just OO) can suffer from the same mindset to try to figure out correct types up-front. Of course sane discipline and smart developers can overcome this or any other trouble in any language, but still, it brought back a bit of my Java years.

Congrats to the team for the great delivery, another example to illustrate real-life Clojure projects aren't really hard to find anymore.