WORK IN PROGRESS!
We benchmarked the following operations (all operations got timed
with system.time()):
| ## Update apt | |
| sudo apt-get update | |
| sudo apt-get install -y build-essential tar wget | |
| ## Remove system curl | |
| sudo apt remove --purge curl libcurl4 | |
| ## Install OpenSSL | |
| cd ~ | |
| wget https://www.openssl.org/source/openssl-1.1.1w.tar.gz |
Summary of meeting between Tidyverse members and Luke Tierney at useR! 2024.
Frontends and low level tools need to know what kind of bindings they are dealing with. Objectives include:
Avoiding side effects such as triggering a promise or causing a missing argument error. Low level tools often can't afford to protect against those for every variable lookup. Figuring out what happened by inspecting errors is also ambiguous, and sometimes impossible (promises may cause longjumps in a variety of ways).
Transparency in debugging/development settings. Providing context to the user about what's going to happen if they attempt to retrieve the value of a binding (i.e. an active binding invokation, a promise forcing leading to the evaluation of such and such expression, etc).
| library(shiny) | |
| library(dplyr) | |
| library(plotly) | |
| ui <- fluidPage( | |
| mainPanel( | |
| tags$style(".recalculating {opacity: 1.0}"), # Comente esta linha para ver o comportamento normal do shiny | |
| plotly::plotlyOutput("grafico") | |
| ) |