Haken speaks
POSTED BY: SigmaNunki
UPDATED: Sunday, July 27, 2008 23:01
VIEWED: 6539
PAGE 4 of 4
FFF.net is at the top of my favs list.
A well deserved "Thanks Haken" for your time and effort.
Z
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Quote:
Originally posted by zzetta13:
A well deserved "Thanks Haken" for your time
Z
time? y'mean - Tuesday, October 03, 2006 10:41
(cue twilight zone music)
NOTIFY: N | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Quote:
Originally posted by Steamer:
However, I'd like to ask you respectfully to consider that the site still gets a great deal of traffic every day. Even though the series has been over for quite a while, the fandom by no means died with it. I've seen an influx of introductory threads and blog entries just in the past few months - new fans are still joining the ranks and signing up on a site that seems to have established itself as THE Firefly fansite, a fine and fun community for fans and friends. Sometimes it's mind-boggling what you do to keep it going for everyone as it is, but IMHO, the amount of activity around here, and the effect it has on the site, is hard to overlook. Because I don't think many users are much of the mind to take flight and find a new place to commune.
While it may seem like there are new members joining the site and an increase in activity, the overall traffic to the site has actually dropped over the past year. As such, my main focus right now is to get Shiny Universe to some usable point before the Fall TV season starts.
If and when SU becomes stable and if traffic to FFF.NET remains steady, I might consider rebuilding FFF.NET. We'll just have to wait and see.
NOTIFY: N | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
Quote:
Originally posted by Haken:
As I have stated, this site was written in MS ASP. No one builds websites in classic ASP anymore. There are way better ways to build a fansite these days. A framework like Ruby on Rails is way more elegant.
I never said that the site should be rewritten in ASP.
I must say that although I agree that RoR/etc would be more elegant, my personal opinion on RoR and similar stuff is that although it is great for rapid prototyping, it isn't necessarily the best for a production site. As in, you never know what's really going on in those internals unless you go through them. Sure, there is a certain level of trust with any framework, library, etc. But, RoR/etc, IMO, takes it too far.
Quote:
Originally posted by Haken:
Also FFF.NET isn't an OSS project.
Never said it was. I was doing a comparison.
Quote:
Originally posted by Haken:
Anyway, my feelings are I see no point in continuing development of FFF.NET in a dead language and I see no point in rebuilding FFF.NET in a new framework for a long canceled series.
You have a point, but think about it from another angle.
Though the series is finished, though it has been for some time, people, many people, still use this site daily. They have and continue to invest a significant amount of time in this site. So, its continued existence and stability isn't insignificant. Far from in fact.
What I'm not saying is that you have to do it. What I am saying is that it isn't necessarily wise to not allow anyone else to do it just because you don't want to.
I have a loose, "use this or that tech" type doc with some other ideas lying around my hdd if you're interested. Let me know if you are, otherwise I'll consider this speaking my piece.
----
I am on The Original List (twice). We are The Forsaken and we aim to burn!
"We don't fear the reaper"
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME
@JewelStaiteFan:
You haven't disagreed with anything that I've said. You've disagreed with a straw man.
You don't seem to understand how such a team would work (have you ever worked in such a team?). Let me explain.
Given several developers working together there would be goals for any given milestone all working together using a SCM (e.g. CVS, Subversion, Mercurial, etc) to share there code. The code would be developed on the developers own computer so there wouldn't be any downtime on the production site due to any incompetence on the part of a developer during development. Also, not everyone would be given write access to the code repository. Assumedly, one would have be given read-only access (if there isn't already public anonymous read-only access) and then they would be given small tasks to complete, participating in debugging and other small tasks. Once trust is built and competence is proven, then they may get write access and officially become part of the development team.
The typical life-cycle goes:
1) implement milestone goals
2) once "complete" put on a feature/code freeze with some developers going to (1) for the next milestone, with the rest continuing onto (3) (branches are lovely)
3) debug, debug, debug...
4) release to a beta site and ask for users to hammer it. Upon flaws return to (3) else (5)
5) release to production site and goto (1)
The first release would of course include many iterations of the above.
Also, I said nothing about an "admin by committee". I also said nothing about constant "upgrades" or any such thing. What I'm talking about is fixing problems that exist (i.e. maintenance), and POSSIBLY give people a few features that they've been screaming for for years (e.g. paging). And doing this collaboratively. Ideally, there should also be more than one person with admin privileges on the production server (ssh is a beautiful thing). That way things can be fixed faster. But, that's it and these are all typical things to have in place. Don't put words in my mouth. Because, if collaboration didn't work, you wouldn't be typing on your computer (OS's, etc, etc, etc, are good examples of such).
The only thing I'm saying is that standard maintenance isn't going to cut it (from Haken's responses he seems to agree with this), that a rewrite is necessary to get things going optimally and that it should be done.
----
I am on The Original List (twice). We are The Forsaken and we aim to burn!
"We don't fear the reaper"
NOTIFY: Y | REPLY | REPLY WITH QUOTE | PERMALINK | TOP | HOME