It was a response to a third party's legal demand, not a marketing fail. A change to the name used by the software is suggested, not just a change of the language name. In fact, the language name would not normally be an issue.
....Roy > On Sep 6, 2016, at 6:39 AM, Oliver Lietz <[email protected]> wrote: > >> On Tuesday 06 September 2016 00:03:22 Justin Edelson wrote: >> Simply put - because Adobe changed the language name. Since Adobe defines >> the specification and Sling just contains the implementation, it makes >> sense for the implementation to have the same name as the specification. >> Otherwise, we are implementing something which no longer exists. > > Sorry, I have to disagree. The language or spec is one thing, the > implementation(s) a different. Most prominent example is HTML itself and the > various rendering engines, e.g. Gecko, KHTML, WebKit, Presto, Tasman... > > We now have a break between names and modules/packages and a bunch of dead > links. That mess is totally unnecessary. Marketing fail. > > Adjusting the language name in Sling from Sighlty back to HTL (*sigh*) would > have been sufficient: Sling Sightly implementing (Adobe's) HTL. > > @Radu, can you please revert the changes in Sling Launchpad 8 and Sling IDE > Tooling 1.1 release news? The name of the language was Sightly at that time. > > Regards, > O. > >>> On Mon, Sep 5, 2016 at 2:16 PM Oliver Lietz <[email protected]> wrote: >>> hi all, >>> >>> why do we rename Sightly in Sling back to HTL? >>> >>> Thanks, >>> O. >
