Quote:
|
Originally Posted by GReaper
Have to agree with Allfather, there are plenty of existing CMS solutions as well as other frameworks which could get the job done shockingly fast. You could even use something as simple as Wordpress, yes it's a bit of a nightmare for security but it can do news and static pages quite quickly. Personally I'd go with Django these days, but I'm sure there are plenty of options.
One question, what exactly is being done to prevent the next version of the portal from being a failure?
The same mistakes seem to happen with every version of the portal, so I'd like to know just what steps are being taken to ensure that we don't end up with yet another dead portal in a few months time. I don't want to see another batch of false promises which won't be implemented.
It's sad to see the constant failure of the portals.  |
A bespoke package is significantly better than anything off the self. Yes they have had problems in the past with bespoke systems buts thats due to the coders being substandard (mainly in the the documentation area which is poor or none existant and makes it hard for other coders to come in later and enhance or fix the framework. I know back in round 6 when I was part of the coding team the documentation for most of the other coders sections were so poor they were useless) and from a management pov where they weren't strong enough to tell coders to piss off when they demanded to recode the whole system when it wasn't needed
BUT atleast a bespoke system isnt full of redundant code for PA and most importantly isnt riddled with exploits that are so easy to find out about and exploit that the world and their wife can hack the system and take control of your server with little effort.
With little effort you can find hundreds of exploits for things like wordpress or any CMS and a portal for a company that requests money from its users is a prime target to be hit. A bespoke website will probably still have exploits available but anyone wanting to take advantage of them has to find these exploits themselves, effort that most people wont bother with and when exploits are found they can be fixed internally rather than wait for the CMS systems programmers to be bothered to fix it