On Jul 20, 2012, at 11:03 AM, shawn wilson wrote: > (disclaimer: totally ot and oppinion) that said, i dislike having sql, > regex, tt, js, html, css, and perl in a project. i can get rid of one > by using nodejs and another by using a json nosql db. though, these > are new and perl has had 20 years of developers trying to make it work > right.
I agree, that's just a messy approach. I've mentioned before that there ought to be Perl runtime for the client side, but that seems to be a pretty stupid idea because no one else liked it ;) I still don't use sql in the apps I've made. I haven't run into a desperate need for it. The thing I think many developers ignore is that if you know where the data you want to use resides (the path to the file), you really can't get it much faster than opening and reading the file (using the system B-tree). I don't use Template Toolkit. To me, calls to my perl code that are embedded in HTML is just the opposite of putting html in my perl code. It adds complexity that I don't want. I use HTML Template instead. It's simple and straight forward. I struggle with JS, and CSS, but I'm getting a little better with both. I recently got Dreamweaver 5.5 and that's helped a lot with applying CSS. I've been using the Prototype JS libraries for a bit now, and they're pretty easy to figure out, but I still struggle and fumble my way along with them and JS in general. There is a lot to be said for keeping things simple. If you're one guy coding perl, js, css, and html for an app, you've already got too much to do. Bill -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
