Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
10.10 is "archaic" to most modern devs. Unless the dev explicitly goes out of their way to support older platforms (some wonderful devs like developer of DriveDx do this), assume that the min version specified in info.plist is probably wrong. It probably may not be too hard to get it working on 10.10 though by polyfilling the missing functions on your end.

Also uncle bob is a bit... controversial
 
There's nothing "archaic" about 10.10 in my book. Many apps that I use and regulary update work on systems going as far back as 10.6. DriveDx is no exception. The problem lies with those coders that don't give a s*** about anything older that their own machine and their OS.

In that one particular case it wasn't a plist, it was a single framework, compiled by someone on his new shiny machine resulting in 'symbol not found' error. Swapping the framework from previous release fixed it. Now, how careless is that?
(All other binaries were 10.9 compatible, btw.)
They also forgot to put one tiny png into resources folder, resulting in small glitch in app's UI. I had to go back to 8 year old release to find that png. This tells a lot about their attitude towards what they do and are trying to sell. For almost a grand!

Uncle bob might be controversial on other topics, but what he says in that fragment absolutely makes sense to the rest of the world. He's right about ethics. He's also right that programms are products, like everything else, that the rest of us expect to work flawlessly out of the box. Not run beta test for sloppy coders or report bugs.
And, he's right about uploading betas. Amost all the apps that I have checked with Apple's Instruments, leaked. Apple's own stuff was mostly clean.
Shipping debug versions instead of release is also almost a norm these days. Stripping symbols? Nah, only losers do that. I can go on and on.
The latest plague that I've encountered on several occasions in commercial (and expensive) apps is Clang's profiling compiled in and active. As a result it creates profraw files (quite large) on the disk and confuses or even scares regular users. What the heck? Who do they think we, customers, are for them? Guinea pigs? At our expense? That's perverse!
 
Last edited:
>Stripping symbols

Stripping symbols is usually not worth any benefits it gives, and makes it much harder for the power-user to go through a backtrace. Most of apple's own binaries still have symbols. On windows stripping is not an issue because of its good symbol server integration, and on linux you usually have the source.
 
He's also right that programms are products, like everything else, that the rest of us expect to work flawlessly out of the box. Not run beta test for sloppy coders or report bugs.

When you pay for the program, yes. Your unhappiness here was initially about an originally open-source community-maintained software product which MacPorts implemented a port for, and I fixed that to build on older systems including powerpc.
Which party in this chain owes anything to potential users? )
 
  • Like
Reactions: repairedCheese
converseen.png


With the kind help of the developer who bothered to debug an archaic version of the app, I got Converseen working on PPC now. It is not a replacement for professional photo apps, but it is functional to convert RAW into whatever one needs.

UPD. The fixed version has been merged to MacPorts master.
 
Last edited:
Then I guess that’s a wrap. I can’t verify because there’s no way I’m going to attempt a full install on Leopard after the week of the Tiger port install. I will submit bug reports to the hub in hopes somebody sees it eventually. Though the fact that it’s apparently been a known issue for Tiger makes me less optimistic.

oj, man some on it can’t be that serious 😆 I get the same feeling when the kid at Wendy’s argues about the difference between a “plain” vs “dry” sandwich but what am I going to do? Ain’t worth the shake.
 
Then I guess that’s a wrap. I can’t verify because there’s no way I’m going to attempt a full install on Leopard after the week of the Tiger port install. I will submit bug reports to the hub in hopes somebody sees it eventually. Though the fact that it’s apparently been a known issue for Tiger makes me less optimistic.

oj, man some on it can’t be that serious 😆 I get the same feeling when the kid at Wendy’s argues about the difference between a “plain” vs “dry” sandwich but what am I going to do? Ain’t worth the shake.

I do understand that compiling gcc from scratch takes time. However, one does not need to do it every time building something. Once you have built gcc7, cmake and icu, just leave them installed. There are not too many “normal user” apps which take forever to build.
You obviously have no obligation to update everything whenever MacPorts updates it. (To avoid updating of dependencies, use -n flag. For example, sudo port -n install or sudo port -n upgrade.)
In essence, one needs a one week investment to have a build system for pretty much anything. And I do not mean 8 hrs/day for a week, of course, the process is supposed to be more or less unsupervised. Initiate it and leave the machine struggle for how long it needs.

Avoiding 10.4 will certainly make life easier in this regard. Tiger is painful, mostly untested and will have things broken. (I mean, I don’t mind anyone working on 10.4, of course, this is merely a precaution.)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.