How do I add ae to my D project with Dub?

Add a dependency on 'ae' or a subpackage in your dub.sdl or dub.json file. Be aware that subpackages like ae.net may have additional dependencies such as OpenSSL, so check the dub.sdl for specifics.

Is ae or vibe.d better for networking in D?

ae offers a broader toolkit with UI and utilities, while vibe.d is more focused on web and networking. Choose ae if you need integrated graphics or promise-based async, but vibe.d might be simpler for pure web apps.

How stable is ae for production use given its versioning?

It's used in production by projects like DFeed, but the lack of stable branches means you must monitor breaking changes closely. The commit messages provide update instructions, but it requires active maintenance.

What's the best way to learn ae if the docs are limited?

Start with the demo programs in the 'demo' directory, examine open-source projects like Digger or DFeed that use ae, and use your editor's go-to-definition feature to explore the source code directly.

How to handle breaking changes when updating ae?

Breaking changes are prefixed with [BREAKING] in commit messages, each including rationale and update steps. Regularly review commit logs and follow the provided instructions to adapt your code.

Does ae support 3D graphics or only 2D?

ae's UI framework is focused on 2D games and graphical applications using SDL and OpenGL. For 3D graphics, you'd need to extend it with other libraries or custom code, as it's not built-in.

Can I use ae without Dub, and how?

Yes, but it's complex. Use recursive compilation with rdmd or dmd -i, or set it up as a git submodule in your project root. The README warns that compiling all files into a single library won't work due to multiple entry points.

ArmageddonEngine — Composable D Library for Networking

What is ArmageddonEngine?

ae (almost everything) is a general-purpose auxiliary library for the D programming language that provides a comprehensive set of tools for networking, UI development, and data manipulation. It solves the problem of fragmented utility code by offering a cohesive, composable collection of modules that work well together while remaining independently usable.

Target Audience

D developers building networked applications, games, or graphical interfaces who need reliable asynchronous networking, cross-platform UI frameworks, and robust utility functions.

Value Proposition

Developers choose ae for its clean composability, comprehensive feature set covering networking to graphics, and proven reliability through use in production projects like DFeed and Digger.

An auxiliary general-purpose D library

Use Cases

Best For

Building asynchronous network servers and clients in D
Creating cross-platform 2D games with SDL and OpenGL
Developing web services and network applications with HTTP/IRC/TLS support
Implementing promise-based asynchronous workflows in D
Processing and manipulating graphical data and images
Building D development tools and build systems

Not Ideal For

Projects demanding strict API stability and versioned releases with long-term support
Teams seeking a lightweight, single-purpose library without additional dependencies
Developers unfamiliar with D or its build systems, especially those not using Dub
Applications requiring advanced 3D graphics or complex UI components beyond basic 2D

Pros & Cons

Pros

Comprehensive Feature Set

Provides a wide range of modules from asynchronous networking to UI frameworks, all designed for composability, as seen in its use for projects like DFeed and Digger.

Asynchronous Networking Power

Includes an event-based networking loop with HTTP, TLS, and IRC support, plus a full Promises/A+ implementation for modern async workflows.

Production-Proven Reliability

Used in multiple production systems such as community WormNET services and D development tools, demonstrating real-world robustness and maturity.

Cross-Platform UI Framework

Offers a 2D game and graphical application framework using SDL and OpenGL, with a working demo in ae.demo.pewpew for practical reference.

Cons

Unstable Versioning Model

Uses commit-based versioning with no stable branches, and breaking changes are frequent and explicitly marked, which can disrupt maintenance and upgrades.

Complex Non-Dub Setup

For projects not using Dub, compilation is cumbersome due to multiple entry points and dependencies, requiring recursive compilation or manual configuration as noted in the README.

Sparse and Implicit Documentation

Relies heavily on DDoc-generated docs and suggests learning from demos or source code, which may slow down onboarding and increase the learning curve.

Frequently Asked Questions

What is ArmageddonEngine?

Target Audience

D developers building networked applications, games, or graphical interfaces who need reliable asynchronous networking, cross-platform UI frameworks, and robust utility functions.

Value Proposition

Developers choose ae for its clean composability, comprehensive feature set covering networking to graphics, and proven reliability through use in production projects like DFeed and Digger.

Use Cases

Best For

Building asynchronous network servers and clients in D
Creating cross-platform 2D games with SDL and OpenGL
Developing web services and network applications with HTTP/IRC/TLS support
Implementing promise-based asynchronous workflows in D
Processing and manipulating graphical data and images
Building D development tools and build systems

Not Ideal For

Projects demanding strict API stability and versioned releases with long-term support
Teams seeking a lightweight, single-purpose library without additional dependencies
Developers unfamiliar with D or its build systems, especially those not using Dub
Applications requiring advanced 3D graphics or complex UI components beyond basic 2D

Pros & Cons

Pros

Comprehensive Feature Set

Provides a wide range of modules from asynchronous networking to UI frameworks, all designed for composability, as seen in its use for projects like DFeed and Digger.

Asynchronous Networking Power

Includes an event-based networking loop with HTTP, TLS, and IRC support, plus a full Promises/A+ implementation for modern async workflows.

Production-Proven Reliability

Used in multiple production systems such as community WormNET services and D development tools, demonstrating real-world robustness and maturity.

Cross-Platform UI Framework

Offers a 2D game and graphical application framework using SDL and OpenGL, with a working demo in ae.demo.pewpew for practical reference.

Cons

Unstable Versioning Model

Uses commit-based versioning with no stable branches, and breaking changes are frequent and explicitly marked, which can disrupt maintenance and upgrades.

Complex Non-Dub Setup

For projects not using Dub, compilation is cumbersome due to multiple entry points and dependencies, requiring recursive compilation or manual configuration as noted in the README.

Sparse and Implicit Documentation

Relies heavily on DDoc-generated docs and suggests learning from demos or source code, which may slow down onboarding and increase the learning curve.

Frequently Asked Questions

ArmageddonEngine

What is ArmageddonEngine?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

ArmageddonEngine

What is ArmageddonEngine?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?