jfl

4 ms·

1. 1.▲
   by jfl 17y ago

   We have to agree to disagree. Peace.
2. 2.▲
   by jfl 17y ago

   "A caller of a function in an imperative environment cannot assume anything about the scope of that function's access of mutable state within the program" This really doesn't make sense. main() { A a = new A(); f(); ... } the caller main
3. 3.▲
   by jfl 17y ago

   Actually, my webapps are full of threads. Again, Imperative style is not the wrong way, and FP the right way. They are just different. Why not let people find their own way ? Just give the information they need to make up their mind. And wh
4. 4.▲
   by jfl 17y ago

   All my methods take just a few argument, I learned to design carefully the state of my programs and manage adequatly how function access that state. Imperative programming works for me (and many others). You say I am doing it wrong and want