anynines joins the Cloud Foundry Foundation

We are excited to announce our participation in the Cloud Foundry Foundation, a non profit organization aiming at accelerating the adoption of the Cloud Foundry open source project. By joining the Foundation we intend to contribute our share to create an open source PaaS standard and share our excitement for the platform with the community.

A journey to Cloud Foundry

While advancing our expertise in hosting and software development in the past years we felt the need for a next step in the evolution of hosting. As our developer team follows the agile approach for creating software in iterative cycles we rely on a simple application deployment process and robust hosting. With the rise of new technologies, programming languages and frameworks we have to be able to run each kind of application regardless of the used framework or language.

Our investigations led us to the Cloud Foundry project which allows us to unite our way of software development with the increasing requirements in hosting. By using the Cloud Foundry PaaS our developers are able to create their own staging and live environments including the ability to scale applications as needed while decreasing our administrative efforts. We also want to provide our customers with the latest technology for implementing their visions which is the reason for choosing Cloud Foundry as a basis for

Cloud Foundry Summit

As we did last year, we will be attending the next Cloud Foundry Summit from the 9th until the 11th of June 2014 in San Francisco. The summit is a great opportunity to meet the community behind Cloud Foundry and talk about the future of the CF eco system. If you would like to join us you can register here.

The differences between Cloud Foundry CLI v5 and v6

Since we adopted the latest Cloud Foundry version anynines users are able to use a completely rewritten version of its command line client (CLI). Read how to install the new client and how to use the this client. If you used the old CLI version before you might be interested in the differences between the old version (v5) and the new one (v6). Here we go, a roundup:

Easy to install

The new client is an executable binary which you can download for your operation system. You don’t have to install a Ruby runtime anymore. This guide shows you the simple steps to install the cf client on your operation system. (more…)

Agile CSS and frontend testing at the JavaScript Days

We attended the JavaScript Days (JSDay) in Verona and I summarized my favorite talks for you to enjoy. After the opening chat by the GrUSP guys – did you know they not only organize PHPday and JSday, but a number of other smaller conferences like better software and kerning? – the madness started:

Metaprogramming in JavaScript

Massimiliano Mantione, who previously worked on v8 team at Google, starts the day off on a skeptic note: “We all know that JavaScript is powerful but it can be a really terrible language when misused. It lacks several advanced features that are taken for granted in other languages. One technique that is overlooked is metaprogramming.” Mantione developed Metascript taking the best bits of Coffeescript, Typescript, Lispyscript, Clojurescript, Lisp and Haskell. Code that can modify your code, that compiles to JavaScript…

Metascript has a readable syntax and at the same time allows for lisp-style metaprogramming (macros that can manipulate the AST). Lisp-like languages have a ‘clean’ syntax per definition: they explicitly use parenthesis everywhere to express the grouping of expressions. Metascript uses a combination of parenthesis, indentation and infix operators to ensure that the syntax is similar to a number of mainstream programming languages, and can be used interchangeably. The next steps for Metascript would entail completing the compiler and the metaprogramming system. Writing standard macros and publishing a module on GitHub are also on the road map. As is implementing a type system. One to watch.

NSA.js – really tracking user interaction

Danni Friedland (eBay IIC) dislikes how current tracking solutions are sub-optimal. Charts, graphs and heatmaps are too abstract. There’s no up-close-and-personal with your user. What if you could see what the user sees? You’ll have to record everything and add an Eventlistener to scrollObserver, mouseObserver, ViewportObserver (screen sizes), TestSelectionObserver, track focus in/out, URL changes, the open or closing of a popup… (more…)