Search Results for "concurrent"

Build powerful reactive, concurrent, and distributed applications more easily. Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala. Actors and Streams let you build systems that scale up, using the resources of a server more efficiently, and out, using multiple servers. Building on the principles of The Reactive Manifesto Akka allows you to write systems that self-heal and stay responsive in the face of failures. ...

...Excellent type inference, so you never need to annotate your code. Supports sources in OCaml (and soon Reason syntax too). Caramel aims to make building type-safe concurrent programs a productive and fun experience. Caramel should let anyone with existing OCaml or Reason experience be up and running without having to relearn the entire language. Caramel strives to integrate with the larger ecosystem of BEAM languages, like Erlang, Elixir, Gleam, Purerl, LFE, and Hamler.

A self-contained and portable build system derived from the traditional 4.4BSD system. It implements Bourne configure script generation, concurrent building and it can compile IDE project files. It is portable to most operating systems and make flavors.

With its WYSIWYG designer and familiar C# programming model, Visual WebGui is the natural choice for Visual Studio developers who want to create enterprise-class HTML5 apps for any mobile device or desktop.

LIME (Less-is-More) is parallel/concurrent programming environment based on C. Internally, it uses XML technology to describe tasks and their dependencies. Externally, it offers the ANSI C99 programming as well as a set of visually-oriented interfaces.

Continuous Integration Engine which allows concurrent building of dependent projects via ant scripts.

Concurrent build systems, such as "make", tend to let the output from the various running processes overrun each other. This makes the result hard to read. There are some solutions that buffer the entire output from each process, and then output only when the process exists. This works fairly well for short processes, such as compilations, but prevents output of progress reports.