4 ms·

> Why don't you wait till you have more data before wasting all our time with stuff like this? What's the rush? I used the opportunity of your reliability fail

> Why don't you wait till you have more data before wasting all our time with stuff like this? What's the rush? I used the opportunity of your reliability failure to make a larger point about reliable software. I admit was deliberately provocative and terse in the posting, but I have futher clarified things in the comments. I thought about writing a long, detailed, well balance article about this. But that wasn't going to happen, I don't have the time. But then I thought why not just write what I think, but not everything I think? So I did. Sorry, I might be completely wrong about the source of your problems, I am definitely theorizing as to what you are seeing and I don't think I've implied otherwise. But I will say these are the sorts of things that crop up again and again in Java and other GC'd mutable state languages. Good luck debugging the problem.

Hexstream 19y ago
"I used the opportunity of your reliability failure to make a larger point about reliable software." Your argument construction is not very reliable either. You're basing "large points about reliable software" on... on what exactly? You can't overgeneralize like that, at least not while remaining convincing.
brlewis 19y ago
A lot of the buzz around Lisp web applications does relate to mutable state accomplished through continuations, but that's not a requisite to using Lisp, nor is it the only advantage to using Lisp. I manage state via relational databases, and haven't had to deal with any memory-leak bugs. I even found it easy to prevent leaking of database connections. Mutation is definitely optional. A lot of people even still count Lisp dialects among the functional languages.