Test an API of a microservice

Above mentioned microservices provides different services which ultimately drives to perform one complex business scenario through an application. A microservice can be a service provider to another…


Javascript history

As the web gained popularity, a gradual demand for client-side scripting languages developed. At the time, most Internet users were connecting over a 28.8 kbps modem even though web pages were growing in size and complexity. Adding to users’ pain was a large number of round-trips to the server required for simple form validation. Imagine filling out a form, clicking the Submit button, waiting 30 seconds for processing, and then being met with a message indicating that you forgot to complete a required field. Netscape, at that time on the cutting edge of technological innovation, began seriously considering the development of a client-side scripting language to handle simple processing.

In 1995, a Netscape developer named Brendan Eich began developing a scripting language called Mocha (later renamed as LiveScript) for the release of Netscape Navigator 2. The intention was to use it both in the browser and on the server, where it was to be called LiveWire.

Netscape entered into a development alliance with Sun Microsystems to complete the implementation of LiveScript in time for release. Just before Netscape Navigator 2 was officially released, Netscape changed LiveScript’s name to JavaScript to capitalize on the buzz that Java was receiving from the press Because JavaScript 1.0 was such a hit, Netscape released version 1.1 in Netscape Navigator 3. The popularity of the fledgling web was reaching new heights, and Netscape had positioned itself to be the leading company in the market. At this time, Microsoft decided to put more resources into a com- petting browser named Internet Explorer. Shortly after Netscape Navigator 3 was released, Microsoft introduced Internet Explorer 3 with a JavaScript implementation called JScript (so-called to avoid any possible licensing issues with Netscape). This significant step for Microsoft into the realm of web browsers in August 1996 is now a date that lives in infamy for Netscape, but it also represented a significant step forward in the development of JavaScript as a language.

Microsoft’s implementation of JavaScript meant that there were two different JavaScript versions floating around: JavaScript in Netscape Navigator and JScript in Internet Explorer. Unlike C and many other programming languages, JavaScript had no standards governing its syntax or features, and the three different versions only highlighted this problem. With industry fears mounting, it was decided that the language must be standardized.

The following year, the International Organization for Standardization and International Electrotech- nical Commission (ISO/IEC) also adopted ECMAScript as a standard (ISO/IEC-16262). Since that time, browsers have tried, with varying degrees of success, to use ECMAScript as a basis for their JavaScript implementations

Add a comment

Related posts:

How marketplaces can nurture customer engagement with video

The changes that COVID-19 is forcing on businesses all over the world are vast and sure to bring long-lasting implications across a broad variety of domains. In today’s installment of our four-part… Read more


Some nights I work all through and have little or no time to sleep, well for one I have so many persons counting on me and I just cannot afford to fail and then I have very limited time to get things… Read more

Python Pandas Library

Pandas library created for studying data frames. So, what is data frames? Data frames are excel files, this files has datas. In Pandas, transition from file to file (.csv or .txt files) is easy. Also… Read more