"Side effect" is a breakage of referential transparency.
Depending on your model it can be proven.
Electricity consumption won't be a side effect in any reasonable model.
Depending on your model it can be proven.
Electricity consumption won't be a side effect in any reasonable model.
Surely this is a troll...
If fact the latter is better, because it may be somehow enforced by cogen if you code-generate into a language which may, for example, enforce purity or totality.
And the whole story about "REST not being an RPC" or "there is purity/idempotence/whatever in REST because RFC says that GETs are pure/idempotent/whatever" makes very little sense.
At the same time I'm saying that it's total bullshit when someone says that it's not possible to enforce lack of side effects (like in referential transparency) during a remote call.