Of course you have the right to be disappointed. We all are. Not an attack dog, just a fellow Windows user.
Scribhneoir wrote:Really. They're giving a release time frame, vague though it is, after vociferously claiming time and again that they never commit themselves to release dates? Right.
So we can expect another six months of waiting, assuming that their fiscal year begins on January 1, and also expecting that they'll release it on the last day of Q2, not the first, if they release it at all.
I will point out they're not announcing a release date here, they are sharing their current forecast if you read the linked blog post. A nuanced difference, granted, but still a difference. No matter what happens, there's always someone ready to throw rocks.
A slight delay? Windows users have been told parity with Mac will come with the "next paid upgrade" for more than five years. So why did Mac get Scriv 3 more than a year before Windows? Because L&L is a Mac-based company offering a Windows version only grudgingly. If more resources and time had really been thrown at Windows than Mac, then we should have seen Scriv 3 before, or at least at the same time, as Mac users.
In one way, you're right. L&L is a Mac-first shop. The software as we know and love it wouldn't exist without specific features that were possible because they were tied to capabilities within the Mac OS text system. That means KB often doesn't have to write nearly as much code to implement feature X as someone on another platform would.
Scrivener for Windows 3.x *is* the next paid upgrade. They have been consistent. And if you have been following along with the betas (even if you aren't using them for day-to-day work as recommended), you will see that gap is actually narrowing at a noticeable pace.
Part of the large gap is that everything is being developed against moving targets that are VERY different. And it's not just MacOS and Windows you have to compare against; it's MacOS (all supported versions), Windows (all supported versions), and Qt framework (whatever the currently used version is). MacOS provides several fundamental capabilities and services that are core to how Scrivener works -- and these capabilities are not present in Windows. Parts of those gaps are made up by using Qt instead of writing Scrivener as a native Windows application, but that doesn't bridge everything, and so the Windows developers not only have to port and code the existing Mac features over to a different language and framework, they also have to spend quite a bit of time creating system libraries. Without seeing the source code. Without adequate documentation. Including, in many cases, recreating the bugs across various versions of those libraries so that all of the special use-cases buried in our Scrivener documents get recognized and handled properly so that the Windows version doesn't mangle our data or produce output that isn't consistent with the Mac version or iOS version. Or, I'm willing to bet, in many cases having to figure out why specific chunks of code in the Mac version are there and what Mac OS bug they're working *around* and analyzing it to figure if they need to include an equivalent workaround. Having to figure out the same sets of bugs in Qt and generate their own Windows-specific workarounds, and work with the Qt developers to report and get those upstream bugs fixed. Then upgrade Qt and see if it breaks anything else, and if it's faster to go fix those new bugs or stay with the current version and keep building code.
Writing that much software takes time. Testing it takes a lot more. It's just slow work. If you haven't done a significant amount of coding, it's hard to understand of describe the specific difficulties. But I'll point out that the Windows version has *two* developers who do nothing but work on Scrivener. The Mac version just has KB, who also works on Scapple and Scrivener for iOS. When they say they've put more resources into the Windows version since 2009, it's not hard to go back mentally, see what was being produced when, and realize that they're not exaggerating.
Being bitter about where we're at is certainly your choice, but what does it change? It doesn't make you any happier. It doesn't get the coding done any faster.