Summary: | A hex editor with a 2Gb file limit is useless | ||
---|---|---|---|
Product: | [Applications] okteta | Reporter: | Henry Pfeil <hpfeil> |
Component: | general | Assignee: | Friedrich W. H. Kossebau <kossebau> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 0.26.9 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Henry Pfeil
2022-09-04 20:26:59 UTC
Hi Henry Pfeil, I am sorry Okteta does not serve your personal needs, and you only found out after trying it that it does not meet your criteria for what is "useful". Yet, for those who just need to peek and twist small-sized files even on 64-bit address systems (like myself) it works good enough. And yes, I would have liked to have time to implement support for endlessly sized data since the very start two decades ago (should be documented in code even), but always had too many other interesting things to do in life (the answer to: " why not a 64-bit version"). No reason though to no longer share the fruits of my former work with others under the GPL, which explicitly states that such licensed program is provided > "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, > BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS > FOR A PARTICULAR PURPOSE Would it have helped you if the description of the program (as done in the app metadata) would explicitly hint that there is a limit in supported file sizes? Might consider adding that there, to save people time and frustrations (but only when people actually read that and not just go ahead based on their assumptions :) ). For your needs, you might consider also giving wxhexeditor or ImHex a try (not tested myself). *** This bug has been marked as a duplicate of bug 182577 *** |