Re:The choice was probably about cost...
on
Nessus Closes Source
·
· Score: 2, Interesting
What about a partnership? While the other security company offers appliance solutions using Nessus, the Nessus developers could write better and more focused releases to accommadate with the business demand. Seems like a win-win to me. Any other thoughts?
The VAX C compiler compiles the loop into 2 instructions (a movw and a sobleq,
I think.) As it turns out, this loop was the bottleneck in a real-time animation playback program which ran too slowly by about 50%. The standard way to get more speed out of something like this is to unwind the loop a few times, decreasing the number of sobleqs.
What exactly is a sobleq? i'm assuming it's a VAX assembler statement, but i've never seen it before and was wondering if any of you knew how it worked.
for data to be shared and recognized as distinct fields of information, won't there need to be standardization across all hosts in order to use the data in any comprehensible way?
ie.
<product> Acme(tm) xxxxx </product>
on host #1
while on host #2 the same item is recognized as:
<saleitem> Acme(tm) xxxxx </saleitem>
how will the semantic web describe and relate items which are recognized as an item for sale but under different labels?
Another one is: When changing the original will take longer than rewriting from scratch.
If this is the *only* reason for a rewrite then it is a ill fated one. Unless the original design or architechure is incompatible with the introduced change, a rewrite because of time will only reintroduce new bugs or cycle the old bugs back in. However there is the case of management seeking a faster return time . . .
And now besides the 99% of the population who will buy them and not modify them, there will be an added percentage bonus from the scientifically applied hobbyists who would never have bought one before.
Slashdot Mirror
quotes within quotes equals single quotes
What about a partnership? While the other security company offers appliance solutions using Nessus, the Nessus developers could write better and more focused releases to accommadate with the business demand. Seems like a win-win to me. Any other thoughts?
Thanks
for data to be shared and recognized as distinct fields of information, won't there need to be standardization across all hosts in order to use the data in any comprehensible way?
ie. on host #1while on host #2 the same item is recognized as:
how will the semantic web describe and relate items which are recognized as an item for sale but under different labels?
Another one is: When changing the original will take longer than rewriting from scratch.
If this is the *only* reason for a rewrite then it is a ill fated one. Unless the original design or architechure is incompatible with the introduced change, a rewrite because of time will only reintroduce new bugs or cycle the old bugs back in. However there is the case of management seeking a faster return time . . .
Just my [2] sense of things
john
And now besides the 99% of the population who will buy them and not modify them, there will be an added percentage bonus from the scientifically applied hobbyists who would never have bought one before.