[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Piping contents of SVG directly to stdout
From: |
Andrew Bernard |
Subject: |
Re: Piping contents of SVG directly to stdout |
Date: |
Mon, 18 Jul 2022 13:23:29 +1000 |
I'd avoid WSL like the plague. It's still half hearted, terribly
slow with various filesystems and offers no advantages that I have
seen so far over simply putting in Virtualbox and running full
blown Linux of your choice. This is not merely my own opinion -
there are dozens of websites mentioning the same thing. No need to
detain the list further with all the gory details. Microsoft is in
no way committed to Linux and sadly it is not a glorious new era.
Andrew
On 18/07/2022 1:12 pm, DoubleFelix
wrote:
So
You could also use the Windows Subsystem for Linux, which is
easy to install as far as I could hear (yes, Microsoft
officially
provides an option to install Linux these days, which speaks
volumes...)
Re: Piping contents of SVG directly to stdout, William, 2022/07/18
- Re: Piping contents of SVG directly to stdout, Henning Hraban Ramm, 2022/07/18
- Re: Piping contents of SVG directly to stdout, DoubleFelix, 2022/07/18
- Re: Piping contents of SVG directly to stdout, David Wright, 2022/07/18
- Re: Piping contents of SVG directly to stdout, DoubleFelix, 2022/07/18
- Re: Piping contents of SVG directly to stdout, William, 2022/07/18
- Re: Piping contents of SVG directly to stdout, Jean Abou Samra, 2022/07/19
- Re: Piping contents of SVG directly to stdout, DoubleFelix, 2022/07/19
- Re: Piping contents of SVG directly to stdout, Jean Abou Samra, 2022/07/19
- Re: Piping contents of SVG directly to stdout, DoubleFelix, 2022/07/19