There is no killer webframework for Erlang. However, N2O looks promising. 
Also, the learning curve: I took me half a day to be good enough in Python and years to learn the basics in Erlang. It is way more complex and the standard library is plagued with inconsistent/messy interfaces. (They say it is because of legacy code support or other BS.) But under the ugly surface lies the hidden beauty: single assignment is great when reading other people's code. Patching several running servers without stopping with one command is thrilling. Or the built-in nice abstractions for distributed programming like rpc:multicall .
There are too many raw edges on a Nokia 301, probably related to new features (which are not many). One can google for them. To me the most annoying is that panorama mode fails to save the photo ~20% of the time on a large and mostly empty SD card. 39 days standby is a lie. Mine barely manages a week of standby on 2G only. Earlier versions of this platform are more robust and seemingly less power hungry. I wish I had bought a 2-3 year old one.
"Racket's interactive mode encourages experimentation, and quick scripts easily compose into larger systems. Small scripts and large systems both benefit from native-code JIT compilation. When a system gets too big to keep in your head, you can add static types."