Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: paulycy; Jim Robinson; John Robinson
Throwing more money at the problem won’t solve it. [This latest glitch] was a technical issue and we just had to keep troubleshooting until we found it. And no, we’re not going to invite a bunch of strangers in to get their hands on our secure systems. John has been programming since he was 14 and he’s pushing 40 now. He built these systems and he’s an expert in them. And no, we are not going to throw out our software and rewrite it and no we’re not going to move on to some other database system. There are no guarantees that any other system can do a better job and not without hiring a staff to build and maintain it and that’s for sure. And we don’t have the financial wherewithal to do any of that anyway. Maybe if we had a couple million bucks at our disposal and a couple years to do it in we could build an iron-clad system. And maybe not.

Also, Jim, from a 25 year veteran in software development, myself: You have the right idea.

A rewrite is probably a formidable task, since this is an enterprise-level web app. My offhand guestimate is that it would take 2 senior developers, 1 fulltime tester, and one SOLID architect to pull off a full Free Republic implementation in 9 months to a year. Let us say, it is a year. Senior developers go about 100k, testers 60k, and an architect of the caliber you'd want is about 200k. That's 450k, and we haven't even talked about licensing development software and the equipment for them to develop on, much less the server farm itself. Figure 600k-750k to do a redevelopment.

John's system is, frankly, amazing for the price it's cost. it's obvious it's a labor of love. Plus, for him to have accomplished it in a bass-ackwards language like Perl, is truly mindboggling. (Poke poke, John.... lol.... told ya .NET was the way to go......lol.....)

Anyways, the plan you have adopted -- Keep up with the existing software, for it does work, and when needed, troubleshoot -- is viable. Objectively speaking, it is a decent plan.

There may come a time when the Perl system you have simply won't cut it any more. When that happens, I suggest a conversion to a robust enterprise solution. I favor C#.NET with SQL back end. It's battle-tested and well-regarded for enterprise apps. John would be a pro in it in about a month.

62 posted on 01/11/2011 6:10:14 AM PST by Lazamataz (If Illegal Aliens are Undocumented Workers, than Thieves are Undocumented Shoppers.)
[ Post Reply | Private Reply | To 1 | View Replies ]


To: FReepers
We The People

Support Free Republic

66 posted on 01/11/2011 6:14:10 AM PST by DJ MacWoW (America! The wolves are at your door! How will you answer the knock?)
[ Post Reply | Private Reply | To 62 | View Replies ]

To: Lazamataz

Oh my, I did not even consider this site was still using PERL for such a high volume website.

One plan for a future change is to keep the old posts in the depreciated PERL version as an archive and just start fresh with a new system/database with username/password imported from the old database.

Converting a CGI forum when millions of posts would not be a fun thing to do. Personally, I would just leave the old system in place and move on a new system for new posts. Just my 2 cents.


75 posted on 01/11/2011 6:20:45 AM PST by WaterBoard
[ Post Reply | Private Reply | To 62 | View Replies ]

To: Lazamataz

Thanks.

It helps to have those figures.


505 posted on 01/11/2011 9:08:47 AM PST by Quix (Times are a changin' INSURE you have believed in your heart & confessed Jesus as Lord Come NtheFlesh)
[ Post Reply | Private Reply | To 62 | View Replies ]

To: Lazamataz

>> “There may come a time when the Perl system you have simply won’t cut it any more.” <<

.
Will you and I still be alive?
.


564 posted on 01/11/2011 9:27:19 AM PST by editor-surveyor (Obamacare is America's kristallnacht !!)
[ Post Reply | Private Reply | To 62 | View Replies ]

To: Lazamataz; paulycy; Jim Robinson; John Robinson
John's system is, frankly, amazing for the price it's cost. it's obvious it's a labor of love. Plus, for him to have accomplished it in a bass-ackwards language like Perl, is truly mindboggling. (Poke poke, John.... lol.... told ya .NET was the way to go......lol.....)
Agreed. I'm not a fan of Perl but this is testament to what tenacity and a good mind can do with it.

A rewrite is probably a formidable task, since this is an enterprise-level web app. My offhand guestimate is that it would take 2 senior developers, 1 fulltime tester, and one SOLID architect to pull off a full Free Republic implementation in 9 months to a year. Let us say, it is a year. Senior developers go about 100k, testers 60k, and an architect of the caliber you'd want is about 200k. That's 450k, and we haven't even talked about licensing development software and the equipment for them to develop on, much less the server farm itself. Figure 600k-750k to do a redevelopment.

This is true; but while Jim's stance seems somewhat anti-opensource of FR's internals I'm not sure if he is also unwilling to accept the 'donation' of developers re-implementing FR for him. I bet there's at least several capable programmer-types in the membership.

As I am currently unemployed [just graduated] I could probably donate some time to just such an effort. Even without pay, there is the possibility that I could put it on my resume as an experience point.

There may come a time when the Perl system you have simply won't cut it any more. When that happens, I suggest a conversion to a robust enterprise solution. I favor C#.NET with SQL back end. It's battle-tested and well-regarded for enterprise apps. John would be a pro in it in about a month.

As long as the system is being rewritten in another language, and the .NET paradigm of "language-independence" [CLR] is somewhat valid, then the choice of language should be given careful consideration. I would suggest that in this situation (where the common runtime makes data-types usable from anywhere) the best language would be one which facilitates:

  1. Compile-time error-checking
  2. Verbosity
  3. Modularity and perhaps
  4. language-level concurrency
(Items #2 and #3 together should greatly help maintainability, while #1 should prevent at least some troubleshooting.)
I would suggest Ada as it offers all of these features; and from my understanding the .NET-targeting Ada compiler from AdaCore can be used freely in non-commercial projects.
712 posted on 01/11/2011 10:37:46 AM PST by OneWingedShark (Q: Why am I here? A: To do Justly, to love mercy, and to walk humbly with my God.)
[ Post Reply | Private Reply | To 62 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson