durable-php VS nimble

That's a really clean implementation. And the shares are used to resolve authorization here [1], right?

Two things that we're solving for at Oso is: making it easier for multiple teams to collaborate on permissions (which we solve by having a declarative language), and solving the list filtering problem (as talked about in the post).

If you don't need either of those two things and are happy with a DIY approach, what you've shared would work great IMO. If you packaged that up as a standalone solution, I could see a lot of people getting value from it!

[1] https://github.com/bottledcode/durable-php/blob/3ad509fcdbb3...

Heh. https://github.com/bottledcode/durable-php is a semi-faithful php port of Orleans, borrowing some ideas from similar things too. I’ve actually been working on some really neat FFI things for this the past few weeks.

It’s fun.

Durable php: https://github.com/bottledcode/durable-php based off of C# durable functions.

The way I've successfully used event sourcing was to think of it like a WAL where you are basically building up a HashMap. (This is how DurablePHP works -- https://github.com/bottledcode/durable-php -- if you are interested) Replaying should result in the exact same HashMap every single time, any side-effects only happen once.

I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly).

At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language.

Might try dusting it off for some AoC puzzles this year :)

nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.

I meant it's unfortunate that Nimble has no standard system-wide library management. It's one of the mains thing holding Nim back from being more prevalent in the Linux sphere in my opinion.

`nimble` is the package manager for the programming language `nim` [1].

From [2], we can see that `nimble scss` simply generates the CSS files for the frontend.

The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`.

[1]: https://github.com/nim-lang/nimble

[2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble

Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which introduces lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible — a lot of much appreciated hard work has gone into it, and it's been a real workhorse — but some days it feels like a big ball and chain.

[1] https://github.com/nim-lang/nimble#nimble

[2] https://github.com/status-im/nimbus-build-system

So you wouldn't have a problem with a package manager where the configuration is in the same language, such as Nimble?

if you structure your project with nimble (which can be be used for both libraries and applications) you can use nimble build and nimble run. While I do use nimble for managing dependencies for projects I don't use these commands that often while developing, e.g. because I'm working on a single test or something like that.

Having similar syntax to Ruby makes it easier to port Ruby code to Crystal (ex: digest-crc -> digest-crc.cr). The Crystal stdlib is very complete and they have a growing "shards" ecosystem, roughly the same age as Rust's https://crates.io or Nim's nimble. You should look into Crystal again.