For sure I do use Facebook, I am “on Facebook” just like many other people. But I also use Google Plus and Diaspora. While Diaspora aims at being something really different and relies on a fundamentally distributed model, it is in its infancy and I will not discuss it in this post. I will focus on Google + instead.

I had big hopes for Google + and still do. I still believe it is a better built, more powerful and less harmful service than Facebook, but I also believe that while any service has shortcomings of its own its operator/owner tends to correct them over time by bringing in more features for instance, something Google does not seem to be doing, hence my points below:

• Tastes and colours should not be discussed as everyone has his or her own tastes and yet… I still like Google + much more than Facebook for that matter, however, something seems not all right in Google +: could users customize the look of their page(s), or are they condemned to the everlasting white background? (on the other hand you could point out that simplicity in design never hurt anyone).
• Profiles: it’s amazing how hard it is to see someone’s profile. For this Facebook tends to be much simpler and clearer, Why can’t I just access someone’s profile in one click, instead of searching its own activity feed?
• Sharing and circles is probably what Google + does best, although in many ways it was a Diaspora’s concept that was itself hinted in the discussions around the DISO concept (the early days of a distributed social network) but there is something, specifically about sharing, that I do not understand: sharing beyond circles, such as sharing on Twitter or StatusNet, let alone on Facebook is not possible. I know about the hack for identi.ca and twitter that works by sharing with one specific profile but why would I want to share that with this probably sympathetic, yet unknown person? The most surprising part of this is that neither Google, nor Twitter, nor Facebook, seem to be willing to provide that feature (the same goes for sharing from Twitter, StatusNet and Facebook to Google +). This issue alone, to me, is a major one, and I am pretty sure it’s the same for many people. Because of that posting on Google + is somewhat of a solitary exercise; you have to repost specifically on Google +.
• More distributed content : obviously Google does perform data mining on the content we share on Google + and any of its other services, that’s not news to anyone. But while Google does handle data portability seriously (a big plus!) it might benefit from enabling some sort of “sandboxes”, that is, private spaces that could be self-hosted, yet easily connectable to the “central” Google + network. This would also allow many people to both feel more secure and enrich the overall content aggregation scheme; you would be able to use Google + as a content transport layer in between “pods” or peers and still using the big social network itself if you want to.
• A Google Wave like timeline : as people become increasingly aware that their past posts and interactions can be monitored, reused by others or simply by and for themselves, an easy to use timeline, something completely missing on Facebook, might be useful and fun to use.
• A professional page or job search as well as other specific services might also be useful; but it seems that Google + is very much like other services launched at Google: an experiment first, a product afterwards. I am usually fine with this approach, but Google + needs attention and extra features if it wants to stay and grow instead of being dumped and filed such as Google Buzz was. I really hope that won’t be the case.

Picture by Eliane Domingos of the Document Foundation

If you wish to read our official wishes, we have them here, and they come from all of us. My thanks go to everyone who is making the LibreOffice project possible and what it is today. We have grown quite a lot in 15 months, probably more than we would have thought. 2012 is going to be the opportunity for the Document Foundation to solidify its successes and turn them into a powerful entity and structure. It will also be the year where several strategic project, such as LibreOffice OnLine, will see their development hopefully take off. Adoption-wise things are already well on their way. Deployments are ongoing on a worldwide basis, large and small, and what we  need at this stage is to push our brand name in a more consistent way. It will also be the year where our friends at the Apache Foundation release their first Apache OpenOffice; what will be interesting will be not their first release(s) but the one that will see most of the Lotus stack be injected into it. This will actually be a good opportunity to clearly differentiate Apache OpenOffice, and that in turns will improve the Apache OpenOffice project’s health and its relation with the outside world (LibreOffice being one example).

But 2012 will be the year where you will be able to experiment the benefits of the LibreOffice development’s effort as we will bring the 3.5 and the 3.6 lines to life. I think it will illustrate that a community-based development model does effectively work and brings real and regular improvements and changes to an aging codebase.

On a more personal note, 2012 will be an important year: I’m getting married in June (expect full delays in blog posting) and this is something I was not expecting even a few years ago. But there are a few people in this world (in this case, only one) who can change everything for the best, and for this I’m truly blessed and very, very happy.

Last but not least, I would like to express my gratitude to my family and my friends at the Document Foundation and at Ars Aperta for making all this a reality. You truly rock. What else is there to wish? Health, happiness, and love.

