bramble VS Oat++

I've been looking into Nix a lot lately (but have yet to take the leap - I'll probably start with devshell)

But a couple of projects have come up lately that piqued my interest wrt syntax and alteratives (Since I am not sure about Scheme anymore than Nix (as a langauge) :-)

  * https://github.com/maxmcd/bramble

An alternative to Nix that uses Starlark (python syntax) instead of a purely functional programming language: https://github.com/maxmcd/bramble

I struggled to climb the steep learning curve of Nix/NixOS and wondered what it would be like with a more familiar (to me) syntax.

It's been very rewarding to write. I was able to implement some ideas from the initial Nix paper that aren't present in Nix. Nix is also quite dependent on the use of the /nix/store path, but I was able to allow a user to use almost any path for their build store without sacrificing on the potential for a shared build cache. I also want to have better native support for things like building docker images, among other features.

I'm currently implementing sandboxing and finalizing some of the build structure, but hoping it'll be usable sometime soon.

I looked at oatpp and drogon, which are both great, but feel too high-level for my purposes. I tried drogon and got something working, but it feels like too much for my requirements, as in particular I'd like to slot in my choice of Json and message-body handling. C.f. the simple approach in Crow, which I easily understand and build on.

With the right libraries, C++ could be a good fit for applications that want to expose a fast web API to things that need lots of compute (simulators, for instance) or I/O (interactive editing of large datasets). Projects like Oat++ and Crow give me hope that we might see such an ecosystem develop.

Lots of other options have been mentioned, but I'll throw Oat++ into the mix. I used it for this purpose and it was reasonably painless.

https://github.com/oatpp/oatpp +WASM ;)

cd "some/temp/path/for/repositories" git clone https://github.com/oatpp/oatpp.git cd oatpp mkdir build && cd build cmake .. (sudo) make install

Maybe use something like https://oatpp.io to create a REST API: C++ in the backend with this library to create a REST server, and the JavaScript/TypeScript frontend to ask for the information.

I've used OATPP ( https://github.com/oatpp/oatpp ) which worked nicely for setting up simple rest interfaces. Supports things like swagger & websockets out of the box. It's also on Conan which is nice if you use cmake. I can't speak to it's performance but it has about a 1mb binary size footprint.

As for your web problem, I have only used https://oatpp.io/ in the past but I'm sure there are more frameworks like that on the internet.