Language Selection

English French German Italian Portuguese Spanish

Linux Foundation Commits Suicide as Microsoft E.E.E. Takes a Leap Forward

Filed under
Linux

I have covered Microsoft's interference with FOSS for over a decade and carefully studied even pertinent antitrust documents. I know the company's way of thinking when it comes to undermining their competition, based on internal communications and strategy papers. Even days ago we got this in the news.

The pattern of embrace and extend (to extinguish) -- all this while leveraging software patents to make Linux a Microsoft cash cow or compel OEMs to preinstall privacy-hostile Microsoft software/apps with proprietary formats (lockin) -- never ended. What I see in the Linux Foundation right now is what I saw in Nokia 5 years ago and in Novell 10 years ago -- the very thing that motivated me to start Boycott Novell, a site that has just turned 10 with nearly 22,000 blog posts.

It is a saddening day because it's a culmination, after years of Microsoft 'micro' payments to the Linux Foundation (e.g. event sponsorship in exchange for keynote positions), which will have Microsoft shoved down the throats of GNU/Linux proponents and give an illusion of peace when there is none, not just on the patent front but also other fronts (see what Microsoft's partner Accenture is doing in Munich right now). The links below are a complete list of the bad (in my view very bad) news.

"We need to slaughter Novell before they get stronger….If you’re going to kill someone, there isn’t much reason to get all worked up about it and angry. You just pull the trigger. Any discussions beforehand are a waste of time. We need to smile at Novell while we pull the trigger."

--Jim Allchin, Microsoft's Platform Group Vice President

In the news today:

More in Tux Machines

FLOSSophobia

I have seen it many times. "Linux is a cancer". "Open sauce". "Linuxtard". I even remember the teacher who did not bring a laptop for her presentation and, when I offered her my Linux netbook, she rejected it as if I had presented her something illegal. She tried to use an old Windows computer instead but, when the computer failed, she ended up displaying her presentation with my Linux netbook. Clearly, this teacher's position was not based on ignorance or lack of expertise because she knew Linux existed and all she had to do was to display slides. Her refusal was due to indoctrination: she had learned that Linux and non-Microsoft office suites had to be rejected. Read more

Today in Techrights

Hands on With elementary OS Powered Centurion Nano Laptop by Alpha Store

If you want to buy a new laptop, no doubt you should consider the Centurion line. It will be a good choice for you, Linux aficionado. As well as for your Windows-addicted husband/wife/employees. The Centurion Nano is certainly not a “gamer” laptop. However, besides that particular use case, and for an interesting price, you will get a very competent computer, 100% compatible with Linux and usable for a broad range of tasks. Read more

Tryton and Python Deprecation Warnings

  • Trying Tryton
    The quest to find a free-software replacement for the QuickBooks accounting tool continues. In this episode, your editor does his best to put Tryton through its paces. Running Tryton proved to be a trying experience, though; this would not appear to be the accounting tool we are searching for. Tryton is a Python 3 application distributed under the GPLv3 license. Its home page mentions that it is based on PostgreSQL, but there is support for MySQL and SQLite as well. Tryton, it is said, is "a three-tier high-level general purpose application platform" that is "the core base of a complete business solution providing modularity, scalability and security". The "core base" part of that claim is relevant: Tryton may well be a solid base for the creation of a small-business accounting system, but it is not, out of the box, such a system itself.
  • Who should see Python deprecation warnings?
    As all Python developers discover sooner or later, Python is a rapidly evolving language whose community occasionally makes changes that can break existing programs. The switch to Python 3 is the most prominent example, but minor releases can include significant changes as well. The CPython interpreter can emit warnings for upcoming incompatible changes, giving developers time to prepare their code, but those warnings are suppressed and invisible by default. Work is afoot to make them visible, but doing so is not as straightforward as it might seem. In early November, one sub-thread of a big discussion on preparing for the Python 3.7 release focused on the await and async identifiers. They will become keywords in 3.7, meaning that any code using those names for any other purpose will break. Nick Coghlan observed that Python 3.6 does not warn about the use of those names, calling it "a fairly major oversight/bug". In truth, though, Python 3.6 does emit warnings in that case — but users rarely see them.