Skip to main content
6 events
when toggle format what by license comment
Apr 22, 2012 at 16:49 comment added Giorgio @Mason Wheeler: From a functional point of view, having a shared state is only useful for optimization purposes: copying values around takes too much time and memory, so you share a data object to avoid unneeded copying. But enforcing a shared state as a rule from the beginning is a kind of premature optimization.
Apr 22, 2012 at 16:47 comment added Giorgio @brad clawsie: I think the whole issue of controlling side-effects in FP can serve to make coding much more productive: it takes longer to write but less time to fix. Unfortunately one has to put quite some effort into learning first, and lots of programmers do not have this long-term thinking: things must get done quickly. There is no time to do it properly the first time, but there is always time to debug and fix it later. :-)
Apr 22, 2012 at 16:42 comment added Giorgio @Mason Wheeler: "We don't want interesting new ways to assess the impact of state on our code." Instead, we prefer to spend a week tracking down a very nasty bug due to an unwanted side-effect (I speak from personal experience).
Jan 3, 2011 at 17:24 comment added j_random_hacker The Camry I drive has its problems, but it doesn't require me to constantly check under the hood for space leaks. Haskell is more like a language that looks like an F1 car, but can't actually do high revs for a sustained period of time. :-P
Dec 27, 2010 at 19:48 comment added Mason Wheeler I think your first paragraph describes exactly what's wrong with the FP mindset. We don't want "interesting new ways to assess the impact of state on our code." What does that even mean?!? We just want the state to be there and easily accessible because we need it to actually get things done.
Oct 28, 2010 at 22:04 history answered Brad Clawsie CC BY-SA 2.5