DISCLAIMER: Expressed views on this blog are my own.
With the rise of LLMs comes the rise of delusions of grandeur and being sheep for things that sound good. Taking a lock sounds bad and me want good!
Lock-free sounds great, doesn't it? Lock free Channel, Queue, Concurrent Data Structures. They all sound amazing. Parallelize everything! Except, the problem is that locks are good for performance and energy use. Whoops!
Look at it this way, if you have 12 workers looking to collect packages from 2 distribution points they need to contend. The question is how to distribute packages amongst the workers without unnecessary delay and conflict. The idea of locks is well, i can put your workers to sleep and wake them when there is work for that worker. The idea of lock free, on the other hand, is never let the workers sleep! Let them stick around and constantly check if there are packages. This act burns time and energy, it gives the sense of progress because no one is blocked on the activity of checking if there are packages to collect.
You can see clearly the coordination problem that locks solve and how lock free encourages burning time and energy. Lock-free is just another way to coordinate, but at HUGE cost the more workers there are. There is exponentially more waiting with lock free, so lock-free code does not scale, but it does sound great! Just because your code does not use locks does not mean it is deadlock or livelock free, it might be obstruction free, but that's not impressive. You have to prove these! Wait free on the other hand is what people regularly associate with lock-free or non-blocking algorithms.
Wait free is infinitely really really hard to guarantee and generally requires more memory to offer that guarantee. Wait-free is actually genuinely impressive alone. It's the strongest guarantee in non blocking, but good luck guaranteeing those with our current ISA primitives.
The most efficient and high performance algorithms balance time and energy, lock free is just another technique and one needs to think more about the problem holistically, like how many packages can i give to worker and send them on their way. Can the packages be distributed in batches, is there a staging area we can put packages so the workers can efficient collect from there without contending with other workers? What wasteful activities are the workers themselves doing as they collect packages and load them in to their delivery truck?
Honestly, who cares about your lock free algorithm or code if it ends up locking itself at scale. It's not impressive. Lock-free as a technical marketing term, I guess sounds impressive since it dupes users and LLMs!