Language Selection

English French German Italian Portuguese Spanish

M$/TomTom Lawsuit

Who's copying who isn't a clear cut case

The rise of MS is also an adventure of copyright violations and exploitation of weak patents. The computing industry has existed for a long time now and has for several years been an integrated part of people's daily life. Code that in the past was viewed as Mr. Merlin's magic is today is today a knowledge shared by many, even outside corporate buildings. Therefore I think this is more a testimony of how deprecated the whole idea of how patents work in this industry is. There's always a breaking point when something becomes common knowledge and therefore can't be viewed as intellectual property.

But of course if carton box still needs 6 (or is it 9?) patents printed on it in the US then probably FAT must be viewed as rocket science worthy of Nobel price to its initial author. Since exploitation of patents in itself is a lucrative business in the US you've got printed black on white that the system has to be overhauled. As it is now everything imaginable and thinkable beyond a coke and burger is valid to be patented. MS isn't alone in this silly brainstorm game; a look at many company's patent portfolios reveal the same.

No, I don't think this MS/TomTom thing is anything else but an attempt to strengthen a business model of living well on weak but never challenged patents. In view of how the market is changing faster than MS is able to adopt, it might be a "smart" move to make sure your economical future is a bit more secure even if your software fails, or sales of it.

The premesis and qualifications for a patent...

is an important question. A patent system isn't a universal unchangeable set of rules. Hence patent systems differ and what might be a valid patent in one country isn't even qualified to become one in another.

Emotions aren't of any interest and you're actually allowed to comment with a portion of playfulness with words, aren't you? If a patent system doesn't fulfil its intentional purpose it has become unproductive and in need of an overhaul.

I assume you don't like Bilski's arguments for a change of the US patent system? I fear that the lobby against such changes is too strong in both influence and money, but I believe the suggested changes would stimulate innovation and remove some of the obstacles to innovations. As of today it's difficult for innovators with limited money resources to defend their innovations.

Therefore my answer to your question [or questioning of my understanding] is: it's not good enough to only know current patent laws, it's even more vital to defend the initial purpose of them and strengthening them accordingly. We might have different opinions on the matter without the need to ridicule one another.

Schestowitz

Do you need glasses? Perhaps you should try one of those screen magnifier app's so you don't have to inflict the rest of us with your over sized type.

Obama, fix you f*ing system

"Since the birth of the Republic, the U.S. government has been in the business of handing out "exclusive rights" (a.k.a., monopolies) in order to "promote progress" or enable new markets of communication. Patents and copyrights accomplish the first goal; giving away slices of the airwaves serves the second. No one doubts that these monopolies are sometimes necessary to stimulate innovation. Hollywood could not survive without a copyright system; privately funded drug development won't happen without patents. But if history has taught us anything, it is that special interests—the Disneys and Pfizers of the world—have become very good at clambering for more and more monopoly rights. Copyrights last almost a century now, and patents regulate "anything under the sun that is made by man," as the Supreme Court has put it. This is the story of endless bloat, with each round of new monopolies met with a gluttonous demand for more."

--Lawrence Lessig

If they can uphold the

If they can uphold the patent, then they can make all the other companies using FAT pay up. Easy money.

More in Tux Machines

Slackware Live Edition – on its way to 1.0?

Last week the second Beta of the upcoming Slackware 14.2 was released. My goal was to have a new Beta of my liveslak ready by that time, so that I could provide new ISO images to test the Slackware Beta2 on a live medium. Unfortunately, there was an attack of the flu in my team at work and things got a bit busier than usual. There was a plus side to this: some last moment bug fixes which could be applied to my scripts – the result of having more evenings available to test. Therefore the new release is not labeled “0.5.0” but “0.5.1” Read more

Leftovers: KDE

  • Cantor migrating to Phabricator: which tools our contributors must to use
    Projects and software developed by KDE community are going to migrate for a new tool to manage our code, commits, reviews, tasks, and more. This tool is Phabricator and you can visit the instance for KDE projects in this address. Since November 2015 we are migrating Cantor to Phabricator. After our first successful review code some days ago, I decided to write a post about which tools our contributors must to use while the migration process is not finished.
  • Kdenlive's sprint report
    Last week-end, Vincent and me met in Lausanne for a Kdenlive sprint. One of our goal was to merge Gurjot Singh Bhatti's GSoC work on curves for keyframes. This was more work than expected and we spent many hours trying fix the curves and make keyframes behave correctly. Not much time was left for sleep, but we still managed to get outside to make a group (!) picture in the woods above Lausanne.
  • Jekyll 3.x
    I’ve found three different types of transition issues (it is cool to look at these in a project I do not upgrade on a daily basis like Plasma and the rest of the KDE software).
  • kdev-python on Windows: try it!
    I spent the last two or three days playing around with KDE on Windows, with the aim of getting my Python language plugin for KDevelop to run there. In the end, it wasn’t that hard to get this to work — not as hard as I would have expected it to be, anyways.

Manjaro ARM launched

Hi community, wonderful news in regard of architecture expanding within Manjaro Linux. It all started with a simple post on our developers mailing list. Somebody wants to do Manjaro for ARM … Just after one month of development our first alpha release is now ready. So what is this all about? Manjaro Arm is a project aimed to bring you the simplicity and customability that is Manjaro to ARM devices. These devices are growing in numbers and can be used for any number of applications. Most famous is the Raspberry Pi series and BeagleBoard series. Read more

Plasma 5.5.4 and Calligra Suite 2.9.11 now available

The 4th update for KDE's Plasma 5.5.x series is now available to all Chakra users. According to the release schedule, unless new issues occur, this will be the last update for this series before 5.6 gets released next month. Plasma 5.5.4 as usually includes a month's translations and bugfixes, with the authors highlighting the improvements for handling multi-screen setups. The Calligra Suite also receives a bugfix update to version 2.9.11, which mainly provides fixes for krita and kexi. Read more