ReSharper and Visual Studio should be OS X compatible, it's not like every developer is using Windows. Such a monoculture.
See? It goes both ways (which, from your edit, I know you understand, but it's work a specific example). This guy's labor of love is a well crafted, thoughtful application for programmers using OS X. There is zero controversy there. Same with any other OS X-only application that Windows or (Li|U)nix users want.
When we beg for cross-platform apps from developers who don't understand all those platforms, we end up with web-browser-as-platform Electron-based apps that bundle a browser to render their UI layer. Sometimes that's done well (Visual Studio Code is quite nice) - often it's just okay bordering on slow. In fact, it's so rare that high-speed apps are available in some native form for multiple people platforms, I consider it a special gift to use one (Sublime Text comes to mind).
Let's not stifle the creativity and drive that small or single-person developer shops have by suggesting - even passively - that we are entitled to three OS-specific builds of anything they write.
If ReSharper was called "The Programmer's Refactoring Suite" or if Visual Studio were called "The Programmer's IDE" I would see your point.
I'm not simply referring to the decision to target a particular platform. That's fine. There's nothing wrong with having a narrow focus. But please stop pretending it's anything but a narrow focus.
Neither ReSharper nor Visual Studio communicate anything about their environment. That's call setting expectations. There is no expectation of what environment it's to be used with (although ReSharper sounds like c# a lot to me).
The issue with 'The Programmer's Notebook' is that the expectation is set at something like 'This is a notebook that will be generally useful for many types of programmers'. It's like the Physician's Desktop Reference. The name implies that it will be of general usefulness to anyone in that particular field.
So when I see the title 'The Programmer's Notebook', the expectation is that it will be something useful for all types of programming (embedded, linux, bsd, web, native desktop, rtos, etc).
Then the expectation is crushed because it's only usable if you have an apple device. That means a large swath of 'programmers' (whom this notebook is apparently supposed to be for) are not going to have access to it. Thus the whole thesis of the title is invalid. It's not the programmer's notebook, because many/most programmers are not going to be able to use it.
You seem to have missed my point. It's what those names don't communicate that makes them better. They don't make it seem like they're more broadly applicable than they are.
That said, the "sharp" in "resharper" actually does hint at its Microsoft nature, as it's the same sharp in "csharp"
And just to be even clearer, I'm not begging this developer to release their product cross-platform. I'm begging everyone in the developer community to communicate in ways that are less presumptuous. The way we choose to name things is an act of communication, and it seems to have failed in this case.
See? It goes both ways (which, from your edit, I know you understand, but it's work a specific example). This guy's labor of love is a well crafted, thoughtful application for programmers using OS X. There is zero controversy there. Same with any other OS X-only application that Windows or (Li|U)nix users want.
When we beg for cross-platform apps from developers who don't understand all those platforms, we end up with web-browser-as-platform Electron-based apps that bundle a browser to render their UI layer. Sometimes that's done well (Visual Studio Code is quite nice) - often it's just okay bordering on slow. In fact, it's so rare that high-speed apps are available in some native form for multiple people platforms, I consider it a special gift to use one (Sublime Text comes to mind).
Let's not stifle the creativity and drive that small or single-person developer shops have by suggesting - even passively - that we are entitled to three OS-specific builds of anything they write.