Monday, December 27, 2010

Erlang for Smart Phone Operating Systems?

A thought I recently had was whether or not Erlang would be a better language for smart phones than Java. My reasoning is that smart phones need to be very reliable as they have become a primary form of communication for many people. Erlang, with a long history of use within the telecom sector, has proven that it is reliable. Also, it already has good multiprocessing, so that is one less thing that needs to be worked on for a phone.

Yes, much work would need to be done to make it work on a variety of hardware, but that's nothing new. Even then, unless I'm mistaken, Erlang pretty much is the same on every platform, so in theory we wouldn't have to install a special version of Erlang to develop apps on normal computers. We'd just have to make sure that all of the APIs exist for all platforms.

The only area that I see that would probably need a lot of work is the UI. AFAIK, there hasn't been any mobile UI work done for Erlang.

Anyway, just a thought. I personally think it's a good idea and would love to see it happen, however I think Android has become too powerful for this to happen unless somebody does this and really shows the benefits of Erlang over Java.

Labels: ,

Saturday, December 18, 2010

Android and the ParrotOS Concept

I just had a revelation that I believe to be accurate: my concept of an OS that is a VM, which I dubbed ParrotOS after the Parrot VM, appears to be reality: Android. I haven't done much with it, but it does run on multiple devices, each with a different hardware configuration, and all of the software, as far as I can tell, will run on all Android devices. This is, of course, barring OS compatibility.

The coolest part is the fact that the concept works pretty well. Android phones appear to have very good performance despite the fact that the "apps" run in a VM.

Now if only we can get this to work on other devices, like desktops, laptops, and servers.

Wednesday, December 08, 2010

New Language Attempt Take 2

Well, I decided to take another attempt at designing the language. It may not be the same, however that's O.K. I'm not 100% sure that I did things right the first time, so I figured I'd take another stab at it especially since I have some new ideas.

So, the first step I'm going to take is to clearly outline my goals. I feel that this is a crucial step so that I stay on track. If I don't have a clear picture of what I want the language to be able to do, then how do I know when I'm done or even which direction to go in?

I'll most likely revisit/reuse some of my previous ideas, however I'm sure some decisions I had made before will change. Again, that's O.K. I'd rather change my mind now to make a better product than regret an old decision.