iPhone or Openmoko

Well as I had been following mobile phones. What I have found is that actually there are just two worthy competitors. Rest are just like that. One is iPhone and other is Openmoko. Well iPhone because it has the glory. It has the backing of Apple and support of Steve Jobs behind it. But there is none of that sort for Openmoko. But it has the guts. Its has probably what it takes to make a real revolution. Just making a phone with a bigger screen and touch sensitive does not make revolutions happen Mr Jobs. The best part of the Openmoko phone is that its open. And surprising its priced at $399 and in India its around Rs 20k. Not bad for the phone which has Assisted GPS, WiFi, touch screen, bluetooth, microSD Card support and powerful 500Mhz Processor. To top it all, a user replaceable battery. 

Well the only blemish that I am able to spot is the internal memory. Its a mere 256 MB. Though I can carry all the data in my SDCard but then its not the most convenient way to do things.

Anyways with its killer price(Unlock iPhone reportedly costs $599) it sure makes people think. With no restrictions, I can run apps to my hearts content. I am sure of some amazing applications coming for Openmoko, just because its so much more  developer friendly. No contracts, no iTunes, just fun. I am sure if Apple could, it would have allowed software downloads only through iTunes. Infact I feel very soon it will be a reality for snobby rich Apple fanatics.

In the end it will the people power which will rule. The flexibility is what is going to make a killer app and  mobiles are yet to witness them. And for geeks like me its cooler to have developer friendly phone.

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