ID:138508
 
Tom mentioned elsewhere the number of unused features...

I think the upcoming book will help a lot here. Sometimes you Byond guys have added 2 or 3 critical and subtle features in a single release, and I already have a bunch of code doing it the old way and am doing something else at the moment and...

Well a month later I realize there is probably some new better way to do this but my code is still already filled with the old way so...

Anyway, I'm sure that reading through the book will remind me of some of these improvements and get me to switch over.

I can certainly say that switching to \ref for the Forum library made a huge difference. It simplified the code and made it more object-oriented. In retrospect I realize I could have taken that approach even without \ref in place, but I didn't think of it.
On 7/10/00 9:27 am Deadron wrote:

I can certainly say that switching to \ref for the Forum library made a huge difference. It simplified the code and made it more object-oriented. In retrospect I realize I could have taken that approach even without \ref in place, but I didn't think of it.

It's funny that you mention this one, because I dealt with the very same problem with the SubmitLink library. I used some hacks to get around the old notation, so if I were to rewrite it now it would be much cleaner. But, alas, I have no plans to rework it anytime soon. Quite irritating!

Even when new features work perfectly the first time out, they can be problematic for just this reason. However, previous coders need not feel an obligation to use everything just because it is out there (I know I don't).

The biggest pains are those which break the compatibility with existing code. We are going to go to great lengths to avoid this from now. So new features, when added, should merely augment the system. But don't feel pressure to conform!

That said, I'm glad the new stuff made your code more pleasing. Even though I was initially upset at Dan's blatent violation, I'm secretly pleased too :)