🚀 go-pugleaf

There were some misunderstadings resulting from my posting about
_Launch so let me try and clarify.

1.  Sublaunching is an extension to _Launch.  Programs that call
_Launch (transfer menus, etc...), will still work with System 4.1.

2.  Sublaunching is available using System 4.1 or higher.

3.  One application launching another however, is a discouraged
practice.  There are some applications that must do this (integrated
development systems for example), but most applications don't need
to.  The reason for the discouragement is that at some point
in the future (a year perhaps, the crystal ball I'm looking into
isn't all that clear), _Launch MAY change or go away and everything
that calls it will not work.

The Finder is the application that should be used to launch applications.
In the future, it may provide better integration for applications and
you would circumvent this if you tried to take over its role by calling
_Launch.

_Launch will only go away if it is absolutely necessary.  We don't
break applications for fun.  There will be heated discussions about
it.  But there may be a time when we have to make a decision between
major improvements to the MacOS and breaking a few applications and
we will choose to break apps.  (We will however, give developers
notice and a chance to change their products before the change
takes place)

Sorry for any confusion or panic I caused with my first posting,

Fred