-
@gus if those 361 million people were all programmers, bug count would be astronomical; the success of WP is, in fact, that you just need to be able to read and write in order to use it; don't rely on the people using it to assume the code is optimal; after all, how many PCs are powered by Windows?
NOTE: This comment was originally posted at StackOverflow.com by Damien Pirsy
-
@gus: The numbers given are the open ticket count over time. Tickets are mentored by wordpress developers. It's not the actual bug/feature count. So it can only show the number of open issues, which has a different meaning per each project. And take a look at the dates given in the graph, these numbers are older - it has more than doubled since then but I have no graph at hand.
NOTE: This comment was originally posted at StackOverflow.com by hakre
-
Saying that the success of WP is based on the fact that you just need to be able to read and write in order to use it is total nonsense. All kinds of people use WP, programmers, companies, corporate, end users and so on en.wordpress.com/notable-users . 2.5 billion page views per month is fairly compelling evidence that it works regardless if its perfect or not.Good coding methodology helps but is no guarantee of the success of a project and one method vs another if you arrive at the result is at best purely academic.
NOTE: This comment was originally posted at StackOverflow.com by gus
-
@hakre the point i make is its all relative. With that many users across the world its a very small percentage. The other point I make is that its far too general to plonk metrics on a page without qualification of the metric and how it relates to this particular topic in particular the functions in question.
NOTE: This comment was originally posted at StackOverflow.com by gus
-
@gus: What I highlight is that each project has its objectives which influences code. The graph can only be a visualization which foremost shows that keeping the number of open tickets low is not an objective. Management by objectives. More important than relativisation is that you define your own goals. Only because Wordpress can live with that code, it does not mean that you could survive with it. Much cheaper is to have sysreqs that are useful and train users instead force development into a direction that hurts for years.
NOTE: This comment was originally posted at StackOverflow.com by hakre
-
@hakre I agree, of course its better to build on solid foundations. But things change over time like the PHP versions, OS, expectations and functionality and people don't have crystal balls. What we "think" is good practice today may also be considered total rubbish in 5 years time and full of legacy code.
NOTE: This comment was originally posted at StackOverflow.com by gus
-
@hakre as i said before you didn't mention that the graph is not official nor is it verified and may not be accurate. You have also made an assumption that keeping the number of open tickets low is not an objective. According to who exactly? Have you verified that with WP?
NOTE: This comment was originally posted at StackOverflow.com by gus
-
what i find really funny is your profile points to hakre.wordpress.com LOL
NOTE: This comment was originally posted at StackOverflow.com by gus
NOTE: This comment was originally posted at StackOverflow.com by gus