Archives
April 2005
4/26/05
Responses to AIM 6 Comments
4/25/05
4/11/05
Tuesday, April 26, 2005
10:11:00 PM EDT
A number of people wrote in with comments, I appreciate the feedback. I'll try to address some of them here briefly...
* Features - I can't stress enough that this is AN EARLY BETA (some of us would have called it alpha). Lots of things are missing. They'll appear in future betas.
* Memory footprint. Yes, it's big. Way too big for a final product. But it's not a final product, it's an early beta, we haven't done any tuning. The footprint will come down.
* Number of processes. We currently run different components as different processes to improve stability for this beta. This will change in future releases (and will help memory footprint as well).
* IE as renderer - we do very strict client-side filtering and run the incoming text through an XHTML converter to ensure a valid DOM, so I think we will be considerably more robust than AIM 5.9's creaky ATE control. In the event that we made a mistake, we have the ability to do server-side filtering as well.
* AIM for Linux... can't say too much now, but most of the Triton code is very portable, and may show up in another form in the future.
Written by juberti Blog about this entry |
Add to del.icio.us | 
digg this
10:11:00 PM EDT
Responses to AIM 6 Comments
* Features - I can't stress enough that this is AN EARLY BETA (some of us would have called it alpha). Lots of things are missing. They'll appear in future betas.
* Memory footprint. Yes, it's big. Way too big for a final product. But it's not a final product, it's an early beta, we haven't done any tuning. The footprint will come down.
* Number of processes. We currently run different components as different processes to improve stability for this beta. This will change in future releases (and will help memory footprint as well).
* IE as renderer - we do very strict client-side filtering and run the incoming text through an XHTML converter to ensure a valid DOM, so I think we will be considerably more robust than AIM 5.9's creaky ATE control. In the event that we made a mistake, we have the ability to do server-side filtering as well.
* AIM for Linux... can't say too much now, but most of the Triton code is very portable, and may show up in another form in the future.
Written by juberti Blog about this entry |
Add to del.icio.us | digg this
This entry has 10 comments: (Add your own)
-
I'd have to agree whole-heartedly with the first comment. I myself use addon programs simply because I feel AIM doesn't (or hasn't so far) had all the features I'd really appreciate seeing. The addon that I use allows for skinning, buddy aliasing (so instead of seeing the actual screenname, you can see any name you want to give them. Quite helpful for remembering who is who sometimes), Tabbed IMs (which the beta seems to have so far, so that's a definite plus), and of course Logging.
The buddy aliasing, while convenient for me, isn't a huge necessity. Neither is the skinning. The logging on the other hand I find I use all the time to keep track of important things going on, what things were said, and such. Adding in an optional real-time log feature would practically eliminate my need for addons. By "real-time" I just mean that the log for each IM is written as each line is sent and/or received.
Looking forward to seeing if these things will be added or if I'll continue to need to keep looking for addons instead. -
is there anyway that one of the new features for AIM 6 could be logging? Because I know a lot of people are always downloading plug-ins for AIM just so that they can have their conversations Logged.
-
I personally find it EXTREMELY annoying to wait for the GUI animations. It's irritating, really. Perhaps in a future beta, included should be something to turn it off or perhaps an older-style GUI option.
-
Am I missing something... Or have profiles been entirely removed from AOL 6? Me and my friends (and tons of other AIM users) LOVE the profile feature! What's up?
11/30/05 5:55 PM