Really interesting. Nowadays with new protocols and frameworks such as gRPC, rSocket, etc... there is no need to write low-level implementation for communication protocols anymore, however it is very useful to understand them how they works internally to know the better option to use depending on each case.
And is it a problem? You can always write your own annotation processor using the same annotations lombok uses but I find no good reason to do so. Every language has it's own "too good not to use" library but in Java's case it's very small and has no footprint because it just generates bytecode for you. Definitely fits in no-reason-to-not-use-it category.
Since IDEs generate all getters/setters/toString thing, there no reason do add more "unmanaged code" to your code base...convenience is not a good tradeoff for: extra processing time, extra memory usage, extra security risk and lack of control...
RSocket is ready for QUIC and we are actively working on adding support for it. There is already an implementation for Kotlin (not yet released). And the others implementations are under the development of the new quic transport. > Also, any insight into progress of RSocket Kotlin lib - the project seems to be stalled RSocket-Kotlin is live and is actively maintained. May be some of the work in progress and is not visible. But nevertheless it just from the first glance. We have a strong maintainer who does a ton of work to make RSocket-Kotlin a powerful cross-platform implementation of the RSocket protocol
@@olehdokuka8523Thank you for the update! I watched your and Violeta’s presentation from November on QUIC for RSocket and became very interested in it since. Good to know it is under active development.
Well explanations quite poor in this video. Topic is quite opposite very interesting. Definelty missing some pictures how it works inside. Even for electronics explanation such video even in 3D models but software education is lagging behind with old school.
