6 June 2011

  1. Front Page
  2. Development
  3. Devices
  4. Maemo in the Wild
  5. Announcements
  6. Download issue

Other Issues

  1. 20 May 2013
  2. 6 May 2013
  3. 29 April 2013
  4. 22 April 2013
  5. 8 April 2013
  6. 25 March 2013
  7. 18 March 2013
  8. 11 March 2013
  9. 4 March 2013
  10. 18 February 2013
  11. 4 February 2013
  12. 28 January 2013
  13. 21 January 2013
  14. 14 January 2013
  15. 7 January 2013
  16. 17 December 2012
  17. 3 December 2012
  18. 26 November 2012
  19. 12 November 2012
  20. 29 October 2012
  21. 22 October 2012
  22. 15 October 2012
  23. 8 October 2012
  24. 1 October 2012
  25. 24 September 2012
  26. 17 September 2012
  27. 10 September 2012
  28. 3 September 2012
  29. 27 August 2012
  30. 20 August 2012
  31. 13 August 2012
  32. 6 August 2012
  33. 30 July 2012
  34. 23 July 2012
  35. 16 July 2012
  36. 9 July 2012
  37. 2 July 2012
  38. 25 June 2012
  39. 18 June 2012
  40. 11 June 2012
  41. 4 June 2012
  42. 28 May 2012
  43. 21 May 2012
  44. 14 May 2012
  45. 7 May 2012
  46. 30 April 2012
  47. 23 April 2012
  48. 16 April 2012
  49. 9 April 2012
  50. 2 April 2012
  51. 26 March 2012
  52. 19 March 2012
  53. 12 March 2012
  54. 5 March 2012
  55. 27 February 2012
  56. 20 February 2012
  57. 13 February 2012
  58. 6 February 2012
  59. 30 January 2012
  60. 23 January 2012
  61. 16 January 2012
  62. 9 January 2012
  63. 2 January 2012
  64. 19 December 2011
  65. 12 December 2011
  66. 5 December 2011
  67. 28 November 2011
  68. 21 November 2011
  69. 14 November 2011
  70. 7 November 2011
  71. 31 October 2011
  72. 24 October 2011
  73. 17 October 2011
  74. 10 October 2011
  75. 3 October 2011
  76. 26 September 2011
  77. 19 September 2011
  78. 12 September 2011
  79. 5 September 2011
  80. 29 August 2011
  81. 22 August 2011
  82. 15 August 2011
  83. 8 August 2011
  84. 1 August 2011
  85. 25 July 2011
  86. 18 July 2011
  87. 11 July 2011
  88. 4 July 2011
  89. 27 June 2011
  90. 20 June 2011
  91. 13 June 2011
  92. 30 May 2011
  93. 23 May 2011
  94. 16 May 2011
  95. 9 May 2011
  96. 2 May 2011
  97. 25 April 2011
  98. 18 April 2011
  99. 11 April 2011
  100. 4 April 2011
  101. 28 March 2011
  102. 21 March 2011
  103. 14 March 2011
  104. 7 March 2011
  105. 28 February 2011
  106. 21 February 2011
  107. 14 February 2011
  108. 7 February 2011
  109. 31 January 2011
  110. 24 January 2011
  111. 17 January 2011
  112. 10 January 2011
  113. 3 January 2011
  114. 20 December 2010
  115. 13 December 2010
  116. 6 December 2010
  117. 29 November 2010
  118. 22 November 2010
  119. 15 November 2010
  120. 8 November 2010
  121. 1 November 2010
  122. 25 October 2010
  123. 18 October 2010
  124. 11 October 2010
  125. 4 October 2010
  126. 27 September 2010
  127. 20 September 2010
  128. 13 September 2010
  129. 6 September 2010
  130. 30 August 2010
  131. 23 August 2010
  132. 16 August 2010
  133. 9 August 2010
  134. 2 August 2010
  135. 26 July 2010
  136. 19 July 2010
  137. 12 July 2010
  138. 5 July 2010
  139. 28 June 2010
  140. 21 June 2010
  141. 14 June 2010
  142. 7 June 2010
  143. 31 May 2010
  144. 24 May 2010
  145. 17 May 2010
  146. 10 May 2010
  147. 3 May 2010
  148. 26 April 2010
  149. 19 April 2010
  150. 12 April 2010
  151. 5 April 2010
  152. 29 March 2010
  153. 22 March 2010
  154. 15 March 2010
  155. 8 March 2010
  156. 1 March 2010
  157. 22 February 2010
  158. 15 February 2010
  159. 8 February 2010
  160. 1 February 2010

In the Wild

Is one of MeeGo's problems its name?

Randall Arnold is proposing that one of MeeGo's problems is its name (which likely anyone from the Maemo community around when MeeGo was announced last year would agree with): But months later, Nokia’s retreat from MeeGo was followed by dismay amongst the faithful and abandonment by the casually interested. Many were put off by the name “MeeGo” and are now left to wonder if the childish-sounding appellation has some involvement in the operating system’s recognition problem. [...] Could MeeGo’s name be hurting its chances? I know it sounds trivial, but at some point adoption and acceptance are driven by marketing more than anything else. When consumers are faced with dozens of products that really aren’t differentiated at a meaningful level, then buy-in comes down to presentation. The best-looking of the bunch. The most clever commercial. The coolest name. The name is hardly the platform's most pressing issue (nor the most tackleable of them), and a name change at this point seems unlikely to generate more confidence in the platform.

Does MeeGo have a $32 license fee? No

More FUD from the man who brought you the excellent-journalism-in-action piece last year in Dublin: "Nokia's MeeGo is doomed". Back again with "MeeGo will be dead in eight months" Tamlin rants about MeeGo's inability to competent in the market, going so far as to invent a fictitious "32 dollar licence". An excerpt, A MeeGo licensee tells TechEye there's no chance for the platform. The 32 dollar licence (Android is $2, Microsoft is $100) is only getting bought up as a way to show and save face, to tell the partners involved that you're current and as a pat on the back. According to informed sources, MeeGo will be doomed as soon as eight months from now.

Despite the money thrown at the huge MeeGo developer conference in Dublin last year, where the entire Guiness brewery was hired out, it's a dead duck. Like throwing money down the drain. The tablet offered to all of the thousands of participants has been described to us as "horrible". Of course as MeeGo is an open source project and under no licencing more costly than the compliance program, the $32 is certainly an interesting one. Henri Bergius's rebuttal is below.

Understanding MeeGo

MeeGo presents a confusing subject, unsure enough of its positioning when it was first announced, recent business shifts have only confused things more. In response to a rather impressive blog post from TechEYE.net, Henri Bergius has written up a summary of sorts of the project and the platform to help clarify when it is and what it could be: Subsequent discussion has highlighted the Tablet and IVI UXes as something where the project's achieved openness fell far short of its publicised openness. Nathan Willis' write-up (in LWN) of Carsten Munk talk at the conference sheds further light.