I've always heard the terms "double-buffering" and "triple-buffering" thrown around but never knew what they meant. Now I know after this amazing talk! The pace is a little fast for the big amount of information, but it was still very insightful.
@aksh16182 сағат бұрын
The DSL example is pure elegance and I'm here for it!
@vengateshm21223 сағат бұрын
Is this available in kotlin 2.0?
@thedeemon2 сағат бұрын
After 2.2. see 12:40
@vengateshm21222 сағат бұрын
@@thedeemon Thank you.
@vighnesh1533 сағат бұрын
This looks very similar to compositionLocals in Jetpack Compose.
@PavelPikalov-z6t5 сағат бұрын
I'm looking forward to this feature
@bofu96626 сағат бұрын
Nice feature
@seksky3338 сағат бұрын
Love your work. Keep going. Always love to see devs utilising Canvas to draw great things.
@abdrsbte8 сағат бұрын
What a beautiful Rectangular app 😂 A very nice code along 👍
@vengateshm212210 сағат бұрын
Which client it uses for http communication? AWS SDK or kotlin native http apis?
@user-qx7zu7xg6u19 сағат бұрын
I checked this man's blog, it seems never update again.
@user-qx7zu7xg6u20 сағат бұрын
first commit?
@henrik9086 сағат бұрын
So what ?
@VirgilioSolanoКүн бұрын
Nice, congratulations for whole JetBrains team.👏
@ndrmqaxnКүн бұрын
The cameraman should get an extra cup of coffee XD
@limecraftstudio6824Күн бұрын
If you ask me then my answer will be "Because its Perfect"
@bennyhuoКүн бұрын
🎉🎉🎉
@starry_shivam2 күн бұрын
He seem to be dancing while speaking lol
@dzartxstudio2 күн бұрын
He appears to be so stressed
@h4ktbtw2 күн бұрын
Now I get it why Compose feels better on iOS
@GeorgeC-ur9yw2 күн бұрын
Thats a huge amount of work put into it
@artursradionovs95433 күн бұрын
Where to study Compose Multiplatform or Kotlin Multiplatform?
@DystopianSnowman3 күн бұрын
While I understood only the half of it, it was *very* interesting! Nice work!
@JamesPower3 күн бұрын
Really neat stuff
@bofu96623 күн бұрын
Wow
@yektadev3 күн бұрын
Interestingly detailed👌
@MWGreek4 күн бұрын
Finally
@hifromspace4 күн бұрын
Очень круто. Не удивительно что он первый в мире.
@etherxi4 күн бұрын
this will be more useful if we can read through the ktor server implementation and create a type safe client side codes using ksp.
@srinisiddireddy14284 күн бұрын
Overall great job. We @SportsPlusApp are counting on Timefold for youth sports scheduling to make it easy organizing sports.
@nO_d3N1AL5 күн бұрын
This seems like a classic use case for model-driven engineering. I'm curious whether the team considered using mature MDE tools such as EMF, Xtext and Epsilon 🤔
@nishu333895 күн бұрын
Does the shared rest api call also implemented in this demo project?
@krellin6 күн бұрын
its great but the only thing that sucks about this is the serialization its pretty clear that state of the art approach is to not do any serialization, just wrap a buffer with something that can randomly access fields like SBE, capnproto, flatbuffers... but this is fine for majority, i just don't see why not have the best of the best.
@shadowpenguin34826 күн бұрын
I think you misunderstood. SBE, capnproto and flatbuffers are all serializations. So it is the same interface as JSON, but different implementations. The difference lies in the efficiency. In the call he mentioned that CBOR and protobuf are already supported (which is also very efficient). So krpc is separated from the concrete serialisation implementation :)
@krellin6 күн бұрын
@@shadowpenguin3482 oh thats nice, i thought its hardcoded to use their own kotlin serialization thing they did a while ago... Regarding the libs mentioned no they do not do any serialization, they format data in binary form and store it in buffer, so when you get data over network into buffer you are literally ready to interact with that message, even mutate in place, you are not reading the buffer into new object and populating any fields. Similarly when you want to send the message its entire serialized form is ready in the buffer, no actual serialization or deserialization happens. Most applications have highest overhead from serializatios, with those you completely avoid that overhead.
@krellin6 күн бұрын
@@shadowpenguin3482 oh i didnt see that serialization is independent, i thought they just use their own serialization which i remember was actually creating objects... i'll check what is the interfce, i find that often its not possible to integrate some of these zero garbage/zero serialization libs
@krellin6 күн бұрын
@@shadowpenguin3482 so i was right, in order for you to implement a serializer for something like SBE/capnp/flatb you need much more controll over buffers and how they are managed, their interfaces forces you to return an object after reading the buffer, meaning you are done with the buffer once you return it, so you cant just do the wrap over buffer segment and return the flyweight... and thatas why you cant do it... as i said that's the only thing that sucks about this RPC, but its ok for the majority. UPDATE : i believe with this interface (SerialFormat) you could maintain a pool of buffers and pay the cost of buffer copy which is still much cheaper than any work converting binary into object... but yes you cannot take full advantage of zero copy and zero serialization... Still super useful library that makes perfect sense to have in kotlin, kudos to JB
@erictsang06 күн бұрын
This is awesome and so easy! Wow 😃
@vengateshm21226 күн бұрын
Cool stuff.
@demo13307 күн бұрын
kord is really nice but needs the docs updated badly
@Heksapoda7 күн бұрын
Is it mean that Activity initiate a Thread and exist until the Activity destroyed then other components could use that Thread to do asynchronous job?
@landsman7377 күн бұрын
what a hack
@clurigaconrad7 күн бұрын
One of the more interesting talks of the conference!
@aniruddhasen88017 күн бұрын
I was with you in the first half . . . but when you started adding `LoggerContext`, `NotificationContext`, adding more objects to the `main()` function, and then extracting the logging call to a separate context received function . . . I started to think, _". . . Honestly, at this point, I don't mind adding the logger and notification sender as parameters to my function."_ If the point of this is to simplify code, then you've definitely missed the runway. *Edit:* Though, I'm still wrapping my head around 'em, the transaction & JSON examples helped clarify & justify the use of context receivers. More exploration, investigation, deeper inspection, consideration, and contemplation is definitely needed (from my end, that is).
@evgeniyemelyanov72817 күн бұрын
Great explanation, thanks!
@MaxWeninger8 күн бұрын
So now you can do what you can do with Jupyter notebooks in Python for years? :)
@kyay108 күн бұрын
But with static typing, MUCH BETTER IDE help, a way faster language, and all of the JVM libraries available to you
@swankidelic8 күн бұрын
Wonderful talk. Combines code, math and art so gracefully. Really shows how notebooks make code into an artistic tool of expression.
@ilyaglaz76328 күн бұрын
Very impressive!
@cslesin57508 күн бұрын
when math comes to code I am like 🤯
@user-eb9kg4kn7h8 күн бұрын
Finally, an argument for people sticking with Spok (which is waaaaay too magical) and it's assertion messages
@aungkhanthtoo76788 күн бұрын
Great talk!
@LarryGarfieldCrell8 күн бұрын
The live demo gods were not kind today...
@khaqim41489 күн бұрын
What is it about?
@MixwellSidechains9 күн бұрын
Bravo. I loved your presentation!!
@MixwellSidechains9 күн бұрын
Jetbrains and all fellow developers. Can we have at least 1 or 2 libraries that are goto libraries (even if they can be endorsed by Jetbrains or up voted by the community) for various things. If they can be open source that would be great since everyone would contribute to the same library. It's not practical to have a dozen of libraries that access the camera for all KMP platforms with some having better features than others. I've seen that with Flutter, there are too many gibberish libraries fighting for prominence. It's nice to have a standard or 1 or 2 choices, it's great for community support. For example for KMP persistence we have Room Library or the MongoDB one. Two is enough.
@toshempire82969 күн бұрын
Am flutter developer what are the benefits of KMP
@sanglin93879 күн бұрын
in our new project - we stick to few naming . yes we know a lot of existing table column and those pojo / poco is a mess up