วีดีโอ

ThePrimeagen the Clown

Casey is broken

Excellent explanation! A complicated concept explained very simply.

Do you know how to use vim?

It would be nice to go more in depth and see it in practice. This reasoning itself is unfortunately insufficient, as it seems to me to downplay the downsides while exaggerating the upsides. Downplaying the downsides: It is in fact a big deal that the data contract is enforced in the code and not assumed by the function and all the callers. The nature of code is to change and the nature of programmers is to forget, so these errors get resolved during compile time instead of becoming run time bugs. In addition, what do you do when you realize you no longer want to use a map, but instead want to use a set to hold your data? Do you go over every method that ever had to use that data and change it, or do you just change the implementation seamlessly behind an interface? Exaggerating the upsides: When am I actually going to reuse these map operations? Is a function that accesses `dictionary.get(httpStatus)` or whatever else ever going to be useful outside the context of an http connection? Is this just about meta collection operations like streaming, flatmapping, etc.?

impressive

Git internal implementation always surprises me.

This is my ultimate problem with trying to evangelize Clojure: all the young developers I keep talking to are not exhausted from the Java nonsense to really understand and appreciate Clojure. They've not seen the mess that big Java/C# apps inevitably evolve into. They don't understand that software is not about the now, but about the long term evolution of systems. They've just not experienced it. Oh well...

I know, this is an ancient video, but I have a change that improves this computation by cutting about 30% off the time. private static void analyzeWordPairs(List<String> words) { List<Integer> invs = Arrays.stream(powersOf31).map(x -> findIntInverse(x)).boxed().toList(); Map<Integer, List<String>> byHash = words.stream().collect(groupingBy(String::hashCode)); words.parallelStream().forEach(right -> { int targetHash = (Integer.MIN_VALUE - right.hashCode()) * invs.get(right.length()); for (String left : byHash.getOrDefault(targetHash, Collections.emptyList())) { System.out.println(left + right); } }); } where findIntInverse is: public static int findIntInverse(int x) { // find the number y such that as an int (after overflow) x*y = 1 // assumes x is odd, because without that it isn't possible. // works by computing x ** ((2 ** 32) - 1) int retval = 1; for (int i = 0; i < 31; i++) { retval *= retval; retval *= x; } return retval; }

excellent, thanks

Does hit different now that I am all three of those things.

You Clojure guys are insane... and not in a good way. This is extremely unreadable and difficult to understand. I'm not talking about data structures and algorithms either... I could code this up in 5 mins in Python or Java.

The Germans love their “koohl” and “heh”. Koohl

well he made another video with python code

Awesome video !

There's never going to be a next video, is there?

Nice

thanks

OMG! The audio!!!!

how come your Windows system uses bash?

After i learn clojure, my mind change

Clojure's backwards compatibility far out performs that of Scala's. Clojure just works, I haven't had issues w/versioning. Compare that w/Scala, where my Intellij setup is *always* breaking.

Danke dir

Would you consider doing some videos on namespaces, filenames, maven, jar, clojure cli, deps.edn, etc.? You explain things very clearly and I have found the Clojure language beautiful but the aforementioned topics rather difficult.

Would you ever consider a series of videos on reader macros? I hope these comments will do something to get the algorithm to recommend your videos more, they are tremendous.

Does the concept of transducers hold across other functional languages that rely more heavily on their static typing or type inference?

stop reading this, go.learn().

Great talk. What are you using to integrate the function arity and examples in your editor window? Very helpful information to have handy when using Clojure.

My take is that Kotlin is a better Java, but Scala is a better programming language.

💖

Great video. I am curious whether this quote at 0:38 ends up being correct or not. Based on the video vectors and sequences are fine, but not sure about things that can be parallel as Java streams Context for the question - transducer "shape" seems to pretty relatively simple. However, Java is now previewing a feature called Stream Gatherers which on the surface trying to achieve _some_ of the same goals (at least composability aspect of those intermediate operations), but despite being pretty Stream-specific, end up being much more complex of a feature comparing to transducers. Because of that I am wondering, are Stream Gatherers over-engineered, are transducers a bit more complex under the hood or are transducers not that universal for more complex scenarios?

excellent

thank you good sir! subscribed!

TDD from a different angle :)

Cool, I actually recently started reading a Common Lisp book from around 2005 criticizing Java a bit for how difficult it was to get things done with it. Which was at least true in that time, nowadays it does not matter all that much anymore, as also Java has evolved further. Performance comparison turns out to still be true. I have recently tried a bit of Lisp recursive calculations with SBCL, and it does pretty well for a scripting language, kind of in the order of where JS sits as well, which is still faster than most scripting languages, but slower than compiled languages like C#, Java and Go, which on their turn are slower than Rust, C and C++.

I think that indeed both Scala and Kotlin are actually a layer over Java in a way. I really like Clojure a lot. In my opinion I think the reason clojure doesn't grow that fast is purely because although lots of people claim that Java is a "horrible language", those same people likely do not want to do anything that is fundamentally different than java and clojure is an example of that. The fact that it also works in the JVM doesn't help to the argument. Some Kotlin developers I've met aren't even aware that there is a JVM running when they start a kotlin "program" to begin with.

You don't deserve 1 view cuz you need 2 years to make a part 2

Please improve the sound

Thank you a lot man

👍lol I dream huge

🤔 I don't this level of coincidence. Soo I will ask. What was the process that made you decide on your thumb nail for this recursive descent series BECAUSE I just finished a video about parsing. And you used the same pic of your thumbnail that I used mid video. My process for picking that image, I think I went to Pexels or RawPixel, I searched out rabbit hole because I was thinking Alice In Wonderland (the video game) and I am felt recursive descent is just going down the rabbit hole. The search results turned up rabbits and holes but also spirals. And I liked the spirals and I ended up choosing with that image. I never saw your video, I doubt you saw mine, I had searched for recursive descent videos but your video never came up. Only today did TH-cam recommended your video. A couple of days after I had published it on Odysee. I don't publish on TH-cam because I have a personal policy of boycotting Google. Anyways, yes, do you remember the thought process for choosing your thumb nail for this video?

I wished I found your video yesterday. I just spent the whole day trying to find out about this!! Thank you very much!!

I have never met a developer who recognizes that there is better elsewhere 🙂

The main issue with clojure is the relatively steep learning curve, for example due to the lack of standards for many common tasks (it follows quite a lot the lisp philosophy of having a lot home made)

fyi I have grabbed the original video that this is from from the waybackmachine and reuploaded it on my own channel.