Erlang and the Web
I have been spending a lot of time thinking about leveraging Erlang’s concurrency features and OTP in web applications. Right now I don’t believe that any of the available frameworks do that very well. Erlyweb tries to be ‘rails’ for Erlang without really leveraging the features that make Erlang great. Yaws is more a web server then a web app server. It tries to make some amends here by providing things like appmods and yapps but they feel bolted on, and they don’t leverage OTP at all.
This lack of good web support has been an open issue in my mind for some time. I created the tercio project as a starting point to solve this problem back in November or December of last year. It languished for awhile, partly because I had yet to figure out an elegant solution. Well, I think that I finally have. Its the logical conclusion of current web development trends. I am surprised that no one has thought of it yet. The idea is two-fold.
1) Let client side handle the client side 2) Let the server side handle the server side