I had been thinking of building a PIs cluster for a while now and I was looking with interest at the turingpi board project [1] they are taking preorders for the second batch if anyone is interested. But I would like nodes with more than 1GB of RAM so I guess I'll have to wait for that.
Of course that's only the theory...
Here are my answers for both:
Pi cluster: meshing won't save any additional wires here since there is already a wireless bridge set up (between the black Mikrotik device pictured, and an off-camera Mikrotik wireless router.) I chose to wire the cluster simply to guarantee a reliable connection within the cluster. You can absolutely use a Raspberry Pi over WiFi without an Ethernet cable, it would just be a less reliable connection (jitter, congestion), and then of course it would have to be powered conventionally rather than via PoE.
General 802.11s meshing: If all you want is fewer network cabling in your home specifically between switches and access points, then it could certainly help. However, the best choice network-wise is almost always a proper deployment with a central router and several APs (broadcasting the same SSID) wired back to it.
I see their project as a fun hobby. It's very fun to put a lot of tiny low-power computers together in a cluster and learn as you go. Sure, you should take into account the limitations, but you should not feel discouraged if all you want to do is to have fun, learn and build something that is quite unique.
In terms of understanding distributed computing and the failure modes that can occur, the GP's approach is definitely better. If you build distributed systems only testing them through virtualisation, you'll run into all sorts of issues that come from adding real world constraints that are otherwise masked through the virtualised abstraction.
Even the tone itself is non-constructive, all wrong and off-putting.
I'm sure you can understand that someone who bolts on computers over WiFi and praises a 100MB/s connection is not aiming for performance.
This is not what HN is all about.
Speaking of that, happy to see LXD on the front page. Its not as hyped as Docker but I really like it.
One small thing they're nice for is if you want to play with a cluster (e.g. nomad, kubernetes, whatever) on a budget. Of course it's not going to be great bang for buck just for performance but if you're trying out some distributed computing it's nice to be working to real limitations, network and RAM and particular.
I was really impressed that I got line speed Ethernet between the Pis, 112MB/s doing a wget of a 1G file from one to another. Things have improved a lot since the original Raspberry Pi from 2012.
I need to figure out how to get the 8th Pi working though, since I'm using one of the PoE ports to power a Mikrotik that I'm using as a wireless bridge onto my existing broadcast domain. Technically I don't need the bridge, since each Pi can connect to my wireless AP over 5GHz 802.11ac just fine, but it feels nicer to funnel upstream data through one point. More importantly, it reduces WiFi collisions since there wouldn't be 8 devices broadcasting simultaneously and interfereing with each other (especially at those close distances) if they all needed to download something from the Internet at the same time... like a Docker image for a Kubernetes deployment :)