Remix.run Logo
▲ txdv 28 minutes ago

Load, scale?

Biggest pain point? Biggest win?

▲netbioserror 16 minutes ago | parent [-]

It has a scoped responsibility, does mostly compute and data processing. Invoked by a PHP backend, single-threaded, we get parallelism at invocation rather than internally. So we can saturate server threads optionally if we need to.

Biggest win: Single-owner scoped lifetimes by default with no annotations plus expression-oriented value semantics makes it eminently readable. Basically no memory semantics, all business logic. (It does processing of proprietary binary data including a lot of math.) Extraordinarily easy to maintain, refactor, add features. Valgrind confirms no orphaned blocks in some of our biggest test scenarios, it's impressive. Full compile-time evaluation is nice too, easy to slurp a whole file at compile-time and have it accessible in a normal binding, and writing generic procedures is obvious and simple.

Biggest pain point: Hard to say, the only friction I've really ever run into is its weak tooling. I just use Make for build scripting (invoking the compiler directly instead of using Nimble) and Sublime's built-in features for refactoring. It's small enough that print-debugging works, but I occasionally dip into FlameGraph. Nimsuggest has some...dealbreaking quirks, but successors are in the works.