Best Practices in Javascript Library Design

I guess the idea is that these are things that are so natural you don't have to document them - they should still be in the documentation though, e.g. for people who write their own plugins.

what a video smooth work..time has no problem does it

Im just learning web-development, but I have experience with C++ and C#. I have always stayed away from Java because I figured C# was supposed to kill Java. My question is: Since JavaScript has been around forever, is there any other language that is better for client-side scripting??

Java & Javascript are different. Javascript was never well supported on various browsers. However with JQuery framework it is probably your best client-end scripting tool. If you are new to web development, you should definitely try JQuery. It is wonderful and makes your job very easy. There are numerous JQuery plugins that are contributed, you can use them in your application and get instant functionality without writing lengthy and unstable javascript code.

I read how 'Java' slow and to be avoided. In the case on Javascript, is this the only language use for building interaction on the web? It seems to be the most popular...

Sun has Java, of course, and now JavaFX, which uses JavaFX Script. Adobe has Flash, which supports ActionScript and, with Alchemy, C/C++ compiled to ActionScript. Its AIR runtime lets Flash/Javascript run offline in a VM. Microsoft has Silverlight, which supports many languages thru the CLR/DLR (e.g. C# and IronPython). Google has 'Native Client', which lets compiled C/C++ code run in the browser with standard library support (e.g. stdlib, libstdc++, math, NPAPI, RPC, and threads).

the words arent sinced with the guy

Here's a web based REPL. squarefree(dot)com/shell/shell .html

Javascript returns the last expression or the one you explicitly returned. Also, you can use print("foo") and obviously alert().