papereditor

8 ms·

1. 61.▲
   by papereditor 3y ago

   1. Sorry for the disappointment! SEO articles and high-quality thought pieces can coexist on a website - they have different purposes. The /blog slug is indeed a bit misleading, but that's what I started using initially, many year
2. 62.▲
   by papereditor 3y ago

   I don't want to be public with $, but I can say that it is many times smaller than my full-time European salary.
3. 63.▲
   by papereditor 3y ago

   Thanks! 1. What's wrong with SEO? People discover the app from Google. Some of them even become paid customers. If people discover and purchase what they need - what's the harm? 2. That does not affect the App Store search results
4. 64.▲
   by papereditor 3y ago

   Thank you!
5. 65.▲
   by papereditor 3y ago

   Thank you!
6. 66.▲
   by papereditor 3y ago

   Thanks! Can't recommend anything specific, to be honest. I've been piecing together information from old Apple docs, StackOverflow, API header files, and a bunch of really weird blogs. A lot of trial and error as well. I think you
7. 67.▲
   by papereditor 3y ago

   Thanks! Sorry, I'll try to make it more accessible.
8. 68.▲
   by papereditor 3y ago

   You are correct. Swift is lighter on the eyes, but it still uses the same APIs when paired with UIKit/AppKit. SwiftUI is a different thing though. It's like React for UIKit/AppKit and has a different API.
9. 69.▲
   by papereditor 3y ago

   Thank you!
10. 70.▲
    by papereditor 3y ago

    It's a calculated risk. You can make unique experiences with private stuff. Apple ships betas, so there is plenty of time to see if stuff breaks with the latest OS.
11. 71.▲
    by papereditor 3y ago

    The Markdown engine is bespoke. I don't follow any specs. Paper might be looser in what it allows than other Markdown editors. Practically no one had issues with that over the years. :)
12. 72.▲
    by papereditor 3y ago

    Thank you!
13. 73.▲
    by papereditor 3y ago

    Thanks! Still on TextKit 1. I am thinking of migrating to 2, but I still have downloads on older Macs, so I want to wait. Supporting both 1 and 2 in parallel would be a nightmare. To be honest, I have not experienced a lot of dramatic updat
14. 74.▲
    by papereditor 3y ago

    I have not investigated it, to be honest. If it's as easy as switching the compiler to Swift, and everything remains working as is, but I also get to use all the Swift stuff in addition to Objective-C, then I am clearly missing out!
15. 75.▲
    by papereditor 3y ago

    Thank you! Sadly, not enough to live off it in Europe. But it's slowly growing, so maybe one day. :)
16. 76.▲
    by papereditor 3y ago

    That would be a massive challenge and probably would lead to more bugs which is against my goal of having a low-maintenance product. The more dynamic is your text rendering, the harder it gets. You can format from the Preview mode, by the w
17. 77.▲
    by papereditor 3y ago

    Thanks! I've indeed forgotten about the RSS feed. That post was created in 2021, but I keep stuff up to date even for SEO content, so the update time is 2024. That said, those posts are purely for keywords - they have no value other th
18. 78.▲
    by papereditor 3y ago

    Thank you for the high praise!
19. 79.▲
    by papereditor 3y ago

    True! It's remarkable that even today, with millions of apps, you can still find paying customers through the App Store even if you are a nobody.
20. 80.▲
    by papereditor 3y ago

    Thanks! Indeed, there is TipKit. I've just learned about it a few days ago. I think so far when Apple added new features to existing components, they've always made dual APIs. Only some completely new things are Swift-exclusive. T
21. 81.▲
    by papereditor 3y ago

    Makes sense. I'll give it a try. Thanks!
22. 82.▲
    by papereditor 3y ago

    Thank you!
23. 83.▲
    by papereditor 3y ago

    Thank you!
24. 84.▲
    by papereditor 3y ago

    Sure. If I can assist in some way - I will. DM me on Twitter.
25. 85.▲
    by papereditor 3y ago

    Thank you for the suggestion! I've always avoided non-App Store distribution to keep things simpler. It's a nightmare to manage many different licensing schemes. Now I don't have to have any backend. Everything is done via th
26. 86.▲
    by papereditor 3y ago

    Sorry, I'll try to make it more accessible. It expands in the app as you hover over it. Probably needs a similar thing for the website. Or I just need to give up and revert it to the standard one. :)
27. 87.▲
    by papereditor 3y ago

    Thank you!
28. 88.▲
    by papereditor 3y ago

    Sorry, I'll try to make it more accessible. It expands in the app as you hover over it. Probably needs a similar thing for the website. Or I just need to give up and revert it to the standard one. :)
29. 89.▲
    by papereditor 3y ago

    Agree! It's a single form-over-function thing that I could not resist not to add. :)
30. 90.▲
    by papereditor 3y ago

    Interesting! So all the NS_SWIFT_UNAVAILABLE APIs are still easily bypassable in Swift?