StrangeLoop

StrangeLoop
Name	StrangeLoop
Status	Defunct (as of 2019)
Genre	Technology conference
Founded	2011
Founders	Alex Miller, Trisha Gee, Jon Gjengset
Location	St. Louis, Missouri
Country	United States
Attendance	~1,000 (annual)
Organized by	Lightbend, Typesafe alumni

StrangeLoop StrangeLoop was an annual technology conference held in St. Louis that focused on programming languages, systems, and software architecture. The event attracted speakers and attendees from organizations such as Google, Facebook, Microsoft, Amazon, and Netflix. It became known for talks connecting topics like functional programming, type theory, distributed computing, concurrency, and language design.

History

The conference was founded in 2011 by a group of technologists including Alex Miller and community figures associated with TypeSafe and Lightbend, emerging from meetup circuits alongside events like LambdaConf and QCon. Over successive years StrangeLoop hosted presenters from venues such as University of Cambridge, MIT, Stanford University, and companies including Google, Facebook, Amazon Web Services, and Microsoft Research. Notable speakers included engineers and researchers who later appeared at O’Reilly Media publications, ACM SIGPLAN symposiums, and collaborations with projects like Apache Kafka and React. The conference ceased regular operation in the late 2010s as organizers shifted efforts toward other community events and workshops linked to Scala and Clojure communities.

Concepts and Definition

StrangeLoop defined itself around intersections of programming languages, compiler construction, type systems, and concurrent computing with an emphasis on practical systems engineering topics such as microservices architecture, event sourcing, and actor model. The program frequently juxtaposed theoretical work from venues like ACM conferences and IEEE symposia with industrial case studies from Twitter, LinkedIn, Spotify, and Uber. Themes often included discussions of lambda calculus, dependent type theory, formal verification, and domain-specific languages as applied to platforms such as JVM and JavaScript ecosystems, alongside emergent topics like WebAssembly.

Mathematical Formalism

Talks at the conference often drew on formal systems from institutions like Princeton University and University of California, Berkeley, citing frameworks such as lambda calculus, category theory, denotational semantics, and operational semantics. Presentations connected these frameworks to practical tools like Haskell, OCaml, Scala, and Rust by demonstrating type-safety proofs, inference algorithms, and proof assistants originating from projects like Coq and Agda. Speakers referenced classic results and authors associated with Alonzo Church, Haskell Curry, Dana Scott, and work published through ACM SIGPLAN and IEEE Computer Society outlets.

Applications and Examples

StrangeLoop featured case studies from a wide array of organizations: real-time streaming at LinkedIn with Apache Kafka, reactive systems at Lightbend using Akka, frontend engineering at Google with AngularJS and React, and systems programming at Mozilla and Microsoft with Rust experiments. Workshops and talks explored deploying microservices architecture at Netflix scale, using event sourcing in fintech at Goldman Sachs, and leveraging type systems for safety in embedded systems at ARM. Demonstrations included integrations with Docker, Kubernetes, and language runtimes for JVM, CLR, and Node.js.

Related Theories and Extensions

Content intersected with research and communities around functional programming movements such as Haskell and Clojure, runtime and tooling developments like JVM evolution, and language work in TypeScript. Extensions discussed at the conference included connections to category theory applications in software design, gradual typing research as pursued by teams at Google and Microsoft Research, and formal-methods adoption exemplified by SPARK and verification efforts in Ada contexts. Cross-pollination occurred with academic conferences like POPL, ICFP, and PLDI.

Criticisms and Open Problems

Critics noted that the conference could skew toward technology hype cycles represented by companies such as Facebook and Uber, sometimes privileging industry case studies over rigorous peer-reviewed outcomes typical of ACM publications. Open problems highlighted by speakers included bridging gaps between proof-carrying code research from institutions like Carnegie Mellon University and production deployments at Amazon scale, reconciling concurrency models across languages like Erlang and Go, and improving interoperation between type theory tools such as Coq and mainstream engineering toolchains. Ongoing discourse continued in related meetups, journals, and symposia including ACM SIGPLAN events and workshops tied to LambdaConf and regional developer conferences.

Category:Technology conferences