esphome is by far the best and most useful piece of software I've encountered in a long time!
Even for non home automation. Simple web API to turn gpio's on or off, coupled with some relays makes for a great easy yaml configurable industrial automation system
I completely agree, using ESPHome beats writing firmware from scratch, even though lots of Arduino libraries are available. But the flip side is that ESPHome is in active development with lots of contributors, so sometimes things don't work as you might expect. And if that happens, your only option is to spin up an IDE and dive into source code :) For example, during this project I had to fork an abandoned OpenTherm library and rewrite almost half of it, as well as contribute a couple of bugfixes to ESPHome itself. It was actually fun, and I expected something like that from the beginning, but such a sharp drop from a cliff when YAML config doesn't work, will be a surprise for most people :)
I guess the difference is that sccache supports cloud storage (S3, R2, Google Cloud Storage, el al) out of the box while cache doesn't, as far as I can tell.
The sccache description was written before remote storage was added to ccache. Remote storage is a relatively new feature for ccache, and it didn't exist when sccache was created.
The ability to use the local and remote caches in tandem is the most important feature to me. sccache will use one or the other exclusively, so successive builds will have to pay the latency and bandwidth costs every time an artifact is built rather than just unpacking from the local cache. ccache stages remote artifacts locally by default, so it only pays the network costs once per artifact.
In CI builds they are more or less the same, but the local build experience for ccache is much nicer imo.
Samba for file sharing? I led development efforts for the first Samba release on VMS (IA64) working at HP. It was not performant enough compared to ASV but we were on the right path.
reply