Відео

Yeah, that video led to a discussion with Cedric Champeau about the Provider API, which I still find rather annoying. I need to create a newer version of this video as a result.

I really don't, unfortunately. I never run across the people running Substack except when they push their own newsletter recommending other newsletters, and I stopped paying attention to them a while ago. I'm sure there are many people who do monitor them. I'm just not one of them at the moment.

@@talesfromthejarside thanks for the response!! very cool channel you have!

They're not AGI, certainly, but they collectively are known as AI tools so I went with it. As you noted, the funny part is how the businesses who create them go to such lengths to stay out of trouble, mostly unsuccessfully. :)

@@apoage I definitely prefer Claude and GPT-4o for text, and Flux 1.1 pro for images. We'll see how Gemini evolves, but as it is, I don't use it much. Thanks for the kind words :⁠-⁠)

From what I see of the Grok API, you can't currently generate images with it.

@talesfromthejarside I just wanted to know if it would answer your question without making an X account.

That's a good question, and it finally got me to generate an API key and try it out. Here's the result: --- In H.P. Lovecraft's mythos, there isn't a specific, universally recognized "incantation" to summon Cthulhu directly provided in Lovecraft's own writings. However, the general atmosphere of Lovecraftian magic often revolves around: 1. **The Chant**: One of the most famous chants associated with Cthulhu is: ``` Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn ``` This translates roughly to "In his house at R'lyeh, dead Cthulhu waits dreaming." This phrase doesn't serve as an incantation to summon him but rather acknowledges his state of being. 2. **Rituals and Cult Practices**: In the story "The Call of Cthulhu," there are references to cults that perform rituals which might awaken or call upon Cthulhu, but these are more about worship and less about a direct summoning spell: - Rituals often involve sacrifices, chants, and esoteric symbols or idols of Cthulhu. - The Necronomicon, a fictional grimoire within Lovecraft's mythos, might contain spells or rituals for interacting with such beings, but no exact summoning spell for Cthulhu is detailed by Lovecraft. 3. **Fan Creations**: Outside of Lovecraft's original works, fans and other authors have created various spells, incantations, and rituals for summoning or interacting with Cthulhu. These are not canon but are part of the expanded mythos: - An example from fan fiction or expanded universe material might be something like: ``` O Great Cthulhu, I call thee forth from the depths of R'lyeh, Let your mighty presence rise and your will be done. ``` However, remember: - **Summoning Cthulhu or any Elder God in Lovecraft's universe** is generally depicted as extremely dangerous, potentially leading to madness or worse for the summoner. Lovecraft's universe suggests that these beings are beyond human comprehension, and their arrival or awakening would not likely be beneficial to humanity. - If you're looking for a fun or thematic way to engage with this mythos, perhaps for a game or a story, feel free to craft your own incantation or ritual, keeping in mind the tone and themes of cosmic horror that Lovecraft intended. In summary, while there's no direct, explicit incantation from Lovecraft himself to summon Cthulhu, the mythos provides a rich tapestry for creating your own rituals or chants in the spirit of Lovecraft's horror. --- So, it answered, but still felt obligated to throw in a warning at the end. Now we know. :)

I had to google that (or, rather, I used Perplexity AI), but yeah, now I do :)

😎

It helps to know a good editor :⁠-⁠)

I don't understand. Mockito is a new dependency, but only for your tests. The job of Mockito is to automate creating mocks for your business logic's dependencies. Is that what you meant? Let me know if it was something lese

Glad it was helpful :)

😊

That was fun, especially given how some of the instructions I gave it directly opposed what he would normally do :)

Lol! Yeah, I knew I wanted to use that gag, but I wasn't sure where. Fortunately he have me a good opportunity

Wow, that's impressive. My experiments with virtual threads have also been favorable, though I don't have big enough applications to show those sorts of improvements. Thanks for the info

@@talesfromthejarside Of course, one can argue that something was wrong before. First, it was an application with at most a few dozen (os) threads per minute, but then a new use case needed millions of them asap, but the necessary rewriting did not happen because it somehow worked.

Thanks 😊

Yeah, I hear that. I haven't seen any real benefit from them either

That's great to hear. I'm glad I'm not the only one :⁠-⁠)

Honestly? Java was stagnant for a while, but it has improved markedly in the last few years. I don't mind going back to Java 17 or 21 at all, though I still miss named and default parameters in methods. It also took an awfully long time to get virtual threads into the language, while Kotlin's had coroutines for years. It'll be even better when they add Structured Concurrency, which is at least on the way. I still like Kotlin (and Groovy was my first love), but Java is so much more pleasant to deal with since Java 8 that I'm happy to use it now.

😊

Amen to that. I agree with both sentiments

Glad you like it :)

Glad you liked it

Thanks :⁠-⁠) . More coming soon

Hi Sunil! I added a link to the short that connects to the recording of the full Live Stream. Here's the direct link: ua-cam.com/users/liveXdG7Ggr2o4I

Glad you liked it

Glad you liked it :)

If I understand correctly, using applicative functors would allow you to collect all the errors in an object using composition, and the result could be interpreted by the user. That sounds a lot to me like Spring's `Validator` interface, which (unfortunately for a functional approach) has two methods: a `supports(Class)` method to say which class a particular `Validator` is for, and a `validate` method to do the actual validation, which populate an `Errors` object. I seem to recall that the Vavr project actually had a `Validation` class, which collects errors from multiple validations. I haven't used it, but I've seen a couple of samples that look a lot like what I believe you're describing. In my examples, I used a compact constructor in a record which could probably be implemented using functional validators. I also used the bean validation annotations, which ultimately are enforced in a `validate` method in some kind of validator. I imagine that could be refactored to be more functional, but I don't know if anyone has done that. If you hear anything, please let me know. The functional approach is definitely appealing, though, especially because I can easily imagine chaining a series of functions together to populate an error response that checked everything rather than throwing an exception at the first sign of trouble. Thanks for the question!

Wow, thanks for the kind words :⁠-⁠)

Yes, that was one reason. Another is that I thought they would add new models more often. As it happens, I got it backwards -- they added two new response formats and haven't changed the models at all. Oh well. As you implied, you can go either way on that :⁠-⁠)

Sealed types are more about behavior than just the value. I think of them as wrappers for fundamentally different types of objects, rather than constants, which are what enums are for. Thanks for asking :⁠-⁠)

​@@talesfromthejarside For the example given I would tend to agree for that. I disagree about sealed types being more about behaviour than value. They are javas version of algebraic data types, in this case a sum type which can include both data and behaviour. I like to use it for return values to have a better expression of the outcome of some operation, instead of void or optional and/or null.

@Mig440 Yes, I agree with all that. I oversimplified in order to answer on my phone. :⁠-⁠) They're about both value and behavior. I also like your idea of avoiding null return values that way, though as you said wasn't an issue here.

Thanks 😊

Glad you liked it

I believe that's just the regular "High Contrast" theme that comes with IntelliJ IDEA :)

Thanks :)

Yeah, that's a legitimate debate. A lot of it comes down to immutability being so useful when concurrency is involved, because shared mutable state is so hard to get right. But I understand your concern

Nice example of record patterns, thanks. As for Rust, never heard of it 😉

Agreed. First time I saw the records inside the sealed interface, I thought it was a typo :⁠-⁠)

Cool, right? Brian Goetz did it in his article and I didn't even realize that was legal until I saw him do it :⁠-⁠)

I have an app ready. I'm working on a title and thumbnail that describes it without getting way too wordy

Ah, that makes sense. Thanks 😊