more talks
This commit is contained in:
@@ -71,6 +71,57 @@ background in cartography required, only a smartphone.
|
|||||||
|
|
||||||
**How Zig is Used at Uber**
|
**How Zig is Used at Uber**
|
||||||
|
|
||||||
* [Written form]({{<ref "log/2022/how-uber-uses-zig" >}}).
|
TLDR from the [blog post]({{<ref "log/2022/how-uber-uses-zig" >}}):
|
||||||
|
|
||||||
|
* Uber uses Zig to compile its C/C++ code. Now only in the [Go
|
||||||
|
Monorepo][go-monorepo] via [bazel-zig-cc][bazel-zig-cc], with plans to
|
||||||
|
possibly expand use of `zig cc` to other languages that need a C/C++
|
||||||
|
toolchain.
|
||||||
|
* Main selling points of C/C++ toolchain on top of zig-cc over the
|
||||||
|
alternatives: configurable versions of glibc and macOS cross-compilation.
|
||||||
|
* Uber does not have any plans to use zig-the-language yet.
|
||||||
|
* Uber signed a support agreement with Zig Software Foundation (ZSF) to
|
||||||
|
prioritize bug fixes. The contract value is disclosed in the ZSF financial
|
||||||
|
reports.
|
||||||
|
* Thanks to my team, the Go Monorepo team, the Go Platform team, my director,
|
||||||
|
finance, legal, and of course Zig Software Foundation for making this
|
||||||
|
relationship happen. The relationship has been fruitful so far.
|
||||||
|
|
||||||
|
|
||||||
|
Presentation:
|
||||||
|
|
||||||
|
* [Blog post]({{<ref "log/2022/how-uber-uses-zig" >}}).
|
||||||
* [Slides](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.pdf).
|
* [Slides](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.pdf).
|
||||||
* Video: [webm](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.webm), [mkv](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.mkv), [youtube](https://www.youtube.com/watch?v=SCj2J3HcEfc).
|
* Video: [webm](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.webm), [mkv](/talks/2022-zig-milan-party_How-zig-is-used-at-Uber.mkv), [youtube](https://www.youtube.com/watch?v=SCj2J3HcEfc).
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
2016-11-18 Build Stuff Vilnius
|
||||||
|
------------------------------
|
||||||
|
|
||||||
|
**Understanding and building your own Docker**
|
||||||
|
|
||||||
|
Docker started small and got big in really short time. Believe it or not, you
|
||||||
|
can learn to build your version of it too, within the duration of a conference
|
||||||
|
talk!
|
||||||
|
|
||||||
|
In the talk, we will assemble and run a Docker-like container with only
|
||||||
|
standard command-line tools found in modern Linux distributions.
|
||||||
|
|
||||||
|
First half of the presentation will cover the facilities Linux provides for
|
||||||
|
Docker to build upon: cgroups, pid and network namespaces, overlay file
|
||||||
|
systems. During the second half we will put theory to practice in a terminal
|
||||||
|
session. At the end of the talk we will not only be armed with knowledge how to
|
||||||
|
build an isolated container, but also have an actual container running.
|
||||||
|
|
||||||
|
After the talk, you will have a good insight how Docker works, and understand
|
||||||
|
how you could use its building blocks to build something that perfectly matches
|
||||||
|
your environment.
|
||||||
|
|
||||||
|
You’ll get most out of this session if you are comfortable in Linux terminal,
|
||||||
|
for instance, configuring networking from command-line. Knowledge about Pid
|
||||||
|
namespaces, cgroups or overlay filesystems is not required. You will learn it
|
||||||
|
all that during the talk.
|
||||||
|
|
||||||
|
* [Slides](/talks/2016-buildstuff-understanding-building-your-own-docker.pdf).
|
||||||
|
* Video: [mkv](/talks/2016-buildstuff-understanding-building-your-own-docker.mkv) [youtube](https://www.youtube.com/watch?v=vYZKxVkUMvQ).
|
||||||
|
|||||||
Reference in New Issue
Block a user