[mapserver-dev] New MapScript API Docs

[Howard Butler]

>
> Why do you want to kill MapScript?  I have poured everything into
> mapscript.
>

To kill MapScript is a running haha-but-serious joke I've had going for a
long time with some of the MapServer developers. My case to do so is that
MapScript has never been on par with mapfile and the mapfile definition for
specifying objects and their relationships. Object lifetimes and their
relationships were historically indefinite and sometimes inconsistent in
MapScript. Additionally, any backwards compatibility considerations are
often accommodated in mapfile, but were not addressed consistently in
MapScript.

In my opinion, language-specific implementations were better off to use
their own templating facilities and use the msLoad*FromString capability.
This recognizes that mapfile is the definition of how MapServer renders
images, it has validation of the object relationships, and the project does
its best to protect mapfile compatibility as new versions are released.

Seth has done a ton of work on MapScript to fix all that and made MapScript
better than it ever was. All of his work means it will probably never die :)

Howard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20190915/1aa2a2cf/attachment.html>