tag:blogger.com,1999:blog-7895832.post115327221594679348..comments2023-11-28T01:53:02.945+07:00Comments on My Personal Blog: Backward CompatibilityWilly Sudiarto Raharjohttp://www.blogger.com/profile/12738382924950315620noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7895832.post-1153289133569163862006-07-19T13:05:00.000+07:002006-07-19T13:05:00.000+07:00Thanks, Nice comments :Dwell, yes, but sometimes i...Thanks, Nice comments :D<BR/><BR/>well, yes, but sometimes it takes some time to get it better, since sometimes, new packages broke the backward compatibility with the old one. It will be safer if we have some kind of testing system where we can simulate the upgrade process first rather than directly upgrade the main serverWilly Sudiarto Raharjohttps://www.blogger.com/profile/12738382924950315620noreply@blogger.comtag:blogger.com,1999:blog-7895832.post-1153286529590294712006-07-19T12:22:00.000+07:002006-07-19T12:22:00.000+07:00For the convenient of a humble end-user, backward ...For the convenient of a humble end-user, backward compatibility is a must. The ODF-old format converter is essential.<BR/><BR/>For sysadmin, backward compatibilty is depend on system architecture in overall. The essence of "system upgrade" is to bring more best practices. So why we still use old way since there are the better way? <BR/>At least, that's what sysadmin paid for : dealing with the headache of system migration. Hehe. <BR/><BR/>For developers, backward compatibilty often mark as "depreciated" component. In free way, means : "don't use it because we're no longer maintain the old library". <BR/><BR/>One thing to keep in mind that backward compatibiliy is only for short-term. Sooner or later, we have to deal with the headache.<BR/><BR/>In our case, we can take shortcut like this. <BR/>Mark all old format API as depreciated, better yet eliminate them. But at the same time, maintain a converter for our humble end-users using the new API.Anonymousnoreply@blogger.com