Well, perhaps my opinion doesn't have a lot of value (I only check a few portions of code and programming it's not my main activity) but, anyway:
- Certanly, How OACS manages CSS is a problem. I'm not sure what it's the best solution, but our approach now, at least, is modular and, for recurrent users (because of the cache) works quite well. But yes, first time, I had to load a lot of files.
- It's impossible to install OACS in 20 hours (complexity and well trained people), so my students were always happy with LAMP, but ..., it's not fare compare a typical LAMP app with OACS. And for me, Aolserver and Postgres is easy. TCL, OR AOLServer API it's not cool (neither Emacs), but works very well (It solve my problems quickly)
But, what is the future? I miss some things, some bugs that remain a lot of time, and a lot of distributed effort. But I think it's a common problem of a complex and mature project in open source world (like OACS).
But. sure. we have to learn of other approaches