Merry Christmas and a happy new year 2012.

It might be odd to write this, but if there’s any concept that’s both fuzzy and dangerously misleading in the software industry, that would be innovation. I have read for many years and listened to people explaining how to “stirr and create innovation” in a company or in a community. Maybe these words have been used for lack of a better term; but I still don’t see how you can create innovation. I think you might be able to stirr it somehow, as it’s already a humbler verb. But frankly, can someone out there tell me what does innovation mean in the software world?

In general terms, I would define innovation as the big and small changes constantly leading to a change of the art in any given field. I think that’s pretty much what one usually understands by that word. So why could this not be applied to software? Precisely because software is rarely -if at all- the result of big changes happening all of a sudden and by accident. Software development usually happens at an incremental pace, whether openly so (think about the agile development practices) or even when there’s a structured corporate environment favoring traditional code reviews and quality assurance processes through stable product development cycles. Software is not produced by accident. Software is the result of process, and in theory accidents do not happen there. In fact, I could also point out that incremental changes or a period of technological incubation might be observed right before the emergence of almost any given technology. Take the medieval rudder for instance: it’s been rumored to have been imported in Europe around the 12th century by Chinese ships, but there are tracks and evidence of previous try-outs by European sailors and shipyards to design wooden rudders and articulate them with a complete mechanism. Similarly, it is hard to say how “innovation” happened in the sixties when the U.S. decided to send manned flights to the moon, but the wave of small and not so small innovation that was the result of this huge project is still visible to everyone (think of the Tefal pans, among many other things).

Thus there are, I think, two points that need to be highlighted: First, innovation does not happen all of a sudden if the field of software field and more generally ICT. It is a set of processes that ultimately lead to new software, or software that’s supposedly not as bad as the former state of the art. Second, what’s unclear is how -to quote several people I listened to- innovation “happens”. It sounds sometimes that innovation is a mystery or the philosophers’ stone that require care and secrecy to happen. Yet in the software industry, it does not work that way, for all the marketing and bells and whistles that come out of software vendors do not brush aside the fact that even inside these corporations software development is a set of very well defined, but non-public, processes.

Innovation is not a mystery and I don’t think that you can track how it works. You can assume that a certain set of circumstances and an environment letting people code start-ups emerge and Free & Open Source Software projects grow will ultimately translate into something that someone, whether a journalist, consultant, politicians or venture capitalists will call innovation. Anything else besides that, innovation sounds more like vapor and magical boxes. This should probably express what I feel about software patents, by the way.

One last thing: Innovation is different than progress. Progress is usually applied to fields that do not necessarily belong to science or technology; it can be more a perception and may concern society as a whole. Yet the interesting thing is that while progress seems to be an even more elusive term than innovation, you can actually tell progress from regression or stagnation: people perceive it almost immediately, however relative it sometimes may be.

Enjoy the beginning of the Holiday season!

I would like to come back shortly on two of the announcements we made, regarding the porting of the LibreOffice platform (not the interface) to iOS and Android, as well as LibreOffice OnLine. While these two projects are at various stages of completion and have different requirements they help to show not just the vitality of our community, they also shed some light on how we manage to embrace a bazaar-like approach to development and think about what I call our “development ecology” (which some could really translate into development strategy, but I think it’s more subtler than that). What you see through our online office suite project and platform porting announcements is that we are taking some great care in doing something paradoxal with respect to our stated intent to change the codebase as much as possible: we keep our codebase intact. Note that we do change, upgrade, clear and trim the codebase, but we do adopt a singular codebase approach where the code used in LibreOffice OnLine, and the underlying code on iOS and Android will essentially be the same than the one inside the LibreOffice Desktop suite. In other words, we do not release a product here and something completely different there, even if in the future, a specific work on the interface for tablets will have to be made (we won’t use the existing interface on these as it would not make sense).

This “universal” approach makes sense not just for “market growth” and adoption, it has two benefits. The first one is to pool the resources as much as we can, because maintaining millions of lines of code here while maintaining a million of new and different lines of code there would not require around 3 hundred developers; it would actually require 3 thousands of them. We thus keep the codebase as a coherent whole (hence Rob Weir’s confusion answered by something like “just pull the git”) while we will enjoy in the future the second benefit of being able to make changes (and even important ones) in one codebase, thus replicating the changes for the online version at the same time as they will be made available in the desktop or the tablet version.

