First implementation of a chess engine in JavaScript

Today Morfik released version 0.4 of the Morfik Chess application. This version uses a chess engine developed with WebOS AppsBuilder using Object Pascal and which is compiled into pure JavaScript and HTML so that it can run in the browser. It is able to compute at least 2 moves deep. This is probably the world’s […]

Today Morfik released version 0.4 of the Morfik Chess application. This version uses a chess engine developed with WebOS AppsBuilder using Object Pascal and which is compiled into pure JavaScript and HTML so that it can run in the browser. It is able to compute at least 2 moves deep. This is probably the world’s first implementation of a chess engine in JavaScript.

This alpha-version Chess game can be played as a single player or a multi-player networked game. If you choose the 'Single Player Game' mode, you will be playing against the world's first JavaScript Chess Engine which is running within your browser. This release sees a couple moves ahead, i.e. this is not (yet) a demonstration of a JavaScript Grandmaster.......

If you choose the 'Multi-Player Game' mode, you will again be playing via an application which is running in your browser, i.e. you initiate the browser chess game and invite your friend to join the game using her/his browser. This game takes place without utilizing a central server.

This endeavor is driven by the belief that the frontiers of browser applications have not yet been reached for three reasons:

- Current applications written for the browser are limited because they use hand coded JavaScript. Strongly-typed compiled languages follow a rigorous programming model that has made compilers the preferred tool for building large and complex applications. Compiled code is, by definition, more reliable and scalable than interpreted code. Although the client-side code generated by AppsBuilder is JavaScript, rigorous type-checking and enforcement of referential integrity by the compiler produces reliable and scalable AJAX.

- Browsers ‘raw power’ is progressing significantly due to competition. What was difficult to do yesterday is possible today and will be easy to accomplish tomorrow.

- The mindset of developers needs to shift further towards the browser, i.e. it is not just a ubiquitous presentation level but also a ubiquitous OS layer. We may remember the days when developers were asked to move from DOS to Windows. How often the concern was raised that Windows based applications ran slower than those in DOS (and anyway it was only fancy graphics)….but as improvements were made the vision and reality of what could be delivered merged. We are today at the same juncture with regards to browsers. This need to change in order to meet the future. And the future is good.