I know this is not code level, technical, observation but a real world comparison. I use 4, 22in LCDs in my real estate office window to advertise houses. The web page they display is javascript light, one to change the logo every 30 seconds. Each page has FLIKR applet to show a slide show of the property. The 4 firefox browsers will grind the system to a halt within 3 days (P4 630mb of RAM). The same 4 pages shown continously in IE7 will last 8-10 days. Either way it is crap b/c they should not leak at all, they are web browsers with thousands of peole wokring on them. Increased quality review and assurance of core functionality would probably help here. Thankfully memory is so cheap I am bumping up to 3gb. Not to go quicker but to last longer between re-boots...
I am currently using an unplugged T-40 with the larger of the two batteries. I unplugged at lunch around 1:30 and have 5 % battery at 7:10pm. I dont watch DVDs or burn CDs so I dont know how that affects battery life. @5 punds even w/the heavy of the two batteries I have yet to see any laptop last longer. The battery and laptop are also about a year old.
One architect, one engineer and the base jabber client. My colleague (we both work at top 5 Broker/Dealer) put a fully compliant version into production with capability of proxies for all major IM clients in less than four months. The largest issue seems to be the childish tug of war between the proprietary clients. I like the logging b/c one can create chat rooms on the fly through impact analysis tools to couple tech operations and application teams during Incident collaboration and mitigation, allowing managers to review at a later time how the people worked (or did not) work together. I agree with the Disk space guy, another SEC directed boon for their industry!
Slashdot Mirror
Decent idea if it were not a store front marketing tool... It attracts passers by really well.
I know this is not code level, technical, observation but a real world comparison. I use 4, 22in LCDs in my real estate office window to advertise houses. The web page they display is javascript light, one to change the logo every 30 seconds. Each page has FLIKR applet to show a slide show of the property. The 4 firefox browsers will grind the system to a halt within 3 days (P4 630mb of RAM). The same 4 pages shown continously in IE7 will last 8-10 days. Either way it is crap b/c they should not leak at all, they are web browsers with thousands of peole wokring on them. Increased quality review and assurance of core functionality would probably help here. Thankfully memory is so cheap I am bumping up to 3gb. Not to go quicker but to last longer between re-boots...
I am currently using an unplugged T-40 with the larger of the two batteries. I unplugged at lunch around 1:30 and have 5 % battery at 7:10pm. I dont watch DVDs or burn CDs so I dont know how that affects battery life. @5 punds even w/the heavy of the two batteries I have yet to see any laptop last longer. The battery and laptop are also about a year old.
One architect, one engineer and the base jabber client. My colleague (we both work at top 5 Broker/Dealer) put a fully compliant version into production with capability of proxies for all major IM clients in less than four months. The largest issue seems to be the childish tug of war between the proprietary clients. I like the logging b/c one can create chat rooms on the fly through impact analysis tools to couple tech operations and application teams during Incident collaboration and mitigation, allowing managers to review at a later time how the people worked (or did not) work together. I agree with the Disk space guy, another SEC directed boon for their industry!