4 ms·

Hello HN, I'm the guy who wrote the LYSE site! I Hope you'll enjoy it :) At least I have fun writing and drawing for it. I'll always be fixing mistakes and tec

Hello HN, I'm the guy who wrote the LYSE site! I Hope you'll enjoy it :) At least I have fun writing and drawing for it. I'll always be fixing mistakes and technical points that were not caught in the reviewing process, so it's much appreciated if you give me comments and criticism. Feel free to speak your mind, I collect these ideas and build on them.

olliesaunders 17y ago
Did you do the Haskell one as well?
- mattyb 17y ago
  http://news.ycombinator.com/item?id=771200 http://news.ycombinator.com/item?id=771200
callahad 17y ago
Thank you for writing LYSE! This was my first exposure to the syntax and design behind Erlang, and it's really interesting to see the influence of Prolog shining through. I'm looking forward to the future chapters!
- mononcqc 17y ago
  The Syntax is the first hard step to go over for many people. Erlang is hardly what you'd call an easy to read language, except if you've used functional languages before. The recursion and pattern matching are relatively uncommon (and different from what you can get from Haskell, too), with naming conventions and atoms also a bit weird at first. Once you get used to it, it becomes very easy to read and concise language. Once you know it. (like anything else.) The syntax turns off a lot of people. It's a shame because even if you might never use Erlang for personal or real-world project (although it's very well done for that), you'll see a different way to do error management and possibly to organize code, depending on what you've done before. It's worth learning.
keenerd 17y ago
You have it under a fairly tight CC license. Is my automatically ripped PDF version legit enough? http://kmkeen.com/mirror/lys_erlang_fgg.pdf http://kmkeen.com/mirror/lys_erlang_fgg.pdf It was an enjoyable read.
- mononcqc 17y ago
  I might eventually relax the license. I'm a permissive guy and don't mind people sending links, copying or printing stuff, but I'd like to be notified about distribution (I would mainly allow non-commercial stuff, educational and archival purposes, fair use, etc), mainly because I want feedback to make sure the content is right. Some people caught simple arithmetic errors in my stuff already; it would suck to have distributed stuff being wrong because I couldn't update it. At least I can try and notify people who distributed it for some reason. Your version is legit enough for me to ask you if I can link it in the FAQ under the question about books :) What do you think? (I can host it, of course)
  - keenerd 17y ago
    You should never have to ask to link something on the internet! I'd prefer to host it, mainly because my technique is pretty crude at this point, and I do intend to improve the quality.
    - Deestan 17y ago
      > You should never have to ask to link something on the internet! It is considered good form to ask before linking if there is the possibility that you generate a ton of traffic to someone's personal server. It may not be configured with high load in mind, or it may have a small bandwidth quota.

olliesaunders 17y ago

Did you do the Haskell one as well?

mattyb 17y ago
http://news.ycombinator.com/item?id=771200 http://news.ycombinator.com/item?id=771200

callahad 17y ago

Thank you for writing LYSE! This was my first exposure to the syntax and design behind Erlang, and it's really interesting to see the influence of Prolog shining through. I'm looking forward to the future chapters!

mononcqc 17y ago
The Syntax is the first hard step to go over for many people. Erlang is hardly what you'd call an easy to read language, except if you've used functional languages before. The recursion and pattern matching are relatively uncommon (and different from what you can get from Haskell, too), with naming conventions and atoms also a bit weird at first. Once you get used to it, it becomes very easy to read and concise language. Once you know it. (like anything else.) The syntax turns off a lot of people. It's a shame because even if you might never use Erlang for personal or real-world project (although it's very well done for that), you'll see a different way to do error management and possibly to organize code, depending on what you've done before. It's worth learning.

keenerd 17y ago

You have it under a fairly tight CC license. Is my automatically ripped PDF version legit enough? http://kmkeen.com/mirror/lys_erlang_fgg.pdf http://kmkeen.com/mirror/lys_erlang_fgg.pdf It was an enjoyable read.

mononcqc 17y ago
I might eventually relax the license. I'm a permissive guy and don't mind people sending links, copying or printing stuff, but I'd like to be notified about distribution (I would mainly allow non-commercial stuff, educational and archival purposes, fair use, etc), mainly because I want feedback to make sure the content is right. Some people caught simple arithmetic errors in my stuff already; it would suck to have distributed stuff being wrong because I couldn't update it. At least I can try and notify people who distributed it for some reason. Your version is legit enough for me to ask you if I can link it in the FAQ under the question about books :) What do you think? (I can host it, of course)
- keenerd 17y ago
  You should never have to ask to link something on the internet! I'd prefer to host it, mainly because my technique is pretty crude at this point, and I do intend to improve the quality.
  - Deestan 17y ago
    > You should never have to ask to link something on the internet! It is considered good form to ask before linking if there is the possibility that you generate a ton of traffic to someone's personal server. It may not be configured with high load in mind, or it may have a small bandwidth quota.