I read all of it multiple times, before and after editing, and it’s clear to me that we’re failing to communicate.

Markdown and HTML are both examples of markup languages but that doesn’t mean that the words are interchangeable.

It is not possible under any circumstance to represent all that HTML supports within markdown.

Given that HTML supports significantly more formatting than markdown, it’s completely unsurprising that any conversion is imperfect, this is not a flaw in pandoc, it’s simply not possible.

I’ll also point out that I was suggesting that OP starts with markdown and converts that to a required output format using pandoc. The barrier to entry is significantly less than using LaTeX for example.

What are you talking about?

Write it in markdown, segment into separate files for different sections, use pandoc to generate the output.

That’s interesting. It does make me wonder … how does the Go community deal with malicious actors who “tweak” their “vendored” copy of a library, or am I missing something?

No worries, it’s 3am here right now 😁

I meant the users of your project.

This does appear to then break the chain of trust for the users of the project, since it then requires downstream to review even more code.

For example, if you’re an OSS user of three projects that each depend on library X, you now need to trust three copies of this library and make sure that they’re the same as the original.

This seems to be a solution that makes the problem bigger for everyone, not smaller.

So … using a dependency as a submodule?

I don’t understand the author’s description of forking vs. vendoring, the latter being a term I’ve never heard of.

Anyone got any links to something more descriptive?

On SOME ARM64 … but at least it’s a start.

What if it was supported on all hardware that Debian was supported on, that would be something worth getting excited about.

“That’s not a flaw … that’s a feature!”

Around the turn of the century I built a “middleware” layer for an Oracle to MySQL bridge which enabled legacy systems to keep running while modern and open source tooling could be built.

The biggest challenge was moving from columnar to row based data … that and compiling Solaris tools using Oracle libraries.

Oracle is like sendmail, user friendly, just very picky whom it makes friends with.

I’m getting flashbacks to debugging an Oracle connection file.

That was eye opening.

Wow, smash bugs, be in the running for prizes, including a skateboard … might give that a pass.

Puppeteer and Chrome were my go-to, but that was before AI bots started hammering sites, and Cloudflare and others started offering blocking processes to stop them.

I’d be surprised if the service you’re currently using will be effective for much longer.

As for text comparison, lynx -dump will give you the text and diff will show you the changes, but as you mentioned, that won’t show you the graphics and banners, unless the site actually uses accessible content.

Writing software is about problem solving skills which improve with practice. Often the process involves breaking down a problem into smaller pieces and breaking each of those down, until you know how to “solve” each problem.

Writing down each “solution” and stringing them together is then the actual “programming” part of this activity … which brings with it a whole new layer of “problems” to “solve”.

It’s as much art as it is accounting and the more you do it, the better you get at it.

Source: I’ve been writing software since 1982.

… and replace them with a whole new class of bugs.

Source: I’ve been writing software since 1982.

And if you think that migration to Rust will magically remove all bugs and vulnerabilities, you haven’t been writing software for very long.