|
|
Subscribe / Log in / New account

Rumors of new Gnash functionality exaggerated (Linux.com)

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jun 22, 2007 17:51 UTC (Fri) by jwb (guest, #15467)
Parent article: Rumors of new Gnash functionality exaggerated (Linux.com)

The incredible thing is that it works at all. If experience with Free Software is any guide, when an application reaches this level of functionality -- that is, barely working for a substantial fraction of users -- it rapidly improves as testing and patching accelerate. I predict gnash will be in good shape by the end of this year.


to post comments

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jun 23, 2007 18:58 UTC (Sat) by AJWM (guest, #15888) [Link] (1 responses)

Good observation, and I'd agree.

Until a new app or library becomes at least barely usable, only a very few die-hards with the vision are willing to put effort into it. Once it reaches the point where the more casual user (for that particular app, but still an experienced programmer) is willing to give it a try, the "many eyes makes bugs shallow" effect starts to take over, and that accelerates as the app becomes usable to more and more people.

At that point the progress rate also depends on the complexity of the app and how well the code is structured and documented to make it easily understandable/modifiable by programmers new to the project.

(And sometimes that's the difference between an ugly hack that does something an end user/programmer wants done but he's not willing to pass back upstream, and a clean one that he is. Case in point, mplayer, which I wanted to display the file name playing as the title of the window it's playing in. Couldn't quickly (ie, within a half-hour or so) figure out the "right" way to do it, so I did an ugly hack with a global variable. Works for my needs but may well not work in other situations.)

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jul 24, 2007 19:42 UTC (Tue) by kreutzm (guest, #4700) [Link]

Could you post your mplayer hack? I miss this functionality as well. Thanks.

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jun 23, 2007 22:54 UTC (Sat) by endecotp (guest, #36428) [Link]

> If experience with Free Software is any guide, when an application reaches
> this level of functionality -- that is, barely working for a substantial
> fraction of users -- it rapidly improves as testing and patching
> accelerate.

Or, when an application reaches a level of functionality that meets its author's essential needs, development stops. Or maybe that's just my projects :-(

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jun 24, 2007 1:41 UTC (Sun) by dwmw2 (subscriber, #2063) [Link] (2 responses)

Unfortunately it needs to stop eating CPU and memory before people can really start testing it and leaving it enabled. I tried it, and was shocked to see it vying with Evolution to see which could claim the largest virtual memory size -- Evolution won, with over half a gigabyte, but gnash wasn't far behind. I removed it again.

When it no longer hurts I'll keep it installed.

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jun 30, 2007 11:46 UTC (Sat) by oak (guest, #2786) [Link] (1 responses)

> Unfortunately it needs to stop eating CPU and memory before people can
really start testing it and leaving it enabled.

With what SWF file/video it did this? Did you Valgrind/Massif where the
memory went? Did you file a bug about this?

Rumors of new Gnash functionality exaggerated (Linux.com)

Posted Jul 1, 2007 9:54 UTC (Sun) by njs (subscriber, #40338) [Link]

I see the same thing -- mostly it manifests as "I notice my computer seems weirdly slow, and then discover it's because I have a bunch of gnash processes chewing up resources". So all I know is that it was spawned by some web page that I visited recently, that had a plugin buried in it somewhere, and no guarantee that the web page is still around, or that I ever scrolled down far enough into it that the plugin was even visible on my screen, even assuming I would notice the little black box it made...

It's not really clear where one would start debugging. I guess putting the URL into argv[1] so it was visible in ps might help.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds