Archive for February, 2012

The ACE project is a standalone programmers editor written entirely in JavaScript.

You can take ACS for a spin in the project homepage at, you’ll notice is supports multi-language syntax highlighting, parenthesis matching, regular expression and full text searches, although I didn’t see code completion (which would be nice). Judging by the amount of other projects that make use of ACE, it’s fast becoming a de facto for browser based editors.

According to the authors of the system, the mission of ACE is to rival existing native editor like Eclipse. The editor is already used as part of the cloud9 IDE.

So go take a look at the website and see the impressive list of projects that are making use of ACE.

I know I will when need arises.

I know I’m off subject again, just bare with me, its exciting stuff.

There are new interesting things happening at chip manufacturer AMD.

What is HSA (Heterogeneous Systems Architecture)

HSA put simply is a multi-core processor combined with a GPU(s) that are all on one piece of silicon. In the full vision it’s AMD’s goal is to have all these parts functioning in the same address space with little memory conflict, in other words they’ve figured out have to make all the bits of the chip play nicely without bumping into one another, thus faster.

What makes HSA so cool?

Today’s GPU’s and CPU’s are on entirely different memory maps, so you need to copy data to and from different memory maps, this is tedious and slow. The goal is, AMD’s HSA will allow you to access all the the parts of this chip in one unified memory space, which will speed everything up and make programming much simpler. It will be really fast and I mean fast.

What could I do with HSA?

AI, Realtime processing, pattern recognition, photo realistic 3D, all of the things that programmers dream about. There will also be a block of silicon ‘sub-routines’ for doing specific kinds of processing, probable more mathamatical in nature (I’m guessing).

AMD has an ambitious plan, they have committed themselves to producing the finished product within 2 years.

You can find more info at:


Here’s just a quick update on the up and coming release of MoSync 3.0.

It seems that MoSync is the only SDK, where you can create native UI across Android, iPhone & Windows phone 7, it works with JavaScript, So MoSync is the only product that really provides consistency across, JavaScript, HTML 5 and Native UI.

Also here’s an up to date list of features for MoSync 3.0

  • JavaScript libraries to access to native features, including native UI
  • Windows Phone 7 support
  • New deployment model based on platforms, not devices
  • Multichannel Sound API
  • Ads (iOS and Android)
  • Notifications (iOS and Android)
  • Improved development workflow (quicker turnaround)
  • Automatic updates
  • Local SQL Database support

If you have questions, just comment🙂

Do you remember Mophun ? Those nice little chunky pixeled retro games on old phones ?

For those of you who don’t or have never heard of it, here’s the low-down.

Mophun was a mobile phone games SDK, it was released in 2002 and had a huge community of 30’000 developers, there were 200-300 games were written for it. It was also the first platform that had an AppStore (stolen by Apple & Nokia🙂 ) and had deployment via mobile operators world-wide.

For a little more info on Mophun take a look at

Is There Interest

So should Mophun be made open source, is there enough interest.

The Games

There are hundreds of Mophun games out there, these games are not really doing anything, so why not make them open, or at least make the binaries open and free. I will make a appeal to some of the original authors of these games, I feel fairly confident that I cam get at lease 50%.

If there is enough interest, I will write a clean-room version of the run-time engine (to avoid being sued) on MoSync .
I have the domain, I just need to know if anyone’s interested before I do it.

So leave a comment now, or vote on the poll!

In the past year there has been a real buzz around cloud computing, why should use it?

1. No Hardware, No hassle.

We don’t to own hardware, we don’t want to buy a rack and host it, we don’t want to be responsible for it’s up-time. It will cost us more, but the total cost of ownership is too frightening. The downside, it’s one size fits all and it’s more expensive.

2. It Scales.

The Amazon elastic cloud promises us 99.99r up-time and total scale-ability, the choice of OS. But don’t forget, you still need to write the service/server. I always thought that good scale-ability came out of good software architecture, apparently cloud services provide this automatically🙂

3. The singular solution

The reasoning for using the cloud goes something like this:

Singular Solutions

“Buying computers and hosting them somewhere has limitations, therefore we will use a cloud service, because we are building for the future, when millions of people use our service every day, we will be able to handle all of them. We will create our service and make it scale across multiple servers, so we can grow as more people use our service.”

Here’s the problem: Business people think they understand this!!

This sound like utopia, the holy grail, I smell a rat!

 4. The Reality

What’s important, is it the infrastructure, the software/servers or the users of the software.  In what priority should these things done,

Firstly. Study the Users – Clearly the most important, who will use your software, how big is the market, how should your software solve the uses problem, get some use cases.

Secondly. Prototype your software – Now you know what the users want, you can design something quick to solve their problem, it’s not a university project just get on with it. Prototype your software first, just go ahead and write something quick and dirty (search for “Duck Tape Programming”), do this before creating a real design, you will learn more now than at any other time, set yourself a deadline and work to it. If you created a design at this time, it would change constantly and you would end up with deep limitations.

Thirdly. Design your software – Do it properly based on everything you learnt in your prototype. You must be able to create and debug this software with the fastest turnaround in the simplest configuration. Test with a smaller group first, by doing this you can shorten development time, cost and reduce development risk.

Fourthly – Cloud services. Since you already know the scale of your users in step one, you should have taken this into consideration in the software step. Perhaps you don’t need a cloud server or a high level of scale-ability, perhaps you do.


You don’t need cloud services/servers at the beginning, in fact it’s better not to have them, you just need to be prepared in advance. Remember software is king, content is the king of kings and users  are god.

P.S. I know that this doesn’t relate to JavaScript, sometimes I just need to get something off my chest.


Get every new post delivered to your Inbox.

%d bloggers like this: