Difference between revisions of "Talk:Euler problems"

From HaskellWiki
Jump to: navigation, search
 
(These pages should NOT be deleted)
Line 18: Line 18:
   
 
Keep it in the problem threads.
 
Keep it in the problem threads.
  +
  +
----
  +
  +
I disagree. These are clearly marked as "spoilers". Anyone
  +
who wants to participate in Project Euler and enjoy its
  +
benefits knows that they should not peek at these solutions.
  +
  +
On the other hand, this problem space is perfect for
  +
illustrating the power of Haskell, and for providing
  +
excellent examples of how to "think in Haskell".
  +
I would refer anyone thinking of learning Haskell to
  +
these pages - with the warning that they might
  +
first want to solve all of the problems in their
  +
current favorite programming language.
  +
  +
My guess is that many people would look at the
  +
first few solutions, become hooked, and then
  +
redo the rest of them on their own in Haskell
  +
without peeking!

Revision as of 10:32, 30 September 2007

These pages must be deleted.

They are not in the spirit of Project Euler.

They are ruining the fun of problems and the fun of climbing up the ladder.

I am aware that whoever posted this is probably smart and would like us all to know.

Meanwhile:

RULE #1 of Project Euler:

You do not discuss Project Euler solutions.

RULE #2 of Project Euler:

You do not discuss Project Euler solutions.

Keep it in the problem threads.


I disagree. These are clearly marked as "spoilers". Anyone who wants to participate in Project Euler and enjoy its benefits knows that they should not peek at these solutions.

On the other hand, this problem space is perfect for illustrating the power of Haskell, and for providing excellent examples of how to "think in Haskell". I would refer anyone thinking of learning Haskell to these pages - with the warning that they might first want to solve all of the problems in their current favorite programming language.

My guess is that many people would look at the first few solutions, become hooked, and then redo the rest of them on their own in Haskell without peeking!