Multithreaded library or Multithreaded application?

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Zigi - Close all those tabs. Zigi will handle your updates.
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Truly a developer’s best friend
  • tokio

    A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

    Futures work very differently than threads: They enable cooperative multitasking. It's a really complex topic to explain. The result is that if you use futures, you need an async runtime such as tokio, and all the libraries you use for IO need to work with Futures. There are two ways how IO can be implemented: In a blocking way (which works well with threads managed by the operating way) or in an asynchronous way (which works well with an async runtime). Because pcap, the library you use, isn't asynchronous, using Futures doesn't make sense.

  • Zigi

    Close all those tabs. Zigi will handle your updates.. Zigi monitors Jira and GitHub updates, pings you when PRs need approval and lets you take fast actions - all directly from Slack! Plus it reduces cycle time by up to 75%.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts