> >     and specifies additional shorthands for reading it.

I think it's fair to say, as the person who originally implemented shorthands,

that I don't agree with this change.

Providing two different ways to load an .el file so that each interns different

symbols into obarray would lead to unfortunate consequences where it would

be hard or impossible for humans or programs to understand the provenance of

a given symbol.

I cannot understand Richard's assertion that "shorthands are incomplete". 

Shorthands were primarily designed to solve the "the s.el problem", and the current

implementation available since Emacs 28 solves that problem already, IMO.

I've described how to do so multiple times in the past, but here goes again:

Anyway, here are the instructions again summarized:

1. Grab s.el from its upstream repository
2. Don't touch any of its code.  Just add this local variable
   definition to the end of the file.

   ;; Local Variables:
   ;; read-symbol-shorthands: (("s-" . "magnars-string-"))
   ;; End:

3. Rename the file from s.el to magnars-string.el.  Change its line

     (provide 's)

   to

     (provide 'magnars-string)

4. Include magnars-string.el in Emacs core or GNU/NonGNU Elpa
5. Tell the current users of s.el, say im-a-s-user.el, in the world to type

     (require 'magnars-string)

   instead of

     (require 's)