By and large you can ignore laziness without issue. Multi-threading is, ironically, one of the first places you might see an issue as you must guarantee where e

By and large you can ignore laziness without issue. Multi-threading is, ironically, one of the first places you might see an issue as you must guarantee where evaluation occurs and how far. Other than that the major risk is of a space leak. In a web service model you generally won't write the sever or the database connection and therefore will be masked from long-running memory hog computations.