Frankel.ch Website Review

A post brought to light an interesting feature of the JDK I didn’t know about: the ability to update a code running in a JVM. The referenced post shows how to apply a bugfix using that feature. The devious white hat JVM hacker in me started to think how one could apply that trick for other less beneficia Nicolas Fränkel Nov 25, 2018 Kotlin collection sequence stream lazy evaluation When streams were added to Ja*a 8, I wanted to jump on the bandwagon. I read blog posts, watched videos, attended workshops to understand what this was all about. After a while, I became comfortable enough…​ but I was unhappy with the implementation: while streams offer methods with a functional approach, legacy collections do not. When one wants to use Ja*a capabilities on an existing collection, the Coming from a Ja*a background, I'm currently trying to learn the Clojure programming language, with the help of online resources and mentorship. Some weeks ago, I tried to wire things together by trying to find equivalent methods to those available in Ja*a streams. While I managed to get things working, writing working code and writing idiomatic code are two very different things. I was fortunate to have a good degree of feedback from different sources: Hacker News, Reddit and on this very blog. Some weeks ago, I read the post referenced in a tweet. In short, the article provides two ways to generate the boilerplate code required by the Builder pattern: Lombok, to generate code at compile time and the Spark Eclipse plugin, to generate code at development time. However, I already wrote about the Builder pattern. And it's a bit more complex than what's described in the referenced post. In general, one learns by comparing to what one already knows: I'm learning Clojure in that way. Coming from a Ja*a background, I naturally want to use streaming features. So, what would be the Clojure counterparts of Ja*a's functions filter(), `map()`, etc.? The Ja*a EE platform is huge, and I must confess I'm not aware of every one of its API. This is also true of the Spring framework, even