Exciting times are ahead. Stay tuned!

• It’s Holiday Season, nonetheless, and I thought you may want to take a look at how Christmas looks in Paris, especially under the snow. (Paris is a city that looks particularly beautiful under the snow). Prête-moi Paris has all the details.

• The Opera Browser 11 has just been released, with some very nice tab-docking features, among other things. Yes, it’s proprietary, but it’s innovative and truly standards-compliant.

• India embraces Open Standards for good. Interesting read from Venkatesh Hariharan.

• The EIF and EIS 2.0 are published at last. In many ways it is disappointing, but it is at the same time a clear political gesture in favor of open standards and true interoperability.

• Murky details about the famous CPTN’s buying of Novell’s patents. The result? It looks like the mob just bought the latest casino at Atlantic City.

Best wishes for the Season!

Simon Phipps wrote a much welcome post this week-end and quoted Voltaire “I may not agree with your opinion but I will do everything I can to make sure you can express it”; the Wikileaks “cablegate” is about that, as well as about two other issues.

But first, I would like to clarify my opinion on the “cablegate” in the form of a cautious caveat emptor. Contrary to Mr Assange, I do not believe that transparency solves or will solve every problem out there. I believe transparency is good, in general, but transparency can sometimes become a deforming mirror, pun intended: Total transparency is an utopia. We all need and have secrets, and so have human societies. While crime and murky business of all kinds do require opacity to progress, it has often been shown that transparency is also a well made-up reality, whether hiding those criminal or morally reprehensible practices, or hiding conversations or more delicate but legitimate dealings under the veil. Our societies could not exist with total transparency. We could not be humans with total transparency: Or else one would have to explain that Comedy, Drama, and human subconscious are inherently bad and useless. What the “Cablegate” reveals so far is quite embarrassing for the United States of America. I read the newspapers, like Le Monde in French and the Guardian in English, two newspapers that had been working with Wikileaks on the cables. I also went straight to one of the Wikileaks mirrors and watched that specific section. My gut feeling? It’s unfortunately the world we live in. If you think this will make me become anti-American then you’re wrong. The US are failing in bringing Pakistan to become a sincere ally in the war against terrorism? I’m yawning. The US ambassador in Paris describes the French President as being nervous and extremely egotic? Guess what, watch french national television for two hours and you’d get that instantly. For the rest -and there’s more embarrassing material- killing two Reuters journalists and children from an Apache helicopter is an absolute tragedy that bears a name: War. Not that I support what the videos are showing: I hope there will be DoD investigations for this. But war is war, and if anyone thought Iraq, Vietnam, World War 2 or the War of US Independence were about pooh-bears throwing honeypots at each other, then there’s a word for it that goes beyond naivety: stupidity.

Other leaks tend to be somewhat more interesting: it shows how private companies and special interest groups are framing entire legal frameworks in Europe, how the US put spies in political parties and hosts them in their embassies worldwide. It’s obviously embarrassing, but please let’s ask ourselves: Is this all new? I don’t think it is.

In fact there’s two ways to understand what the Wikileaks cables’disclosure reveal. One is the factual disclosure of actions, affairs, skeletons in the closet, various projects and information that enlightens the perception of the US Government on worldwide topics. You can feed anti-Western sentiment or anti-american feelings with this material, but frankly it’s not like these two memes would be fading away anytime soon without the leaks. Another one is the notion that all of a sudden transparency will fix the state of the world, starting with America. Transparency helps, but some things have to remain buried for a long time, some things are not meant to be disclosed. And talking about transparency, we should not be anymore naive and demand that the same kind of information be disclosed from countries like Iran or North Korea: I’m sure it would highlight another well-known reality: that US or democratic countries are not just no worse, but are in fact much better than these countries (some people are ready to absolve them from their wrongdoings on various grounds).

So why did I call this post “Discernment”? For various reasons; the first one is that the US Government in general is behaving in such a way that few will believe that they have a legitimate defense to present. Mafious-like pressures, persecution of one man, denial of reality, outrage do not serve them. The world we live in isn’t the Sopranos’ BadaBing strip club; and if I may write so, even if “shit does happen” one should try to think about not being seen as the culprit. I must indeed say that I find it extremely concerning that a man like Eric Holden is behaving the way he does, using expressions alluding to underground actions used to fight Julian Assange. A government does not fight one man; it discredits him, or it reuses his ideas to gain an advantage, otherwise that government is weak. It only leads to one result in the end: Assange is seen as the victim, the US Government and Barack Obama as the black knights (excuse the pun).

The second reason why I titled this post “Discernment” is that to the best of my knowledge, and interestingly enough many US lawyers seem to think that way, Julian Assange has not violated any US Federal or State Law. This means something quite terrible for the United States: There is simply no due process of law in this affair, only angry politicians. But angry politicians do not constitute a law themselves; you need a legislative and transparent process for this, otherwise you’re no better than in a dictatorship. This law has so far failed to materialize. Meanwhile, Wikileaks is being hunted down around the Internet, large companies withdrawing essential tools for its infrastructure. Julian Assange just went to the London Police and will remain there in custody until the 14th of December under the alleged charge of sex crime. Let’s stop the hypocrisy and speak out the truth: making up a lace of lies will only reinforce Assange’s position: Otherwise, Facebook’s Fan page of wikileaks now has over a million “terrorists”, the Internet should be censored and Wikileaks banned, (China-style) while the KKK, anti-semitic and djihadist groups are free to graze and prosper. And I forgot to add to the list: Pigs can now fly. Unfortunately, that seems to be the situation we are in. But there’s more.

As one may see I’m not exactly a fan of disclosing diplomatic cables, from the US embassies or elsewhere -while in some cases such as private corporations wrongdoings the disclosure helps and is important- but it’s not so much about what Assange did or did not do. Let’s consider this: the whole affair should never have been about Assange in the first place: Wikileaks has not stolen the cables, a whistleblower uploaded them, but nobody really cares. No, the whole point of the scandal is that we now have a great democracy whose government is incompetent in addressing a massive disclosure of confidential material, and its incompetence is now setting a precedent on free speech and free press. What Wikileaks did -and dare I add the newspapers that collaborated with the site to the culprits- was disclosing an information from an “unknown source”. That’s what newspapers in the free world do all the time. Does this mean that under the quite specious argument of the fight against terror we should now ban this? By the way, who will be able to “ban the ones who are banning free speech”?

Therefore, unless we specifically have a due process of law following a public and opend debate on whether initiatives of Wikileaks could be condemned on specific grounds, unless it’s clear for everyone that Free Speech is safeguarded and is actually enacted and thoroughly protected, Assange and every anti-American will have won.

Again, let’s have a public debate about this: It’s well worth the effort, and it’s well worth using our sense of discernment.

“”The Document Foundation is about documents and the associated software is pivotal to create, exchange, modify, share and print documents”, says Thorsten Behrens, a software developer and a member of TDF Steering Committee. “LibreOffice 3.3 is the first flavour of this long term strategy, but the journey has just begun, and the enormous advantages of our developer-embracing environment are not yet fully reflected in the upcoming software release”.

LibreOffice 3.3 is based on OOo 3.3, with code optimisations and many new features, which are going to offer a first preview of the new development directions for 2011 and beyond. TDF founders foresee a completely different future for the office suite paradigm, which – in the actual format – is over 20 years old, to be based on the document (where the software is a layer for the creation or the presentation of the contents).

TDF developers are working full steam at improving the overall quality of OOo code, which is a good starting point, and making easy testability of the code and quality assurance a priority. This is an area where new developers and code hackers, whose number has grown to over 90 in just a month, are instrumental for the bulk of the activity.

In addition, each single module of LibreOffice will be undergoing an extensive rewrite, with Calc being the first one to be redeveloped around a brand new engine – code named Ixion – that will increase performance, allow true versatility and add long awaited database and VBA macro handling features. Writer is going to be improved in the area of layout fidelity and Impress in the area of slideshow fidelity. Most of the new features are either meant to maintain compatibility with the market leading office suite or will introduce radical innovations. They will also improve conversion fidelity between formats, liberate content, and reduce Java dependency.

“The Document Foundation is going to be at the heart of the Free Software universe, where users want to build a different future for office suites, working together with developers”, says Italo Vignoli, a digital immigrant, and the oldest member of TDF Steering Committee. “Users read, write, modify and share documents, and are focused on contents rather than software features. After 20 years of feature oriented software, it is now the right time to bring back content at the centre of user focus”.”

