I'm tired of the comparisons of "the industrial revolution" and the "printing press", I don't see those as comparable to what's happening here. Although Devin isn't this, there's a reason people refer to AGI as our last invention.
SBE needs to define the xml for the java bean, and generated the code. It need lots of work to implement a multiple-layer nested objects serialization. So I don't added it for now.
No, I just mean it's not easy to use. When using fury, you just need one line code for serialization: `fury.serialize(javaObject)`. When using SBE, it need to much coding, it needs define schema xml, compile code, and so on.
Big Peter Lawry fan - I use Chronicle Wire (the library mentioned in the article) often, it's a really nice serialization/deserialization library when performance/allocation is a focus. Combining Chronicle tools + Real Logic tools you can build some extremely performant Java applications.
I've actually really enjoyed some of the recommendations I get - my homepage is usually videos on Java, networking, DCS related content and for some reason last week I got a recommendation for a video by this channel that recreates historic life and the video was how to make a typical dinner as if it were 1820 - it was so random but awesome.
I too enjoy finding new stuff - Imagine being able to tell the algorithm that!
I'm baffled by tech companies taking highly complex recommendation engines with tons of tunable parameters and exposing literally 0 of them to the user. I don't want to see the same things all the time. And I especially don't want to keep seeing that one video all the time!
