From: Michael Sperber <sperber@deinprogramm.de>
To: caml-list@inria.fr
Subject: [Caml-list] 2nd Call for Participation: ´Virtual BOB 2022 (March 11)
Date: Mon, 21 Feb 2022 16:39:36 +0100 [thread overview]
Message-ID: <y9l7d9o44av.fsf@valmont.fritz.box> (raw)
=========================================================================
BOB 2022
Conference
“What happens if we simply use what’s best?”
March 11, 2022, online
0100+UTC
https://bobkonf.de/2022/
Program: https://bobkonf.de/2022/program.html
Registration: https://bobkonf.de/2022/program.html
=========================================================================
BOB conference is a place for developers, architects, and decision-makers
to explore technologies beyond the mainstream in software development
and to find the best tools available to software developers today. Our
goal is for all participants of BOB to return home with new insights
that enable them to improve their own software development
experience.
The program features 14 talks and 8 tutorials on current topics:
https://bobkonf.de/2022/program.html
The subject range includes functional programming, effects,
distributed programming, formal methods, generative art, event-driven
systems, the human brain, Haskell, Python, Scala, Lua, Clojure,
Erlang, Nix, and others.
Derek Dreyer will give the keynote talk.
Due to COVID-related risks, BOB will take place online, entirely
within a Gather Town virtual world. We've placed special emphasis on
enabling social, casual interaction, in addition to our stellar
program.
Registration is open - student tickets are €10, regular tickets are
€30. As always, grants are available for members of groups
underrepresented in tech:
https://bobkonf.de/2022/program.html
reply other threads:[~2022-02-21 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y9l7d9o44av.fsf@valmont.fritz.box \
--to=sperber@deinprogramm.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox