NY Times Says No To Useful App Rather Than Improving Memory

from the backwards-thinking dept

Thu, Jun 4th 2009 3:10pm — Mike Masnick

I have to admit that, while I became a fan of Twitter a while back, it jumped up to a new level when I started using a client-side app called Tweetdeck. While the app has many problems (it is still beta), it allows you to make use of Twitter in a very different way -- laying out a series of groups and searches in near real time, such that it turns the stream of information into a series of very useful flows. From the perspective of trying to stay up on certain types of news, it's become the most important app on my desktop. There are many, many things I wish they would improve upon, with a big one being memory management. It sucks up memory like crazy. However, my solution was to go out and buy some more memory for my laptop. Apparently, the NY Times has gone in the other direction. Mathew Ingram points to an internal memo at the NY Times where it says that due to Tweetdeck's memory issues, the paper is asking employees not to use it anymore -- though, to their credit, it doesn't appear to be a demand, but a request. On top of that, the NY Times suggests that other apps can do the job. That may be true, but I've tested a bunch of different competing apps (hoping they could get over Tweetdeck's other shortcomings) but I'm back on Tweetdeck because those other apps have even more problems, but Ingram again explains the better solution: "I agree that Tweetdeck can be a memory hog, and can sympathize with the NYT-- but the solution is buy more RAM, not exclude Tweetdeck."

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

Filed Under: apps, memory, tweetdeck
Companies: ny times, tweetdeck

39 Comments

If you liked this post, you may also be interested in...

Reader Comments

Subscribe: RSS

View by: Time | Thread

Anonymous Coward, 4 Jun 2009 @ 3:14pm

Standard crappy programmer comments.

It's not bad software, you need more CPU.

It's not a memory hog, you need more ram.

Write more efficient code, and neither is required.

This is the same complaint made often about Microsoft. What the heck is up Mike, this is like two or three times you toss up things that are just not very bright at all.
[ link to this | view in chronology ]
- Jason, 4 Jun 2009 @ 4:49pm
  
  Re:
  Yeah, and I read Ingram's tweet: more like a blind, unsupported assertion than an explanation.
  [ link to this | view in chronology ]
- Anonymous Coward, 5 Jun 2009 @ 12:01am
  
  Re:
  The software is still in Beta. One can't expect software to be perfect when it's still in Beta. It takes time to make code more efficient, don't be so harsh on the app. If it's a final release and then it has huge bugs I would understand. Beta, by its very nature, is unstable.
  
  I do agree, more ram is not the solution to software that's not (yet) written correctly. The most you can do is report the bug (but I'm sure they know about it already) and hope they fix it in the next release.
  [ link to this | view in chronology ]
  - Anonymous Coward, 7 Jun 2009 @ 10:45pm
    
    Re: Re:
    "The software is still in Beta."
    
    Then maybe the NY Times should be telling people not to be loading a bunch of buggy, pre-release beta crap on their work computers.
    [ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 3:16pm

Notepad is good, so is the "Stickies" widget. An anonymous Fox News Editor recommended a high priced pharmaceutical solution.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 3:42pm

Don't support poor quality software
If it leaks memory; it leaks memory.

I'm not going to buy ram because some jerkoff programmer can't develop properly.

Don't encourage crappy software.
[ link to this | view in chronology ]
- Anonymous Coward, 4 Jun 2009 @ 3:53pm
  
  Re: Don't support poor quality software
  Don't encourage crappy software.
  
  I just DL'ed the app. Is it true the app is just a Shockwave file? Of course it's going to leak. Gawd. Get rid of it! Shockwave wasn't made for that..!
  
  It's Free, but is it Open Source? If so, fork the source and let's start over!
  [ link to this | view in chronology ]
ChurchHatesTucker (profile), 4 Jun 2009 @ 3:46pm

Yeah, don't support poor memory management!
(Typed on Safari.)
[ link to this | view in chronology ]
Lawrence D'Oliveiro, 4 Jun 2009 @ 3:57pm

I Love The Smell Of Garbage-Collection In The Morning
Sounds like it’s written in Java.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 3:59pm

What's Adobe Air?
No it needs something called "Adobe Air"

I wonder what "Adobe Air" smells like.
[ link to this | view in chronology ]
Grey Ferret, 4 Jun 2009 @ 4:02pm

If you only have 1 computer, then buying more memory may seem like a good option. However, if you have an entire company or organization, upgrading the memory on every machine can get quite expensive, especially when you consider the amount of time the IT department will spend on installing the memory.

We have about 80 PCs where I work, and we're not really that big (I don't know how many NYT has). And right now, there's no budget for me to get overtime installing extra memory in 80 machines.

Sorry, but this article is very poorly thought out.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 4:04pm

Right.... spend thousands of dollars on ram and man hours to install it, all to compensate for the poor programming of a free, non-business critical application...

Usually I can't stand it when I see people type what I am about to, but it seems to be warranted...

Idiot
[ link to this | view in chronology ]
- Anonymous Coward, 5 Jun 2009 @ 12:10am
  
  Re:
  not to mention the computer down time required to upgrade the computers, that's probably even more expensive. If the ram is cheap to the corporation that just means the opportunity cost of the time to install it is very expensive.
  [ link to this | view in chronology ]
Crash (profile), 4 Jun 2009 @ 4:12pm

I can't disagree more
Usually I agree with you but being a programmer I have to agree with the other commenters the onus is on the developer to create a well designed app that doesn't have a memory leak.

A large IT department can't upgrade all clients just because an app is poorly designed. The cost in manpower alone going to each computer and installing memory would be ridiculous just so employees can have a third party social app.

When the developer fixes his app then they could use the app. It's lazy programming to say just upgrade your computer because I don't want to fix my program just yet.

Regards,
Crash
[ link to this | view in chronology ]
- Mike Masnick (profile), 4 Jun 2009 @ 4:49pm
  
  Re: I can't disagree more
  Usually I agree with you but being a programmer I have to agree with the other commenters the onus is on the developer to create a well designed app that doesn't have a memory leak.
  
  To be clear, I agree that the programmer should fix the app -- absolutely. In fact I've publicly complained that the memory leak on Tweetdeck is a huge pain.
  
  But that doesn't mean the NYT should ban it. For many reporters an app like Tweetdeck *is* an essential tool these days. Telling them they can't use it because of a memory leak is the wrong way to go about it.
  
  No, it's not great that the app is poorly programmed, but that doesn't make the app any less *useful*.
  [ link to this | view in chronology ]
  - Jason, 4 Jun 2009 @ 5:04pm
    
    Re: Re: I can't disagree more
    To be more clear, the NYT hasn't banned it. They just found it to be problematic, gave a proper warning about the problem with a recommendation against it for older hardware, AND most importantly they are (or at least they claim to be) taking action to find a suitable solution that doesn't cripple their employee's computers.
    
    And this is the part where Mike backpedals on his implied assertion "But that doesn't mean the NYT should ban it," and says, yes, and I already said as much in my post.
    
    We know, Mike, and even so, it's not just what you say. It's also how you say it. I'm still totally with you in general - just trying to help keep it real on this one.
    [ link to this | view in chronology ]
  - Anonymous ex-Times IT Guy, 4 Jun 2009 @ 5:18pm
    
    Re: Re: I can't disagree more
    First, they haven't banned it, simply recommended against it. They've warned their users that installing the app will cause problems, which is completely true.
    
    Second, a poorly programmed app is by defition less useful. I personally find apps more useful when they don't choke my machine into a near-unusable state.
    
    Just sayin.'
    [ link to this | view in chronology ]
  - Yakko Warner, 4 Jun 2009 @ 6:17pm
    
    Re: Re: I can't disagree more
    Actually, an app that makes your computer unusable (or just more difficult to use) would make the app very much less useful.
    
    And if it was found that this application was consuming enough extra resources that it was preventing any other work-related applications from running, resulting in lost productivity and an increased drain on IT tech support, then they most certainly should ban it.
    [ link to this | view in chronology ]
  - Ilfar, 10 Jun 2009 @ 3:52pm
    
    Re: Re: I can't disagree more
    I think telling someone not to use an app because it leaks memory is a damned good idea.
    [ link to this | view in chronology ]
Yakko Warner, 4 Jun 2009 @ 4:15pm

That's the better solution?
Spend thousands of dollars on hardware and employee downtime (unless you're just going to force your tech department to do this in off hours -- you can't use a computer while you're upgrading its RAM) to add memory to everyone's machines for the sake of one poorly-written app?
[ link to this | view in chronology ]
Sos, 4 Jun 2009 @ 4:22pm

Alternate solution
he NY Times should invest in the software developer to create a better version
[ link to this | view in chronology ]
Michael Kohne, 4 Jun 2009 @ 4:50pm

Who sent this?
I bet this came out of IT, who have no budget for upgrading systems, but get all the calls when the thing chews up memory and the systems get sluggish. Sorry, this isn't news - this is the IT department trying to deal with user needs on a limited budget and no understanding of why the users have to have this particular app.

I can't fault the IT guys for not wanting to spend god-awful amounts of money to deal with this silly app.
[ link to this | view in chronology ]
Jason (profile), 4 Jun 2009 @ 4:57pm

More like a heads-up than a heads up their...
"If you do install TweetDeck, know that it will slow your workstation."

Basically, they say it's okay to use - just don't expect them to upgrade your machine when it slows down, which it will.

I have to agree with others here. It sounds like Tweetdeck should be treated like a proof of concept and rewritten for better performance. I'm sure the NY Times has a hardware upgrade cycle like any other prudent IT shop. You don't just go upgrade crazy because of one badly written app. UNLESS of course you're ready to take out an ill-advised loan that can't be supported by your current business model - no wait, Mike you were against that, too.

Besides, open source development moves FAST. Give it a few weeks. Someone will have a better rendition sooner than you think.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 5:09pm

I wonder...
Because it's using re-interpreting yet another layer of code via runtime interprerter... I wonder if it will run any better on a more compact, efficient kernel such as Linux, Unix (read: Mac) than the usual Commodity-Based Operating System.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 5:10pm

I wonder...
Because it's re-interpreting yet another layer of code via runtime interprerter...

I wonder if it will run any better on a more compact, efficient kernel such as Linux, Unix (read: Mac) than the usual Commodity-Based Operating System.
[ link to this | view in chronology ]
Anonymous ex-Times IT Guy, 4 Jun 2009 @ 5:13pm

Pros and Cons
Pro: sounds like this app can help manage information, which sounds great for a tech-enabled news organization.

Con: it's beta software. It costs money to support unpredictable software that is by definition not ready for release. IT staff have to spend man-hours learning what the software is and does, how to work around its issues. Have you seen the NY Times stock price?

Con: it's *seriously flawed* beta software. With a known memory leak. It costs money to staff a help desk that reacts to help desk tickets that are *absolutely inevitable* with the use of this software. Have you seen the NY Times stock price?

Con: it's a memory hog. So let's say it comes out of beta but still requires 1GB or so to run. Are you seriously advocating spending 50K or so upgrading the entire newsroom to accommodate running this one app? What's the ROI on that one? And what about the next beta app the editors insists on? Do you just keep caving regardless of the cost?

Your personal decision to upgrade your memory has nothing at all to do with the realities of managing technology in a large company.
[ link to this | view in chronology ]
Chris, 4 Jun 2009 @ 5:44pm

Adobe Air
I've yet to be able to write anything more than Hello World app that didn't leak memory in Adobe Air. IMO right now, AA just doesn't do well for apps that need to stay open for any amount of time. But AA is stupid fast to develop in. If tweetdeck catches on enough, they should either change their choice of language or invest a few programming hours in fixing the relevant bugs in the framework. Either way, having worked in AA - its almost certainly memory leaks in the framework and not the app's fault.
[ link to this | view in chronology ]
- jrdixey (profile), 4 Jun 2009 @ 8:20pm
  
  Re: Adobe Air
  Chris has it right -- the memory leak fault lies in Air (specifically Flash running within the Air framework), not TweetDeck.
  [ link to this | view in chronology ]
  - Anonymous Coward, 7 Jun 2009 @ 10:40pm
    
    Re: Re: Adobe Air
    Chris has it right -- the memory leak fault lies in Air (specifically Flash running within the Air framework), not TweetDeck.
    
    In that case, the fault still lies with TweetDeck for using Air.
    [ link to this | view in chronology ]
jrdixey (profile), 4 Jun 2009 @ 7:37pm

TweetDeck
I stopped using TweetDeck for a while because it was chewing up RAM like crazy (800+mb at one point). Then I upgraded Adobe Air and it normalized down to about 150MB of RAM. It's worth it to me to run the app -- it makes Twitter useful for me, but then again I'm running on lots of RAM so it doesn't matter as much as it might to someone else. I could see it being a superb tool for journalists. The Times is being shortsighted.
[ link to this | view in chronology ]
tijir (profile), 4 Jun 2009 @ 7:59pm

Other clients do the same...
I found Peoplebrowsr http://peoplebrowsr.com/ does a better job of information management and uses the browser instead of a downloaded program, though it has a steep learning curve. I use Google Chrome for peoplebrowsr so I can keep a watch on the memory usage, which is about half what tweetdeck runs. My point, I guess, is that if you won't fix your program others will come along and try to make something even better.
[ link to this | view in chronology ]
Anonymous Coward, 4 Jun 2009 @ 8:45pm

Resources
This reminds me of a large company I used to work for. They limited us to a small amount of disk space to store our emails on the server (unless you were an executive or or other upper management). In fact, with the disk prices at the time it was about $0.25 worth of disk space. So people were constantly having to try and pick which emails were important enough to save and which ones weren't in order to say under the limit and avoid having their email frozen. Finally one day I got disgusted with the situation and walked down to the IT department and asked them to double my disk space and flipped them a quarter to pay for it. I don't know what they did with the quarter, but I never get any increase in disk space.
[ link to this | view in chronology ]
Anonymous Coward, 5 Jun 2009 @ 12:02am

"I agree that Tweetdeck can be a memory hog, and can sympathize with the NYT-- but the solution is buy more RAM, not exclude Tweetdeck."

So you expect the entire organization to invest in new ram for each computer using the software just because of a memory bug? That's an EXPENSIVE move.
[ link to this | view in chronology ]
- Anonymous Coward, 5 Jun 2009 @ 12:05am
  
  Re:
  It maybe easy for an individual to upgrade his/her ram but when a corporation has tons of computers, its' not necessarily that easy (and it's expensive). First of all, some of those computers might have the maximum possible ram already. Also, some of their computers maybe using legacy ram that's harder to find and hence would be more expensive. Not to mention different computers may need different ram which means they'll have to find matching ram for each computer.
  [ link to this | view in chronology ]
Jon, 5 Jun 2009 @ 2:28am

Minimem
Whilst it would be great if every bit of software worked as advertised, the reality is always going to be different. I've managed to 'cure' the memory leak in Tweetdeck (and even Firefox which is notoriously memory intensive) by using a small piece of software called Minimem. You can download it here http://minimem.kerkia.net/ and try for yourselves. It's free and seems to work fine.
[ link to this | view in chronology ]
Baylink, 5 Jun 2009 @ 8:15am

Minimem looks pretty cool
Shame it uses .net

Isn't that like using a military flamethrower to put out a kitchen frying pan fire by burning the house down around it so no one cares anymore?
[ link to this | view in chronology ]
JSF (profile), 5 Jun 2009 @ 8:26am

Hardware Costs
Having worked in IT for 13+ years now I would have to agree with what the NYT has done. They requested that people not use a piece of software that is causing them major headaches. People can still use it, but they are going to have to live with the problems it causes and IT won't support it.

As others have mentioned it is not a simple or cheap task to add RAM to hundreds or possibly even thousands of PC's. Depending on the specific hardware and it's age it may well not even be possible to upgrade the RAM. My main PC at home is less then 3 years old and can not take more the 2GB of RAM. So if I wanted to upgrade to 4GB I would have to get a whole new motherboard, CPU, and RAM. I wouldn't be surprised if the NYT is in a similar situation with thier PCs.
[ link to this | view in chronology ]
Rosedale (profile), 5 Jun 2009 @ 9:40am

Tweetdeck is awesome
Tweetdeck is my app of choice for twitter. Especially once they added FB integration. It helps out so much. I hadn't noticed how much memory it eats up, but that is because I already have 4GB. But that probably explains the slowness I have once I break out the VMs and such :-)
[ link to this | view in chronology ]
Anonymous Coward, 7 Jun 2009 @ 7:58pm

I don't think I've even completely disagreed with an article on Techdirt before. The idea to upgrade your computer/ram because of a small app that's poorly written is silly. Particularly when you are suggesting a corporate (100-1000 computer) upgrade for this free app. Hell it'd be cheaper for the NYT to hire programers and re-write the app correctly.
[ link to this | view in chronology ]