12 ms·

So I had to copy-paste my source code into a web site, submit, then copy-paste the text back out into my document? I'm not putting down the work the author did,

So I had to copy-paste my source code into a web site, submit, then copy-paste the text back out into my document? I'm not putting down the work the author did, but that workflow was always going to be completely obsolete at some point.

reactordev 2mo ago
for one-shots and non-developers, it was useful. Simply because you found no utility in it doesn't mean there isn't one.
- hyperhello 2mo ago
  I didn't say I found no utility, it could have tons of utility, but technology changes over time. Perhaps the gentleman author could have produced a desktop Electron app or something similar running locally.
  - nvme0n1p1 2mo ago
    Or a static HTML file served by (GitHub|Codeberg|Cloudflare|Vercel|Netlify) Pages, and run the formatting logic client-side.
    - reactordev 2mo ago
      It’s also entirely ok to manage something for a long period of time and reach your end. No shame in walking away.
      - Zancarius 2mo ago
        I think this is something to keep in mind whenever approaching a new project, especially solo. Eventually, the end of the road is unavoidable. I started teaching an (older) adult Sunday school class almost exactly one year ago this coming Sunday. I post the notes on one of my blogs. They're generated as a static site via Astro, and I have a few Markdown helpers for making it easier to link to scripture, etc., and while it's not a lot of work, I know I'll tire of it eventually. Or something else will come up. I doubt I'll be happy whenever it does, but I'm extremely appreciative of your comment for this reason. I hope I'll remember what you've written when that day arrives.