Closed orefalo closed 9 years ago
Software takes time and money to write.
While we do not officially support 2.x on Yosemite, all prior versions are downloadable here. You can workaround the crash by doing
$ defaults write com.chocolatapp.Chocolat "Hide Launch Bar" -bool TRUE
This needs to be made more easily discoverable. Spent about an hour today working out which archived version would even run (2.2.3 breaks things, 2.2.2 works, FYI), half of that attempting to track down this mythical "ticket with a fix" after a less-than-helpful tip by locks. #1642 #1621 #1638 #1635 #1618 #1616 were no-gos. (All because I'm too lazy to replace a EDITOR
and VISUAL
assignment in my shell.)
Extortion is a beautiful thing. One expects that paying $50 for something one could otherwise get for free (TextMate, Komodo, etc.) implies some level of ongoing support. Support that doesn't falter at the release of a new underlying OS version that, apparently, broke an entirely cosmetic feature.
If I claimed that "Chocolat 2 works on Yosemite" then I would have to actually deliver that. People would expect it to work properly. I don't have the resources to support two versions of Chocolat at once. I can't even build 2.x anymore because Apple removed support for GC in Xcode. Is it really so egregious to draw a line and say "we're not supporting this, it's too much work"?
I am really befuddled by people who are paid 5, 6 figure salaries and can't afford a $15 update to use a primary development tool on a new OS they just installed. But not surprised.
An OS upgrade that is free, and mandatory for continued support by everything else going into the future. (So not exactly optional.) It's not like I'm switching from Mac to Linux, here.
It wouldn't be egregious if Chocolat cost $15 in the first place, of if there weren't free alternatives. But it was instead priced at a premium, one which is now rather clearly unfounded. (How's that Python 3 support coming? Examining the truffle, not so well even years later and after a rewrite.) As it is, it cost me less to find an App Store-provided alternative with proper iCloud support and support for Python 3… even considering a double purchase, once for desktop, once for mobile.
Boo hoo, Apple changed their APIs. Couldn't you, in theory, keep an old, not-updated box around to compile things? Your argument swings both ways and is ludicrous for both.
I simply expect software I pay such a premium for to continue to operate. As a user, the whiny details about why something can't be supported do nothing to alleviate the fact that you are extorting (obtaining by force, threats, or other unfair means) additional coin from your existing user base instead of, I guess, having sufficient new user base to pay for ongoing development.
The typical pattern is to drop support for old platforms, not drop support for current platforms unless someone pays more. The latter appears as nothing more than an extended digitus me'dius.
Why the hell do you force people into a $15 purchase?