Hey.
Thanks for the feedback. I've just implemented a way to edit+repost. About syntax highlighting, it'll be implemented in the following days.
I'll check out the dropdown menus as well.
First of all, I would like to address the 6 distinct features I was talking about in the theoretical introduction. Those 6 features/rules are described in the same way in a book called "Introduction to Scheme". I'm guessing I haven't explained it very well. Basically, what I meant is that those are the rules functional languages should follow in order to be called pure functional languages. I didn't say that that is the case with most languages, nor that this is the case with Haskell or Scheme. I know most of them don't, but that's just a piece of theory.
And yes, I did mean static binding, I apologize, since linking and binding are denoted by the same word in my language.
Next thing, about the algorithms. Fibonacci example was just to show closeness to mathematical notation and I know it's probably the worst way to use recursion because of the O(2^n) time complexity. But, again, complexity was not the point of the example. About the notation, I'm guessing it's just me then. I was a lot more comfortable with pure mathematical notation, as I like things to be formal as much as they can, and that's something that mathematics provide.
The whole point of the post itself was to give a small introduction to functional programming and show off features that may not be available in most imperative languages.
Of course, as I've also said in the outro, I'm not really planning on switching to purely functional languages, I was just trying to say that they can be fun in some situations and for some problem solving. The different way of thinking is what makes it so fun, at least for me.
About higher-order functions, I truly was mistaken, as I've thought that was a thing for functional languages only. Guess I don't have that much experience in the imperative world, as I've never came across them in my line of work.
So please, don't take this article as anti-imperative, as it's most certainly not.
So, tl;dr, I instantly liked functional programming and I wanted to share some features that I liked the most, and haven't seen in imperative way.
I do apologize for misleading/possibly incorrect parts, and I shall edit those in my earliest convenience.