The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered for cdCon+GitOpsCon to participate in the sessions. If you have not registered but would like to join us, please go to the event registration page to purchase a registration.
This schedule is automatically displayed in Pacific Daylight Time (UTC -7). To see the schedule in your preferred timezone, please select from the drop-down menu to the right above "Filter by Date."
In the delivery ecosystem, devs have a great many choices to make regarding environment. In the past, the top-bar choices were limited to mainly two or three axes: language runtime, operating system, architecture. Now we can further consider these other new operational overheads: Kubernetes, Sandboxing, Browser targets! For a long time choosing a browser as a runtime target meant that choice for language would be severely limited; one could only choose from among the languages or runtimes that browsers could accept (the list kept getting shorter until it was practically only JavaScript! Flash? Java? Forget it, all gone). Wasm is the new binary instruction format for a stack-based VM, and portable compilation target, to save us all from writing only JavaScript forever. Wasm binaries are sandboxed code modules that can interchangeably target either browsers or servers at runtime, and we can use our familiar languages that a growing number are trending towards adding support for Wasm in the language core, including Ruby and Python. But does this mean we can just bring our Ruby to the browser and forget about Kubernetes forever, or is there more to consider before we start the party?