ºÝºÝߣshows by User: Ivanuki / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: Ivanuki / Wed, 21 Oct 2015 19:36:28 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: Ivanuki Reactive Qt - Ivan ÄŒukić (Qt World Summit 2015) /slideshow/reactive-qt-ivan-uki-qt-world-summit-2015/54233794 ivan-cukic-reactive-qt-qtws-151021193629-lva1-app6892
Reactive programming is an emerging discipline which achieves concurrency using events-based programming. Today, It is mostly used for writing very scalable web services that can achieve high concurrency levels even on a single thread. The concept is simple - make a system that is fully event-based, and look at events not as isolated instances, but as streams. When we have streams, we can manipulate them as if they were simple ranges. We can filter them, modify them, combine multiple streams into one etc. Reactive programming is not only applicable to the web services, it can be used in any event-based environment. In our case, in normal Qt applications, to enrich the power of signals and slots. [...]]]>
Reactive programming is an emerging discipline which achieves concurrency using events-based programming. Today, It is mostly used for writing very scalable web services that can achieve high concurrency levels even on a single thread. The concept is simple - make a system that is fully event-based, and look at events not as isolated instances, but as streams. When we have streams, we can manipulate them as if they were simple ranges. We can filter them, modify them, combine multiple streams into one etc. Reactive programming is not only applicable to the web services, it can be used in any event-based environment. In our case, in normal Qt applications, to enrich the power of signals and slots. [...]]]> Wed, 21 Oct 2015 19:36:28 GMT /slideshow/reactive-qt-ivan-uki-qt-world-summit-2015/54233794 Ivanuki@slideshare.net(Ivanuki) Reactive Qt - Ivan Čukić (Qt World Summit 2015) Ivanuki Reactive programming is an emerging discipline which achieves concurrency using events-based programming. Today, It is mostly used for writing very scalable web services that can achieve high concurrency levels even on a single thread. The concept is simple - make a system that is fully event-based, and look at events not as isolated instances, but as streams. When we have streams, we can manipulate them as if they were simple ranges. We can filter them, modify them, combine multiple streams into one etc. Reactive programming is not only applicable to the web services, it can be used in any event-based environment. In our case, in normal Qt applications, to enrich the power of signals and slots. [...] <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ivan-cukic-reactive-qt-qtws-151021193629-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Reactive programming is an emerging discipline which achieves concurrency using events-based programming. Today, It is mostly used for writing very scalable web services that can achieve high concurrency levels even on a single thread. The concept is simple - make a system that is fully event-based, and look at events not as isolated instances, but as streams. When we have streams, we can manipulate them as if they were simple ranges. We can filter them, modify them, combine multiple streams into one etc. Reactive programming is not only applicable to the web services, it can be used in any event-based environment. In our case, in normal Qt applications, to enrich the power of signals and slots. [...]
Reactive Qt - Ivan Čukić (Qt World Summit 2015) from Ivan Čukić
]]> 2026 4 https://cdn.slidesharecdn.com/ss_thumbnails/ivan-cukic-reactive-qt-qtws-151021193629-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Natural Task Scheduling Using Futures and Continuations, Ivan Čukić, Qt Developer Days 2013 /slideshow/qt-developer-days-2013-ivancukic/27073962 qtdd13-ivan-cukic-131010150429-phpapp02
We are used to think about algorithms in a procedural manner – with loops, branches and subroutines. Presenting an algorithm as an easily understandable flow between its steps. In the real world, where we need to reduce latency and forbid the blocking API calls, these flows get broken. Due to the inversion of control (IoC) required by the introduction of asynchronous APIs (Xlib vs. XCB, iostream vs. boost::asio), the code becomes an unreadable call-callback soup. We are presenting a way of defining the algorithm flow in a procedural manner and leaving it up to the C++ compiler to generate the necessary asynchronous code. ]]>
We are used to think about algorithms in a procedural manner – with loops, branches and subroutines. Presenting an algorithm as an easily understandable flow between its steps. In the real world, where we need to reduce latency and forbid the blocking API calls, these flows get broken. Due to the inversion of control (IoC) required by the introduction of asynchronous APIs (Xlib vs. XCB, iostream vs. boost::asio), the code becomes an unreadable call-callback soup. We are presenting a way of defining the algorithm flow in a procedural manner and leaving it up to the C++ compiler to generate the necessary asynchronous code. ]]> Thu, 10 Oct 2013 15:04:29 GMT /slideshow/qt-developer-days-2013-ivancukic/27073962 Ivanuki@slideshare.net(Ivanuki) Natural Task Scheduling Using Futures and Continuations, Ivan Čukić, Qt Developer Days 2013 Ivanuki We are used to think about algorithms in a procedural manner – with loops, branches and subroutines. Presenting an algorithm as an easily understandable flow between its steps. In the real world, where we need to reduce latency and forbid the blocking API calls, these flows get broken. Due to the inversion of control (IoC) required by the introduction of asynchronous APIs (Xlib vs. XCB, iostream vs. boost::asio), the code becomes an unreadable call-callback soup. We are presenting a way of defining the algorithm flow in a procedural manner and leaving it up to the C++ compiler to generate the necessary asynchronous code. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/qtdd13-ivan-cukic-131010150429-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> We are used to think about algorithms in a procedural manner – with loops, branches and subroutines. Presenting an algorithm as an easily understandable flow between its steps. In the real world, where we need to reduce latency and forbid the blocking API calls, these flows get broken. Due to the inversion of control (IoC) required by the introduction of asynchronous APIs (Xlib vs. XCB, iostream vs. boost::asio), the code becomes an unreadable call-callback soup. We are presenting a way of defining the algorithm flow in a procedural manner and leaving it up to the C++ compiler to generate the necessary asynchronous code.
Natural Task Scheduling Using Futures and Continuations, Ivan Čukić, Qt Developer Days 2013 from Ivan Čukić
]]> 4958 4 https://cdn.slidesharecdn.com/ss_thumbnails/qtdd13-ivan-cukic-131010150429-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-Ivanuki-48x48.jpg?cb=1523450261 cukic.co https://cdn.slidesharecdn.com/ss_thumbnails/ivan-cukic-reactive-qt-qtws-151021193629-lva1-app6892-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/reactive-qt-ivan-uki-qt-world-summit-2015/54233794 Reactive Qt - Ivan ÄŒuk... https://cdn.slidesharecdn.com/ss_thumbnails/qtdd13-ivan-cukic-131010150429-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/qt-developer-days-2013-ivancukic/27073962 Natural Task Schedulin...