Code generation has been a well-established technique in software development for decades. Whether you just need a short script converting data into comma-separated values or you require complex language processing, string segments - the code - must be composed eventually. In my daily work, for example, I use code generation to compare the results of unit tests and integration tests with human-readable expectations.
Memory Leaks leading to undesired growth and exhaustion of resources are by far the most common production problem reported on enterprise scale applications. Closure, a powerful semantic feature in functional programs which are used pervasively in modern languages, is a prominent source of unanticipated memory leaks. In this presentation, I will explain most common use cases where Closures are used and their implications to memory retention.
While Javascript as a language is easy to learn, node.js as a platform offers some difficulty for beginners due to its peculiar programming characteristics, and there is always few developers who have questions on the out of order I/O and its implications in the program etc.
Different platforms, different paradigms. However, workload characteristics are not derived from these paradigms, instead driven by business needs. Which one to choose for my needs? The session evaluates the comprehensiveness of programming interfaces of Java, Javascript and Python and provide insights on efficiency in terms of semantic abstraction, readability, consumability, throughput, security, footprint etc. and make useful comparative analysis.
During the past several years, web frameworks have changed drastically. Although it was common to write backends in the classical blocking thread-per-request model, nowadays many developers are starting to use reactive frameworks in order to have better throughput and overall performance. Having in mind the pros and cons of both request models, we decided to create a new JS server engine for the Eclipse Dirigible runtime. This presentation will focus on what we had to change and why we did it. We’re also going to discuss the benefits of our approach compared to other solutions.
Providing developer tooling for people all around the globe using web technologies comes with a large amount of challenges. Aside from the technical issues of actually provisioning your application, you also have to consider the different backgrounds of your users. Making your app accessible to people outside of the English speaking sphere is therefore quite important. Internationalization (i18n), i.e. the act of enabling localization of your app, plays in a huge role in that.
1. How to use the Truffle suite (https://truffleframework.com/) to deploy and test smart contracts on the Ethereum blockchain
2. How to use the Truffle suite to develop a React based JavaScript client
If you love to develop web apps and are interested in the blockchain hype I'll show you how easy it is to develop an decentralized app by using the Truffle tools and libraries.