The statements quoted above unveil several items. This is not a press release about the community itself, it’s a press release showing the result of a liberated community at work. And what does a liberated community at work do? Not only does it fix what can be fixed on the spot; it  is not shy in assessing whether the code base it’s working on is going to be relevant in 5 years and whether the state of the art has changed. Therefore we, the community, gathers around a few simple (but in fact quite complex ideas):

1. Our code base is getting old. Worse, the whole frigging software looks  and feels like we’re stuck in the Bush area. Many things were not fixed, some others need a complete rewrite.
2. The Document is really the epicenter, the conundrum’s point, and software should be built around it, not as if documents were some sort of odd appendices. It’s not just the user that matters, it’s that when the document is what the software is running for, rather than running with, you end up with much more ability to create, share and innovate.  In fact, designing software following this concept leads you to develop something quite different from office suites. That’s a shift of paradigm.
3. It’s time to realize people hate using office suites. You can make them more visually compelling, more practical, and we want that too. But it’s the tool that is the problem in itself. No one really knows why we have to stick to specific features; Powerpoint was a nice visual concept in the eighties; it became a management tool. Who could have guessed it?  Therefore, there is an urgency in making office suites fun to use, by allowing users to unleash their creativity, win time and efforts, there fore make their lives easier and more enjoyable.

The way the Document Foundation is going to address these issues is twofold: First, we will have incremental changes on LibreOffice, although these changes will sometimes be quite visible. This will allow to solve real and identified issues by maintaining the overall code stability and homogeneity. Second, we will open new development initiatives aimed at rewriting entire portions of the codebase (leading in the end to a complete rewrite) that we think are the most urgent to be rewritten. Mind, however, that we won’t have a rewrite for the sake of a rewrite. I think that Ixion, the spreadsheet rewrite project, will show that we’re in this game to change it. Yes you read well: Initiatives such as Ixion will not lead to a nice MS Office clone. It will be a radical departure from what we have today.

These two tracks will thus offer the choice between improved stability and radical innovation, and somewhere down the line, these two will merge, somehow. But that story has yet to be written.

Stay tuned!

In a nutshell, OpenSuse has been breaking away very slowly from its main sponsor, Novell, for about 2 and a half years. The first visible sign of this -which really was a weak signal nonetheless- was the decision taken by the community to switch back to KDE as their preferred desktop instead of Gnome. Of course, just like Mandriva/Mandrakesoft, Suse had always been more KDE oriented than  Gnome. Yet Gnome is where the business, the stability, and theenterprise applications are supposed to be found, and on Gnome lied Ximian, the Groupwise integration etc. Then the OpenSuse folks started to open a brainstorming plan in order to define a new strategy for OpenSuse, apparently independent of what Novell was planning to do or sell with respect to that. This strategy brainstorming session ultimately reached its conclusion a few days ago:

https://lite.co-ment.com/text/lNPCgzeGHdV/history-version/RE3kSeg3LGI/

As you will see, what OpenSuse intends to be is a general-purpose, desktop oriented distribution; which means at the same time that nothing will change in its actual orientations and that it even departs from its usual enterprise polish it always had had. But what this also means is that we will not see OpenSuse or Suse on handhelds or tablets or any other new markets. This is a significant information, especially if you see that whoever will buy the Suse part of Novell in early 2011 might not be able to have its own way if  it does not take the time to engage with the community: The OpenSuse project seems to be very autonomous and not at all ready to fall into whatever new goals any future sponsor might want to achieve. And if it takes a fork to dot it, there’s the Mandriva case.  But always remember that OpenSuse has a very strong userbase and market share, although it’s been declining ever since 2009. What will be interesting nonetheless will be what the future owner of the Suse brand will want to do and how it plans to innovate. OpenSuse can be a general-purpose distribution; the user base is there, but the value might be hard to create if there’s no real business story to tell behind it.

Back to Mandriva / Mageia now. It’s perhaps to early to say anything about Mageia, except they seem to be made of some pretty skilled  people; and that’s usually not the kind of engineers you find easily on the market. They claim to continue what Mandriva as a distro was good at, only in a better way, and without the perceived historical failures of the past management teams.

