Build Stuff'16 Lithuania

It‘s not the case anymore, that a good start-up needs an idea and an app. In pursue of success today we need more ingredients and new business processes. During this presentation you will hear examples and recommendations, on how to build a successful start-up: business process + idea + app.

When we talk about scaling, we usually mean up (bigger machine) or out (more machines). However, there is another alternative, which is changing our workload in a way that makes it inherently more parallelizable and then taking advantage of specialized hardware that's very good at handling that sort of thing. Most of us have exactly this type of hardware just sitting in our computers, doing very little most of the time. I'm talking, of course, about the GPU. General-purpose computing on the GPU (GPGPU) is no longer the domain of pure academic research. It is being used in real-world applications such as image processing and face recognition, cryptography, big data analysis, and Bitcoin mining. In this session we will examine the available GPGPU frameworks, learn how to integrate C++ AMP and OpenCL into regular .NET and Java applications, how to debug mixed .NET and GPGPU code in Visual Studio, and how to use the Aparapi framework to seamlessly mix regular CPU and GPGPU code in Java. We’ll even look at using GPGPU from server and client-side JavaScript with WebCL. We will discuss the kinds of tasks that can benefit from graphics card processing, how best to parallelize workloads, and what some of the performance trade-offs are.

Traditionally we consider web sites to be working in an online mode only. If the Internet connection drops, the entire web site stops functioning. Mobile applications, however, change this perception as connection is considered unstable and applications should take necessary measures for good user experience. Now we are able to create web sites that react on changes in the Internet connection and provide certain functionality offline. AppCache, IndexedDB and File API are few of the mechanisms to allow us to store the application and its data in the browser. However, now we have some questions to think about: Who is the master of the data - the client or the server? What data should we download in advance? How do we handle updates of the application? In this talk I will give overview of how web applications can go offline and which precautions we should take.