3 ms·
The problem with more languages is that you fragment the community. Maybe it'd indeed be nice to use Ruby instead of Javascript for a project or two. But I don'
by lhorie 16y ago
The problem with more languages is that you fragment the community. Maybe it'd indeed be nice to use Ruby instead of Javascript for a project or two. But I don't think something like jQuery would be simple to port over and maintain (especially considering that the mobile landscape is even more nightmarish than desktop cross browser support). And what about plugins?
And what happens when you get the odd client that wants you to do some work for them and it so happens they are using I don't know, PHP or Java on the client-side? (or CL or Scheme, if that's your cup of coffee)
- pedrocr 16y agoShould we standardize on a single language for the server-side as well?
- lhorie 16y agoThe server-side is a good example of the fragmentation I mentioned. There are classes of projects that are hopelessly redundant (e.g. minimalist MVC frameworks), and classes of projects that only exist/work in some languages for various reasons (e.g. async MySQL APIs). In an ideal world, I'd prefer if there weren't so many languages that do essentially the same thing with different syntaxes, but then again, standardization in itself is its own little can of worms (the short story being that it involves a lot of politics).