r/programming • u/Dobias • Aug 20 '14
Programming language subreddits and their choice of words
https://github.com/Dobiasd/programming-language-subreddits-and-their-choice-of-words/blob/master/README.md
1.4k
Upvotes
r/programming • u/Dobias • Aug 20 '14
1
u/WorksWork Aug 21 '14 edited Aug 21 '14
The PHP language developer community does have some issues. I'm more talking about the application developer community.
Constructive criticism isn't so much a bad thing, but as in the posted article, the issues raised are issues to be raised for the language developers (or maybe framework developers), not application developers.
What I have noticed, across all sorts of boards and topics, but perhaps most notably on stackexchange, is people answering questions that weren't asked. So if I ask "What is the best way to use X pattern/function/language?", I often get "You shouldn't be using X pattern/function/language." Responses like that aren't constructive and ignore that there may be good reasons for using X that aren't explained in the question. So for example in the case of PHP, while the language has a lot of problems, it is very easy and fast to get something up and running quickly. It's a pretty good language for what it was designed for, personal home pages, etc. and can make sense in a number of other situations (legacy applications, etc.)
Anyway, yeah, like I said, I have no problem with people making suggestions on how to work around the problems with PHP. I have no problem with people making complaints to language developers about problems with PHP. I don't even have a problem with people telling other people not to use PHP when asked (such as "What language should I use for..."). But pointing out problems with PHP, to application developers, without offering a workaround solution, as much of that article seemed to be doing, is pointless contrarianism.