Interestingly enough, I think Mageia is bad news for Mandriva, and it means that Mandriva should find an innovative business model and acquire/change to a new focus. Let me explain. Reading the Mageia website and going around the Internet, here’s what I understand:
- Mageia realizes the need to be a linux distro for other kinds of
terminals (tablets, handhelds, etc.)
- Mageia has crafted two strong bulletpoints in its storytelling that DOES hurt Mandriva starting today: Mageia “is” Mandriva, since it is
made of the engineers who have coded Mandriva ever since a few years; second, Mageia is “better” since they understood what “is wrong”: the management of Mandriva. (Nobody ever found anything to complain about Mandriva as a distro, it’s still one of the best on the market).
- Mageia is soon to “take over” the market: everyone on the forums  seem to dig Mageia; and in a sense, it’s what the Mandriva community and the French FOSS community was expecting.

If the last claim sounds bold, think again: what is the value of having a Mandriva desktop outside of a corporate support contract (same goes for a server) now that there’s Mageia? The way to create value for Mandriva is to depart from the traditional all-purposes distribution model (which still does not mean they would have to “cut” the actual distribution) and innovate first at the distribution level, and then, if possible, go up the ladder by growing a very skilled technical team able to innovate as an operating system, either by contributing upstream again, which it hardly does anymore these days, or innovating on the user experience just like Ubuntu does and is now clearly intensifying as a strategy.

In the case of Mandriva and Mageia, what might become interesting to watch is the potential race between the two twin-distributions; one is now almost an empty shell, deprived of its developers, and the other one has developers but no resources. In any case, it’s time these two get a real shot at innovating, for the sake of the entire Free and Open Source Software ecosystem.

• Excellent post by Jean-Louis Gassée (French software genius, inventor of BeOS and former Apple employee) on Microsoft’s troubled future.
• There is, in a related but previous post, some hope about that though. I tend to agree with Mr Gassée here: I simply do not buy into the whole all-cloud, no-desktop system. It simply does not work no matter how large your bandwidth is. This being said, it will be interesting to see how Microsoft’s strategy with respect to cloud services and office suite evolves. As for OpenOffice.org, you might ask… Well, that one could also end up being interesting as well. But make no mistake on that one: Fat, Monolithic clients are out.
• Great post on combining some microformats, in this case OpenID & OAuth. Microformats are extremely important in Cloud contexts and are the most pragmatic tools to fight off cloud and social lock-in by companies like Facebook.
• The UK Government promotes open data. If only we could do the same over here…
• Don’t miss Steve Job’s & Steve Ballmer’s interview on All Things Digital, starting tonight at 6 pm California time!
• Last but not least, OpenOffice.org 3.2.1 is almost out. Last RC is looking good, so be prepared to download it.

I tend to think it’s a smart and calculated move by Google, as it was, among other things, noted that the company has a rather weak market share in China. By leaving the Chinese market it will not lose much, and will gain a lot of credibility and positive outlook that Microsoft has been working hard to undermine. The reaction of Steve Ballmer to the story is quite telling, and now he looks like the Borg again. But what I am quite amazed at is the amount of hypocrisy seen in the media about this issue.

Certainly, there is more that meets the eye when it comes to Google and PRC. But this story should have been the opportunity to remind the Free Market Integrists (the ones who believe Free Market actually exists and that we live in an ideal world – many of them, interestingly, were patented communists thirty years ago) that China does not play by the rules of the Free Market. China does not want to play by these rules and has slowly imposed its own rules, special labor laws, low currency, local joint-ventures, and now, a special Internet behind a Great Wall. Most companies fail to see that they will eventually lose, if that’s not already the case for some of them (the French Alcatel and Thomson companies are blatant examples of such “soon-to-be-departed” companies) and that only a few will survive a system they may have contributed to define, but one that automatically creates fierce competitors by the will of one government.

Google, for good or bad reasons, has decided it would stop to gleefully agree to whatever the Chinese leglislators would dictate, and only a few commentators have so far realized the change it has been compared to any other companies.  For the record, I am actually quite admirative of China, its culture, and how it managed to lure Western industries through greed into thinking that what they were going to get by outsourcing/working in China would automatically be a success. To some, it’s even become a duty, although they overlook the evergrowing lack of balance in our trade equilibrium with China.  Ideology has been the sickness of the twenthieth century. In our times, I am afraid ideology is still very prosperous.

But let’s go back to Google and China: Do not be shocked by Google’s move; rather, we should perhaps think at what kind of double standard in business, ethics, and politics we have to set when dealing with PRC. I am disappoined that few have noticed these skeletons in the closet, but I guess a pink elephant is always more visible than they are.