ECS?

[dakom]

@clinuxrulz - I remember you mentioning that you were thinking about a demo using SodiumFRP to power an Entity Component System... can't find it at the moment, curious if you are still thinking along those lines, or maybe even put something together?

[clinuxrulz]

I made a small start, but I've really gotten nowhere with it yet. https://github.com/clinuxrulz/ilc_ecs/tree/master/src

Plus my laptop at home overheated and died. Only got a work machine I can use at work, and its only for work.

[dakom]

Sorry to hear that, hope you get it sorted soon :\

[clinuxrulz]

I've got a old lapping up and going.
Honestly though, my only plan of attack is a Stream of descriptions of scene changes and have other parts of the system work out changes from the current scene plus the description of changes. In that respect ANY imperative entity component system library in existence could be used under the hood would work, and it would make no difference (as long as changes are accumulated and tracked in a Stream).

I have no special attack using a immutable map (immutable ecs), because I've had performance issues in the past with immutable maps which makes me uncomfortable. Just can't compete with mutable maps. I'm happy with immutable link lists, and structs performance wise though.

Experience performance/ram-wise so far:

1. ImmutableMap entitys, ImmutableMap components: bad (too slow)
2. MutableHashMap entitys, MutableHashMap components: bad (too much ram usage)
3. MutableHashMap entitys, MutableTreeMap components: good.

I haven't tried a single map for both entities and components (combined key) yet. I just stopped at option 3, because I was happy with it. Other variations with fixed sized arrays are possible too, given you have a fixed number of component types at the beginning.