The talk emphasizes debugging js as output of another language. But did I understand correctly that it can be used to debug js programs directly? Makes sense and would be awesome.
Great job - again.
406 karma · joined January 4, 2011
The talk emphasizes debugging js as output of another language. But did I understand correctly that it can be used to debug js programs directly? Makes sense and would be awesome.
Great job - again.
I am extremely familiar with clean room reverse engineering. You are absolutely mistaken if you believe that 'That's what you have to do to copy software without infringing its copyright.' Reverse engineering actually has a rather different history. Given a device, say a chip, take the inputs and outputs of said device which defines the machine's behavior. Now design and build a machine which reproduces such a mapping. This practice was frequently associated with 'clean room' protocols. The key point is that the team had absolutely NO access to the source code. And because such a clean room team would never hire anyone who had previously had such access they could be confidently said to have reverse engineered the behavior from the APIs alone. This is a VERY different situation.
The section which Linus is almost certainly referring to is the claims. These are indeed expressed in a technical vocabulary which is tricky for a lay person to penetrate.
But the section which is supposed to enable a person ordinarily skilled in the art to be able to make the invention is not written in such vocabulary. On the contrary, it typically written in language which is perfectly comprehensible. The difficulty if any is in having the patience to read a tediously long description with endless references to diagrams.
The idea that software development is the sole province of the lone inventor is both wrong and irrelevant. The reason that our constitution facilitated patents was nothing to do with how many people invented something but rather with encouraging disclosure of the result.
If we stipulate that software patents are frequently violated...so what? Without further analysis of why or whether specific improvements to the system would be helpful this is a dangling factoid - no more.
Finally, the idea that copyright provides any kind of protection for software is so ludicrous the writer's naivety is laid bare. Copyright protects only the expression of an idea. In the case of a work of art such as a novel or painting the expression is critical to the work and copyright is a valuable protection. But if a programmer sits with original source code before him and rewrites it in another language thereby benefiting enormously from the original work but changing the expression completely they may indeed be programmers writing "their own code" but it certainly isn't "from scratch", and whilst he is right that "they can be confident they aren't infringing others" it is blindingly obvious that they have copied. Copyright is worthless if the expression doesn't matter and all that matters is functional equivalence. And guess what, users don't give a rat's ass how a program is expressed so long as it works.
The issue is often framed in terms of all patents being bad, or all software patents being bad but to anyone to gives the matter more than the kind of superficial thought stemming from ideology the reality is rather more complicated.
Well guess what - that is not unusual when everyday words migrate into a technical area and the law is such an area. To complain about words having specialist meanings in a specific subject area strikes me as naive.