4 ms·
That looks like the Haskell tutorials and trainings I've seen. At the end of it: 1) you didn't learn to read or write text to the console. 2) You are unable t
by user5994461 10y ago
That looks like the Haskell tutorials and trainings I've seen.
At the end of it: 1) you didn't learn to read or write text to the console. 2) You are unable to make any useful program, let alone a hello world.
This kind of non-practical training materials is a recurring issue with functional languages.
- tom_mellior 10y agoWell, it never claims to teach you all of the language; it tries to show off some neat parts. Articles like that often don't go into the details of I/O. Especially articles about languages with REPLs, which have much less need for that since they allow you to interact with your program more directly. (But it's true that many other Prolog resources also ignore I/O.)
- mickronome 10y agoThat drives me up the wall too at times. It's a recurring theme when teaching languages to do it through something the author (maybe implicitly) consider a good fit, something that emphasise the beauty of that particular language. Might be good while you are learning your first language, maybe ? This explains the IO/side effect heavy imperative tutorials, the structure rich OO tutorials, the 'algorithmic' FP ones, etc. Turned upside down quite clearly tells you which language is strong in a particular area, and complicated/awkward in another. Myself, I prefer to start with the ugly parts, they contain much more information about the tradeoffs and focus of any particular language.