Hacker News

points by the__alchemist 3 days ago | 0 comments

What does this mean in practice for software you write? What OSes to you build it for, and what OS or GUI-specific conventions to you follow which don't apply to others?

edit: Link software you wrote's installation instructions.

[–] floydnoel 3 days ago

You can just look at my profile and see some of it, or check out my website. I’ll have a new app to show soon, so stay tuned!

[–] the__alchemist 2 days ago

Those are web and mobile apps... Not PC software.

[–] floydnoel 2 days ago

web and mobile are both platforms with their own special quirks, APIs, and behaviors. however, you missed that Logbook Ed also runs on macOS.

[–] the__alchemist 2 days ago

I will just throw this out there:

- You have made the choice to make software only run on MacOS, excluding the (majority) of users who are not using that. This is balanced against the upside of native look and feel.

- I agree that web and mobile have many differences when comparing them to each other, or to PC software. The differences and conventions which relate to application development between Windows, MacOs, and Linux are much smaller than those. (The only concrete example mentioned in this broader discussion was Home and End keys can have different behavior). I see this as a matter of degree, not kind.

I keep coming back to "So, we are deliberately limiting our software to a single OS because... (Vaguely articulated reasons about native look and feel? About cross-platform applications having "bad UIs" and "subpar results"? I can't do anything with that because it's too vague, and doesn't match my experience. Home and End keys or other keyboard shortcuts which are easy to feature-gate if the GUI kit doesn't handle it which it probably does?) When weighing pros and cons, I need to see the cons.