At the start of the Internet, about 1990, Internet Explorer and Netscape Navigator were the two most well-known internet browsers being used by the overall population.
In only 10 days, an engineer named Brendan Eich at Netscape Inc. had the option to make a programming language that could educate the PC on the best way to write with the client after getting clients’ input. They called this language “LiveScript” and organized it straightforwardly into Navigator.
Java is a programming language created by James Gosling and created by Sun Microsystems. It took slightly longer than 10 days to create — it took more like four years. In 1991, a company of Sun Microsystem designers called the “Green Team” worked day and night to make Java. It was first released in 1995, and a few new forms have been propelled from that point forward. The present Internet is immersed in Java-run programming. We have Java to thank for a meaningful number of the letters that make everyday living simpler. Java is now alleged by Oracle.
Compiled vs. Interpreted
Static vs Dynamic Type Checking
There are numerous upsides and downsides for these two ideal models, but the vital bit of leeway of static sort checking is that type mistakes are gotten right off the bat being developed, and in light of the fact that the compiler knows precisely what data types are being utilized, code usually executes quicker or utilizes less memory.
The primary positive position of dynamic kind checking is software engineer profitability — you are allowed to designate types at your game.
Class-Based vs Prototype Based
Java uses latent sort checking, where the kind of a variable is Java perseveres class-based legacy, a top-down, various leveled, a class-based link how goods are defined in a class and received by a case of that class (one of its people).