Introduction RStudio Server desktop app options Site-specific-browser (SBB) tools Electron Unite / Coherence X Introduction In my work as an R consultant/scientist, I often work on/with RStudio Server (soon to be RStudio Workbench) instances. These have several advantages: The workload is executed on the server and not your local machine The environment can be centrally managed for many users and prevents OS-related issues on Windows/macOS/Linux user machines Session keep running in the background even if the local machine is powered off Often RStudio Server instances are way quicker than local RStudio Desktop installations However, there is also (at least) one downside: it runs in a browser (tab).

Reproducibility is important. More important than ever. However, making a project reproducible is not as trivial as it sounds.

Introduction The problem The mlr use case The solution Code Introduction Continuous integration checking for R packages is usually done on Travis CI because the R community has established a community driven build framework for R. In case you are not aware, there are also other tools that try to simplify the CI tasks for R even more. This works great for simple checking of small R packages but once it comes to packages that have a lot of dependencies, developers sometimes run into troubles regarding build time.

Notion.so is a great tool for various tasks. I use it as a personal wiki but also for work-related notes. Unfortunately there is no native support for Linux and even though this point has been mentioned quite often by the community, the Notion team did not provide a Linux Desktop App yet. Maybe it will never be shipped. The Linux Desktop world can be evil when you have to make money selling applications.

Introduction The advantages of i3wm The disadvantages of i3wm My I3wm setup Introduction After switching from Windows/macOS to Linux about 1.5 years ago I tried many different Linux distributions and desktop environments. I do not want to go into details why I am running Arch Linux (Manjaro) in this post but rather talk about the “visual engine” in the background: the desktop environment. Strictly said, i3wm is not even a desktop environment but rather “only” a tiling window-manager1.