3 ms·
The two reasons javascript is not widespread on the server are: 1. limited database access libraries, there are no standard libraries for talking to mysql/post
by olefoo 18y ago
The two reasons javascript is not widespread on the server are:
1. limited database access libraries, there are no standard libraries for talking to mysql/postgres/oracle/sybase/mssql
2. lack of namespace support in the language itself, which means that you can't rely on external code to not step on your variables.
Also there's a minor usability issue with using the same code in two different environments; the server side and the client-side are not the same and confusing the two can introduce whole new classes of bugs and security holes. Not that anyone here would ever lose track of where the file they were working on was supposed be run.
- SwellJoe 18y agoDefinitely agree on point 1, though I think it might work itself out in surprising ways. CouchDB speaks JSON natively, for example. On 2, there are solutions to this problem based on closures, and basic politeness (YUI uses the YAHOO. prefix, while ExtJS uses Ext., and they can co-exist in one browser). It's not perfect. I'd like to see Perl-style package name spaces, or similar--nothing obtuse like the new PHP namespace support--just very concise and simple but powerful. I, personally, don't think Java style encapsulation and object border defense is all that important...but maybe enterprise users will (though Perl does OK in the stodgy banking and finance world, so it shouldn't be too scary for them).