3 ms·
Interesting. Thanks for the detailed response. When I rank about my current pain points in web development smarter error handling isn't very high on the list, s
by cageface 17y ago
Interesting. Thanks for the detailed response. When I rank about my current pain points in web development smarter error handling isn't very high on the list, so at least for the work I do this isn't a particularly strong selling point. I can imagine for some apps it might be more important though. The ease with which an Erlang stack could support Comet apps might be too.
The area in which I'd really like to see some new ideas is the impedance mismatch between the DB, the business rules, and the HTML user interface. I feel like at least half my code in a typical web app is just glue to make all these layers behave consistently. Any platform that could make that more natural would be very attractive.
- mononcqc 17y agoWell, Erlang has its own database that can store Erlang terms (see mnesia). As you can save some there for the impedance mismatch. Nitrogen itself deals with reducing the differences between your backend code and the frontend. See the demos and their source code for examples: http://nitrogenproject.com/demos http://nitrogenproject.com/demos Erlang also makes it a lot more easier to model stateful applications. I've found the best way to make an active web app with Erlang is just to make a regular application for the command-line (or the Erlang shell), and then add bindings to a web-server. Because every block of code you have is independent, this is really easy to do. It makes every program extremely modular and I've rarely had the concept of 'code reuse' come so easily. Maybe stackless python could be an interesting option under this perspective too, but I never used it for any project.