Erlang is getting too big

[Vlad Dumitrescu]

From: "Thomas Lindgren"
> - get rid of strict and/or in expressions and move
> andalso/orelse to "and"/"or". This just seems to be a
> bug cast in stone.
>
> - write guards as arbitrarily nested (G1,G2) and
> (G1;G2) and drop the and/or-syntax in guards.
>
> All of these get rid of unnecessary complexity of
> Erlang.

Maybe "get rid of" is too much, considering backwards compatibility, but these
could at least be *strongly* recommended in the Style Guidelines and at the
courses?

BTW, where did the style guildelines go? They are only present on the website -
shouldn't they be part of the docs?

regards,
Vlad