Posted by Steve Litt on
URL: https://discuss.asciidoctor.org/Modernize-asciidoctor-css-tp7890p8014.html

On Sun, 17 May 2020 08:57:35 -0700 (MST)
"edsa [via Asciidoctor :: Discussion]"
<[hidden email]> wrote:

 
> I was wondering whether removing support for traditional .css files
> and only keeping .scss would make asciidoctor more dependent on a ruby
> installation/server.

I haven't been paying a lot of attention to this thread, but when I
hear the phrase "removing support for traditional .css files", that
scares me to death. As a Troubleshooting Trainer, developer, website
owner, content manager, creator and maintainer, I've never seen a
technology as valuable and well designed as CSS.

Adding an alternative to CSS is fine, as long as CSS is retained and a
policy is in force to keep CSS as a first class citizen until it has
been unused for several years.

New technologies come every year, and the marketing is always the same:
"Technology X is over 15 years old and is obsolete, our new technology
solves all the problems of Technology X."

New technologies always claim to be better because they're newer,
but in the vast majority of cases, the newer technology is more of a
"Johnny come lately", to be replaced in a year or two by another Johnny
come lately. Only a relative few rise to the top, stay on top, to stand
the test of time. CSS is one such technology.
 
SteveT

Steve Litt
May 2020 featured book: Troubleshooting Techniques
     of the Successful Technologist
http://www.troubleshooters.com/techniques