For example, automatic saving after certain quantity of the typed symbols.
This is the model that Microsoft Word uses and it certainly needs it since it does seem to come to a screaming halt on quite a regular basis (once a month).
I am not overly convince Zeus needs this sort of model since it does not crash on such a regular basis.
I suspect I have seen Zeus crashes about 5 times in 4 years and even then Zeus does not close and as such it is very difficult to actually lose file data.
I think, it is much better, than to save at regular intervals.
Why I really don't like these sorts of models is they are saying
this software has to do this because it is likely to crash.
I will make you a challenge.
If you can make Zeus crash and I can replicate the crash then I will give you a free Zeus license.
I think you will find it is very very very hard to crash Zeus.
Features like Refactoring and debugging are not possible in Zeus. I meant, whether the author of the program is engaged in it.
I refactor parts of the Zeus code on a regular basis.
But I'm an engineer by training so I also believe that
if it aint broke don't fix it
I asked, whether is primary target of developing is aspiration to the maximum convenience.
I think Zeus does aim for maximum convenience as it should.
I use Zeus for my c/c++, c# and SQL development and I find it more convenient than alternative IDEs.
What you can say about fitness not for writing your code, but for reading and understanding alien code?
Create a Zeus workspace, use Windows Explorer to drag and drop the source files onto that workspace and Zeus will ctags the entire project.
Once the ctags database is created there are lots of ways you can navigate that database inside Zeus.
Lots of tools uses ctags for this sort of code analysis but Zeus make the management of the ctags information a trivial exercise.
...especially the opinions of people which program in exotic languages.
Those opinions are the most important since I personally don't have experience of those languages.
But I think you will find changes for Zeus for these languages is quite common.
For example many of the
code folding changes heavily depend on the users coming up with the actual folding specification.
There are also lots of changes made to Zeus for languages like FORTRAN and COBOL that where driven heavily by users of those languages.
Without this sort of valuable user input none of these change would be possible.
Cheers Jussi