Changes between Initial Version and Version 1 of Ticket #65415, comment 27


Ignore:
Timestamp:
Sep 23, 2022, 4:28:48 PM (2 years ago)
Author:
chillin-
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #65415, comment 27

    initial v1  
    11But I did use the information, and I've made the best decision based on the information given and in deference to my older hardware, for which I have previously compiled pdftk for specifically. Being that the hardware is discontinued, and the vendor switched platforms, it is exceedingly unlikely that further development will occur with the platform architecture, so I'll never realize whatever performance advantages Java may -possibly- provide. Further, the pdftk-java readme estimates that due to the differences in Java and C++, that it is likely there are bugs in the Java version and further testing is required. Though I don't use it everyday, I consider it a production machine, and being that I will not be able to go back if I find problems with the Java version, I have stalled out of an abundance of caution. Though it is widely accepted that native code is generally more performant than interpreted, regardless of Java getting a boost from faster hardware, native code will always be more efficient than interpreted, and there's nothing Java will ever be able to do about that until there are Java hardware engines on every motherboard, which will likely never happen because it defeats the purpose of Java's portability. I was being silly towards the end and did not intend to offend anyone, didn't intend to start a flame war, but if anyone is delicate enough to take offense, I will reluctantly accommodate, and if it is war you want then it is war you shall have, because it is all beyond my ability to care.
     2
     3Further, while I understand it is necessary to correct or add more information to original descriptions, and I don't doubt that I am making mistakes, I think it is a bad idea to vacate that description entirely and replace it. I reported the bug having discovered it on 10.14, and was shocked to see that all mention of 10.14 was removed from the description, and the title change, which I know is necessary because try as I may I haven't yet learned the title convention, it appears, incorrectly, this bug only existed on 10.8, 10.9 and 10.10. Leaving that information in the description would avoid future confusion. Just my opinion, and I am definitely not in charge, so just a suggestion.