leech wrote: OL wrote:
leech wrote:Thanks! That's what I'm talking about.
That brings up something, so from what I had read a while back, MyAES is open source just like XaAES, right? But it seemed to me most people thought MyAES wasn't quite feature complete yet, whereas XaAES was. Is that correct? I know most MiNT distributions come with Xa vs My.
MyAES is not open source, it is only free, I don't think any distribution come with MyAES
What feature is not implemented? At my known PDLG is not implemented and extended AES object (I have no documentation on this and I don't know any software using it), but except this I not see, for very old application more design for single task the compatibility is lower than XaAES. For new feature MyAES is I think is more advanced than any AES. The next version (0.97) is really nice, there is some beta already running. The new version is not yet available because I work now on new desktop and I found a crazy bug in MyAES, but should be fixed soon.
Thanks for the info! It may have been a long while since I was researching which one to go with that said MyAES wasn't feature complete, and with all things Atari, I may have read it 2 years ago and it was a post that was 4 years old...
On the thought of Open Source vs Free. It's awesome to give it away for free, though with Atari software, not much is still commercial, but wondering why not just open source it? The biggest advantage is if someone gets bored of working on a project, then they can do a code dump and let others take over.
There was this great remake of Racing Destruction Set that someone was working on, then decided to stop work, and instead of open sourcing it, that work is now just dead.
Anyhow, I'm sure you have your reasons, I need to give MyAES a try, probably will in the next few days when I get me some time.
Perhaps there is some feature not implemented but I don't know wich one! Perhaps they want speak about very specific function from Magic and NAES, some are undocumented and other I not see the need to implement it or simple I don't like
or partially implemented (this is the case of Magic file selector).
Why not open source, for 4 reasons :
- AES is quite complex piece of software, it is very easy to broke system, not easy to test it (it's not classical software with its bugs, if you try fix something for one software perhaps it can not work for another!), when XaAES source code was put in open source I have tryed to modify it, but it was a nightmare to correct it and understand, so I have prefered start a new project from scratch and I work with several people that help me, I'm not as brilliant as Odd Skancke that do an incredible job on XaAES. So I not want correct bugs of other it's already annoying to fix my own!
- I know someone that will be happy to compil it and provide it on his website shouting he is the author of this code
- I know where I want to go, it's a long way never finished! And I want to be sure to do what I want on it!
- I know how I program, it's not easy to understand piece of software you have not write yourself, so for me it is more easy like this
When I will stop MyAES development, I will put it in open source for sure, but at this time I not see the need, there is already an open source AES, broke team in 2 is not good idea there is already too few people working on it.
If you test MyAES try beta version (only the kernel you should take other components for myaes website) : http://myaes.lutece.net/telechargement/myaes097beta.zip
(june 14 2017)