Mobiles in the era of IBM PC compatible predawn age

A lot has been said and done about mobile phones of today. iPhone has brought a brand new concept in phones. It really moves the mobiles to the mainstream to do things other than talking. Just when things seemed bright for the mobiles we have Mr Jobs giving out a big MSish rules for development of Apps. I am not sure of its real usage. Probably he wants to protect iPhone from viruses, but then destroyers dont wait for a legal or easy means. They will find a way out anyways.

The hardware for mobiles available is sadly built and around it software just manages things somehow. I see this as what happened to IBM PCs. They gave way to PC Compatibles with MS making a killing out of it. Even now its because of this that we had such a boom in PCs, atleast in India. It was this parallel development which actually boosted usage. If there is a corporation today which does something similar to what Intel, MS and others did together to kill the mafia of Apple and IBM. I am sure had it been then only, most application would not have had seen the light of today. Thats why I am placing my bets on Open Moko and Android Platforms. I hope they do something to free up the platform. As far as chip manufacturers like TI and Infineon are concerned its better that they realize they are better off acting on the Intels paths and freeing mobiles from the clutches of limited set of manufacturers. The onus lies on the chip makers to make a killing by supporting an open mobile platform of sorts.

It would be great if we have an option to have a basic cellphone and then we can add other accessories like a good processor, memory, SSD and 'n' other things as the user wants. These addons should be open that is to say that any manufacturer can choose to have their device available for the platform, just like on PC. Once this kind of project is announced it will take the developer community by storm and even if the start is a little uncool like initial PCs with DOS, I am sure it will soon take a lot less time to make Vista like jhingalala on the cell phone. I dont know if some mobile phones cos like Nokia or Sony Ericsson or Motorola will take advantage of the situation and open up the platform. I wish they do. If they are able to match near the iPhone I am sure developers around the world will surely make an application beyond the imagination today.

Until that happens, I am happy with the cell phone which is just enough to make and receive calls and my dream phone still remains a dream.

Comments

Post a Comment

Popular posts from this blog

[24th November 2024] Interesting Things I Learnt This Week

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more