inkscape VS rimraf

The contents are rendered through gtk/cairo which not only goes through https://www.xquartz.org/ but also doesn't use GPU rendering (it was experimental 3 years ago, maybe better now). The main issue seems to be that neither Inkscape nor gtk people have much low level Darwin experts or time available to invest in debugging the whole rendering stack. See for example https://gitlab.com/inkscape/inkscape/-/issues/1614 and all the other referenced issues for all the gory details.

There's a year old issue https://gitlab.com/inkscape/inkscape/-/issues/3227 with no visible progress and a medium priority label. I hope it gets more dev focus soon.

Here's a bug report related to this. Also here's a video of this bug with the oldest version of Inkscape that I still have lying around (0.94.2 i.e. 2019, but it's likely the bug is even older than that), and a similar thread on here from more than two years ago.

Yes. Only in specific circumstances, though. It's not really that big of a deal.

Arc handles can't be snapped and it's a known issue. It seems like you're using guides, though, so you can just double click the guide to get its angle and manually enter it as the 'Start' or 'End' angle in the toolbar.

This is a known issue. It seems like it's related to a new setting that was added in recent versions. In the preferences under 'Behavior → Selecting' disable 'Paste above selection instead of layer-top' to get the old, non-buggy behavior back.

See the ASCII table at https://www.rapidtables.com/code/text/ascii-table.html. Have seen it happen in Inkscape on Windows, too: https://gitlab.com/inkscape/inkscape/-/issues/4071

Inkscape bug: https://gitlab.com/inkscape/inkscape/-/issues/4043

And npmjs.com will block your IP if you do too many downloads in on day.

Actually is says 86m a week here: https://www.npmjs.com/package/rimraf

Huge thanks to Isaacs! Rimraf comes to the rescue, providing a reliable solution for deep, recursive removal of folders and files. At PURISTA, we rely on rimraf to maintain pristine build output directories.

Avoid platform-specific commands: Avoid using platform-specific commands in your scripts. Use cross-platform tools like Node.js or Bash to ensure that your scripts work on different platforms. For instance, if you want your npm script to remove a certain directory using the rm -rf command, this would work perfectly on a Linux or Mac machine but would error out on Windows. To avoid this, you can use a cross-platform package such as [rimraf](https://www.npmjs.com/package/rimraf).

rimraf

Babel will overwrite but not delete any existing files or directories in the output directory. To be sure the lib folder doesn’t contain old files you can delete it before transpiling. To do this automatically you can install rimraf and add it to the transpile script like this:

Many packages on npm are designed to make changes to the file-system, such as rimraf or a code linter. In an accident, the consequences of running file-system altering code can be detrimental.

Also, rimraf seems to be popular.

No, that's why there's a bunch of packages such as rimraf[0] that implements that sort of functionality in a cross-platform way that most people use in their scripts

[0]: https://www.npmjs.com/package/rimraf

Something that might work: rimraf. A small node script can churn through file deletion surprisingly fast on Windows. Used to use it to clear out npm packages directories at a greater than glacial pace.

Um actually I use rimraf