Linked by Thom Holwerda on Mon 8th Oct 2012 09:24 UTC
Thread beginning with comment 537840
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Can anyone justify such a system ?
by Thom_Holwerda on Mon 8th Oct 2012 17:14
in reply to "RE[5]: Can anyone justify such a system ?"
RE[7]: Can anyone justify such a system ?
by silix on Mon 8th Oct 2012 18:16
in reply to "RE[6]: Can anyone justify such a system ?"
Your code is protected by copyright. What's good enough for an author is good enough for you.
except that i'm not an author, and a sw is an industrial product resulting from a development process and containing technical and design features, more like a car than a book... now, the car as an industrial object is patentable at all levels (from the suspension strut arrangement to materials - eg pvc laminated steel, or new more efficient noise aborbers - in the product itself, but also the part stamping / welding / mounting process itself - eg friction for welding different metals like steel and aluminum.. and so on and so forth) wherever something novel was adopted
and i doubt you'd call an automotive engineer "a line drawer" based on the fact that blueprints result from the design process...
but then why only those working on sw shall be degraded to second class industrial world citizen and deserve lesser consideration than their colleagues from other fields, just because they happeen to use a keyboard?
RE[6]: Can anyone justify such a system ?
by JAlexoid on Tue 9th Oct 2012 00:43
in reply to "RE[5]: Can anyone justify such a system ?"
the thing is, not always, not forever
So you want the monopoly forever now?
there's no such thing as obvious stuff, otherwise it would have existed since the dawn of time - but actually it hasnt, and took some guy (who most likely didnt think he was doing something obvious at the time) to materialize
Total BS! Obvious does not mean that everyone just knows. Obvious had a very specific definition - a person skilled in the art could replicate the invention without prior knowledge of said invention. And "tada!" most of the stuff that is covered by software patents is like that.(And pretty much is a response to most of the rest of your comment)
RE[6]: Can anyone justify such a system ?
by l3v1 on Tue 9th Oct 2012 15:19
in reply to "RE[5]: Can anyone justify such a system ?"
but, there exist millions of sw patents, and though many are about stuff that by today's standard we dismiss as trivial or appear as a mere application of an everyday "something" to the IT field, most of them trivial are not
There seems to be noone out there who would take into consideration that the computer and software field and industry evolved and changed multiple times more and much much faster than any other field out there, and people still seem to think the same patent laws that seem to somewhat work in other fields can be used in the same form for the computing and software industry. Which is crazy a** stupid. Yet, it seems to remain the practice, and no wonder we can see a lot of flaws and drawbacks in doing so. Anyone who still advocates the applicability of the current US patent system for such purpose is very close to an ignorant bum in my eyes.
Just my 0.02 of course, as always.





Member since:
2006-03-01
bad guess then, because i'm actually a sw engineer
just, one who doesnt believe in security by obscurity but OTOH believes that sw development methods (see later) and the possbility to protect IP are orthogonal matters...
the thing is, not always, not forever:
there's reverse engineering;
there are code leaks;
and there's open source
let's say i develop a product using a (more or less) public source tree to suit a business model that i may chosen (based on expertise and customisation rather than initial license fees) and to involve and allow other parties to cooperate
this doesnt mean i alienate any rights to patent the techniques that i use for the internals of the product, or that anyone who happens to have a look at the code and learn about them, is ok with reusing them in his own product...
google's ip has been protected by obscurity, shall we assume it's the only possible way for anyone else?
there's no such thing as obvious stuff, otherwise it would have existed since the dawn of time - but actually it hasnt, and took some guy (who most likely didnt think he was doing something obvious at the time) to materialize
but, there exist millions of sw patents, and though many are about stuff that by today's standard we dismiss as trivial or appear as a mere application of an everyday "something" to the IT field, most of them trivial are not
design patents are mostly about the aesthetics of a product, technical solutions (inventions), which also are fit for protection, fall under a different category...
more or less like about cars... the bodywork shape is one thing, the way the chassis is made is another(or you think hydroforming, or more recently, aluminum/steel welding processes are not patented with all the research that has gone into them?)
as frivolous or useful as it may be (like all *inventions* in any product field) it's a sw *invention* that noone else had before (then it's not obvious) anyway, and deserves protection as such...
unless the patent is negotiated for licensing and royalties are paid, usually... why does nobody ever take this option into consideration?
so if the several-decades protection time window is (rightly) too long for the sw field, the patent system shall be abolished altogether instead of thinking about a shorter patent lifetime?
except when it's not..
but since the interaction model accounts for only a part of a program's development effort, you'd be leaving behind those working on the rest...
Edited 2012-10-08 17:04 UTC