Search Results for "linux utilities"

Scala.js React wraps Facebook React for Scala.js with a strong emphasis on type safety and functional idioms. It provides a typed virtual DOM interface, reusable components, hooks, and utilities for routing, testing, SSR, and performance profiling, all aligned with Cats, Cats Effect, and Monocle ecosystems.

Ammonite is a modern Scala REPL and scripting tool designed to give Scala users a more interactive and flexible REPL experience and to free them from heavyweight project boilerplate. It provides syntax‐highlighting, multiline editing, auto‐completion, and dynamic importing of dependencies (using a magic import syntax like import $ivy…). Instead of having to set up an sbt project for many small tasks, one can write Scala scripts (with .sc extension) and run them directly, with Ammonite...

Scalaz is a foundational functional-programming library for Scala that provides type classes, data types, and syntax to write pure, composable code. It implements classic abstractions such as Functor, Applicative, Monad, Monoid, Foldable, and Traverse, along with powerful transformers (ReaderT, StateT, WriterT, OptionT, and more) to structure effects. The library offers rich data structures—\/ (disjunction), Validation, NonEmptyList, IList, and Free—that help model errors, invariants, and...

Twitter Util is a collection of utility libraries used at Twitter, covering concurrency (Futures, Promises), timing, caching, I/O helpers, validation, stats collection, and Scala–Java interoperability. Designed for reliability and efficiency in high-scale systems.

Assorted projects. General-purpose libraries for Python, C++, Scala, bash, and others. Meta-programming tools. System utilities. UI components. Web APIs. Configuration files. Benchmarks. Programming competition entries. And much more.

Spray is a suite of Scala libraries built on top of Akka that offers a modular, asynchronous, and non-blocking toolkit for building and consuming RESTful and HTTP services. The core philosophy behind Spray is that it should act as a “library” for integration and HTTP layers, not as a full application framework—it gives you the building blocks to handle HTTP and REST but doesn’t impose heavy structure. It includes modules for low-level HTTP I/O, routing, client and server APIs, HTTP model...