980 karma · joined September 4, 2007
The statement "function composition is a degenerate case of the Decorator pattern" in the blog is bizarre to me. OO languages like Java have to resort to the Decorator pattern to handle their lack of composibility; that seems far more degenerate than a language that supports this kind of composition without hacks.
Also this article is 2.5 years old.
And, here, I assumed that by emphasizing results he meant getting home around 5...
So what does this mean for Yesod? A lot, actually. FP Complete will be bringing Haskell to commercial users, and Yesod will be a big part of that. FP Complete is very supportive of the entire open source Haskell community, and will be contributing directly to it. I will continue fully in my role as maintainer and lead developer for Yesod. This move to FP Complete will not be taking my focus off of the open source community at all. On the contrary, I expect greater opportunities to be able to make contributions back.
It's not like Valve or Blizzard should own the DOTA trademark.
My impression of Java these days is to start with the "right" thing (allocate as needed, etc) and not to overly concern yourself with performance until it becomes an issue. There are certainly situations where allocating lots of objects (say billions or, maybe, millions) causes performance issues, but creating object pools to preemptively avoid that is a lot of extra work that may not be worth it.