factoriolab VS semver-trick

yes, you can start building the house from the roof, as you suggest, or you can use some kind of planner, and start building from the ground.

factoriolab.github.io - my favorite, but if you need a tool for layout, not a calculator - I'm using my imagination

I can recommend https://factoriolab.github.io

You mean the best one, so factoriolab[https://factoriolab.github.io ] aren't you?

There are also online calculators for this: https://factoriolab.github.io

https://factoriolab.github.io/ is pretty similar, but also supports mods and some more options

You might be interested in checking out factoriolab or kirkmcdonald. Both tools work great for planning the amount of machines needed to make a specific factory.

FactorioLab has recipes from several popular mods, including SE, K2, SE+K2, Py, PyAL, A&B, SeaBlock and more.

I mostly make extensive use of factoriolab online calculator. How much planning I'm doing also changes throughout the game:

There's a production chain calculator called FactorioLab which already supports several games beyond just Factorio, and had some discussion about supporting Captain of Industry, but doesn't yet. I would guess there hasn't been a lot of work into it yet because CoI is still relatively early, and has had some significant recipe changes.

A library author concerned about this can use the semver trick. TL;DR: if your current version is 0.42, you can do a 1.0 release, then do a 0.43 release that depends upon your 1.0 release and re-exports all the symbols.

I mean for all the parts of the standard library that do not change, one could presumably use the semver-trick.

The semver trick can help with libraries at least when they go to unify the ecosystem. Release new versions that replicate previous APIs in a compatible way while moving to the standard library implementation.

It's called the "semver-trick" [1].

[1]: https://github.com/dtolnay/semver-trick

The JVM is 114MiB on my machine. A near-minimal ggez program in debug mode is about 100MiB,¹ and ggez is small for a Rust application library. When you start getting into the 300s of dependencies (i.e. every time I've ever got beyond a trivial desktop application), you're lucky if your release build is less than 100MiB.

Sure, I could probably halve that by forking every dependency so they aren't duplicating versions, but that's a lot of work. (It's a shame Rust doesn't let you do conditional compilation based on dependency versions, or this would be a lot easier. As it is, we have to resort to the Semver trick: https://github.com/dtolnay/semver-trick/ — not that many people do that, so it's functionally useless.)

¹: I can get it down to around 8MiB with release mode, lto etc., but that significantly increases the build time and only about halves the weight of the intermediate build files.

The semver issue might be possible to mitigate using the semver trick, but at that point it's probably simpler to just get your patches merged upstream.

When I hear about the libcpocalypse I think about the semver trick: https://github.com/dtolnay/semver-trick

From a language/cargo point of view, there is no issue. But the issue arises when you look at the ecosystem. It's really well explained in the semver-trick readme. semver-trick isn't a complete solution to the problem, but rather equivalent to a band-aid (or a hack).

And on top of all his crates, he's also the origin of the SemVer trick.