I would consider it tidier and more logical to have a fixed file extension for a class of file such as a Sesame macro file. With Q&A you were limited to an 8-character file name: a restriction removed in Sesame.

Quote:


You may not be aware of this, Bob, but those are fighting words around here. If you look at page 440 of the User Guide, you will see that staying out of the users way is a core element of the Sesame philosophy. 

There are a number of good technical reasons to assign a known extension to the macro files. Caliing someone a Bill Gates sock puppet who, like Alec, puts a tremendous amount of thought and energy into which of the myriad possibilities for implementation is best in any particular case, falls a bit short. As does the implication that we lack committment to maintaining user flexibility, when "leave the user's options open" is the rallying cry for this development team, and is maintained wherever the cost to the user does not outweigh the benefit.

We have assiduously avoided dlls, registry entries, and dependencies of any kind. Our lead programmer has worked with many other systems than Windows. Unlike many current developers, he is actually aware that there are other ways to do things.

We have written a product that runs on all versions of Windows since Win95 and Linux with almost no differences in the source code. It keeps us honest, and it keeps Sesame free of many of the traps software has to navigate around.

The development team is extremely committed to maintaining a product that tries to evolve in a direction that makes sense for our users, rather than simply doing what is "done". Sometimes we'll make mistakes in our choices, but it won't be because we blindly followed Redmond, and it won't be because we didn't take the time to thoroughly consider the options.