Skip to content

web - opa programming language (opalang)

Three different pages in two languages pushed an entry on top of there page so i have to investigate the linked content. The entries are about "opa", an self designated "enterpriese framework for javascript". Opa can handle server and client side javascript, and writes the javascript for you. That means while creating your web application, you write all the code in the opa programming language and the framework does the rest for you. Opa uses jQuery on the client side and node.js on the server side. After a few hours investigating, i love the fact "strong static typing" as much as "available for linux, freeBsd and other systems". I recommend the tour and walk through some examples/use cases.

By surfing through the web for opa, i stumbled upon HaXe and this looks quite promising.

Web - Using PHP-GTK to serve Web Applications to HTML 5 Browsers

[...] PHP-GTK is a PHP extension that uses the GTK+ library to build PHP desktop applications. So it can eventually benefit for this GTK library enhancements to build PHP-GTK based applications that can be served over the Web to HTML 5 browsers. [...] Over time PHP-GTK got many contributors that helped making it work with GTK+ 2, as well making it work with PHP 5 under Linux, Windows, Mac OS, etc.. GTK+ 3 broadway HTML 5 canvas backend GTK+ version 3 was released officially this year 2011. Despite the worked started earlier, version 3.2 that was released last September introduces officiallly two new backends for directing the output of GTK+ graphics: wayland and broadway. The wayland backend provides an alternative way to render graphics by providing direct communication with the underlying graphics hardware. This is a faster way to render graphics than the traditional method used in Linux which relies on the X windows system. Read below for more information on the X Windows system. The broadway backend can make the application graphics render in a Web browser that supports HTML 5 canvas elements. [...] Another challenge is to determine whether using PHP-GTK applications over the Web is a technically advantageous solution, when compared to traditional AJAX based PHP+JavaScript Web applications. The matter is that once an application is running on the server side, the resources that it consumes will be taken mostly of the server. When I say resources, I mean mostly RAM. A typical HTTP request handled by PHP is short lived. It usually takes between 10MB and 20MB of RAM. So you can run as many PHP requests in parallel as the available RAM on the server permits.

The source link above has a video inside. Just the video is it worth to click on the link. But i also want to emphasize, that the whole article is worth reading.