Posts

Showing posts from 2017

Slides on TV 1.1 is out!

Image
Release 1.1 I've released a new version of Slides on TV the app that make easy and comfortable (from your sofa)  to watch the presentations on your TV (for details please refers to my previous   post Watch presentations on Apple TV - Here is SlidesOnTV ) Fig. 1 - Main Menu New Features The main feature included in this release the “ Favourites Management ” with the possibility to: Save reference to your favourites slides avoiding to search for it again ( such reference will be saved on ICloud) View Your saved Favourites Delete a Favourite Fig. 2 - Add to Favourite I've also implemented the “ cancel download ” feature  through the remote menu button (Fig.3) Fig. 3 - Cancel Download ? What’s Next For next versions I’ve planned to integrate “ Top Shelf “ feature to allow showing favourite presentation directly from TV desktop Conclusion I hope that, for who own an Apple TV,  SlidesOnTV  can help you to enjoy, ev

Reactive Programming and the RX (r)evolution

Meet-up at DevDay Lately i've conducted a meet-up at DevDay , an Italian Developer Community,  to present the Reactive Programming Paradigm and Reactive Extension. I believe in this approach and would like to share my experience, so I've presented a "slide deck" (embed at the end) and below is reported its summary. 1. The Reactive Manifesto I've briefly introduced the Reactive Manifesto , underlining which are, in my opinion,  the most important concepts coming out from it: Asynchronous non blocking Message Driven  back-pressure Resilient 2. Why use Reactive Why the Reactive Systems are becoming so important in the modern age of the Microservices & Cloud ? In this part I have introduced the importance of  : Let's do it asynchronous  Async != Multi threads Async == Never Block Immutable State 3. When to be Reactive  When Reactive Programming could help you ? For developing which Applications ? In particular, d

NodeJS - Event Loop unveiled

Image
NodeJS : An asynchronous single threaded environment 😮 When started to work with nodeJS i was surprised that it was advertised as " asynchronous single threaded " environment. So I've tried to understand how it worked and then, at the end, I have dealt with famous and notorious event loop. Moreover, during studying, I've also figured out that its operation was the same either when Javascript run in NodeJS than in the whatever Internet Browser. The Event Loop In the image below has shown the basic event loop schema that make clear the architectural choices behind  the callback model (and as consequence the callback hell). In fact such model allows to decouple the event loop thread, where the main application runs, from all the resource consuming operations. Basic Event Loop Schema Event Loop in NodeJS The image below adds more details to the previous one in particular, concerning event loop, we find out event queue and worker threads that give us a

Reactive programming by examples - Episode 1

Reactive World Is almost one year that I have started to learn the reactive world , I began from its manifesto and i continued applying it in development of my Open Source projects and  in particular through the  languages JavaScript (and then RxJS ), Java (and then RxJava ) and Swift (and then RxSwift ) Why Reactive ? I nitially I approached reactive paradigm like a kid that open the gift box with a new and unknown toy, mostly fascinated by the technological wave that carried with it a lot of “ new ” stuff like: functional programming , stream/event oriented programming , backpressure , “ callback hell ” solver . But as always “ all that glitters ain't gold! ” and our capacity to understand context of problems make the real difference and help us to choose the right approach, language, paradigm and frameworks to put on the table. Better explain by examples So I would share with you some problems in particular contexts that I have dealt with reactive