Archive for November, 2006 Page 2 of 2



Which framework/language to choose??

Update: Python Framework Design Revisited discussing on Python’s plateau of frameworks.

There are so many in this world, it can get really crazy to know which to choose! It’s easy to choose if you know you only want Perl – natural choice is Catalyst. But when it gets to languages like Java and Python, you get a whole list of them!

There’s Google Web Toolkit, Struts and Maverick just to name a few! For Python, there’s Zope, Django, a recently heard Quixote and Pylons!!

The main question is, which framework is the best? Everyone usually has their own opinions of it, so it practically boils down to, first, what is your need, secondly, how mature the framework is. It’s quite similar to programming languages, e.g. Erlang is only geared towards for telecommunications related projects. It is no different, for Java frameworks, this poll indicates that the NotInventedHere syndrome and every situation requires different sets of solutions speaks clearly that 1) one possibly wouldn’t know which framework is best at the start until you’ve reach certain understanding and 2) being comfortable in the framework helps alot.

So how about for Python? I believe it’s the same. How far can it differ as when there’s a discussion on “which car do you like best?” It all depends on the use, its purposes and the potential to which the car can promote its purpose. Plat_Form created a very interesting international programming contest, that doesn’t look at hard and fast facts of issues in one language to another, but its totality. I hope they are truly doing a “thorough evaluation”.

The main question is, has MuSMo wisely chosen the framework that works best for the future of MuSMo? If my believe that Zope3 is mature, solid, secure, reliable, scalable, flexible and adaptable in various situations, isn’t that enough? I hope so. After discussing further with a newfound friend in China, my thoughts is once again open for suggestions and have ensued to further read articles off the Internet. Equally important, to discern what is true to our case and which aren’t.

The Past, Present and Future

In the past, MuSMo was just an idea. An idea that evolved to become more realistic and, more importantly, in the direction that the world of technology and internet are fusing together. What was known to be a fantasy is becoming a reality. A project that will satisfy our needs when we travel and when we need to share on what we personally own. One of TzeErn’s primary job was to hunt down the current events that relate to us. We’ve also been talking to all kinds of people, engaging into what we need to fuse together a mediated ecosystem. Together we are confident in the future of MuSMo. We need not only capital and resources, our thoughts and ideas, but also your feedbacks and reflections for our future. This is the purpose of this blog – to centralise constructive criticisms, considerations, thoughts, ideas, projections and plans for MuSMo. More to come soon.

At the moment, we are moving ahead in building the core application of MuSMo. We are looking into various countries, such as India and China, to outsource our project. A few friends of mine are hunting in China, and I will be there soon to scout further. The outlook in China doesn’t seem quite positive, but it should bring back some goodness. I have spoken to some other companies on outsourcing, but so far, it is very difficult to find for what I really need. Unless I’m convinced otherwise in not using Zope 3, I will continue to stick to the framework that is deemed to be mature, solid, flexible and reliable.

The Beginning of MuSMo

Today represents the first of many milestones for MuSMo, today we will publicly share our journey. A dream of two brothers to create a mediated ecosystem.

Our dream? To create an ecosystem that is not burdened by:

  • geographical location;
  • time;
  • format;
  • and device.

This is our dream, which we hope can be realized together with your valuable input.