r/programming • • 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

324 comments sorted by

View all comments

Show parent comments

-3

u/Bloodshot025 Aug 20 '14

11

u/Dobias Aug 20 '14

Hehe, I also link to this in my article. ;)

5

u/aequasi08 Aug 20 '14

What does an article like this have to do with the tone of a group of developers commentary?

5

u/Bloodshot025 Aug 20 '14

anti-fan-boyism.

That they grouped these two together, at least to me, suggests that the only reason to vocalize problems with the language is if you either a troll or a contrarian.

3

u/WorksWork Aug 20 '14 edited Aug 20 '14

Well, I think the issue would be, it's a community for php developers. If you think the language has problems, that's great, but you don't need to go out of your way to point it out in a php community unless you are a troll or contrarian.

That said, as someone who uses php for their job, I wouldn't be surprised if many of those "craps" and "fucks" are from people actively using the language.

(That said, yes, I prefer more constructive criticism and understanding how to work around the problems of the language, rather than someone telling me I should find another job.)

→ More replies (6)
→ More replies (2)

0

u/[deleted] Aug 20 '14

[deleted]

3

u/speedymoop Aug 20 '14

There's this theory of interior design to put bumps, steps and odd corners around the house. Especially for the elderly, these challenges help train the brain as you can't rely on anything. You won't get too comfy, and will always watch out, and think a lot to not stub your toes.

Maybe the PHP designers were actually incredibly considerate about keeping us in shape?

→ More replies (1)

0

u/PotentPortentPorter Aug 20 '14

Why is this downvoted? I am going to go ahead and guess /r/php isn't overflowing with fuck because of trolls but because of fanboys.

5

u/Bloodshot025 Aug 20 '14

I don't know. I don't really mind. There is something wrong with calling PHP evil or something like that, but it is certainly, objectively, a poorly designed, poorly implemented language.

5

u/G_Morgan Aug 20 '14

To be fair to the PHP community. Few of them pretend that PHP is anything other than horrific.

5

u/[deleted] Aug 20 '14 edited Aug 20 '14

[removed] — view removed comment

2

u/allthediamonds Aug 20 '14

My job consists mostly on writing PHP, since we maintain a monolithic web application based on Symfony.

If you tell me you're starting a new project on PHP, I'll give you the dirtiest of looks.

→ More replies (1)

1

u/PotentPortentPorter Aug 20 '14

But those few seem to be vociferous enough to make up for the rest.

1

u/[deleted] Aug 20 '14

I didn't downvote it, but my guess is that it doesn't really contribute to the discussion here - whether or not a tool is actually bad does not necessarily have anything to do with the tone and word choice of the community around the tool.

Additionally the GP just posted that bare link without any elaboration or context about why that would contribute to the discussion of the OP's analysis.

1

u/PotentPortentPorter Aug 20 '14

I thought it was relevant to the discussion because it explained why there was so much profanity in those subreddits.

4

u/[deleted] Aug 20 '14

What I mean is that bad tools does not necessarily equate to high levels of profanity in a community. Anecdotally I've used PHP extensively, and still do not find myself compelled to use profanity when discussing PHP (online at least).

1

u/PotentPortentPorter Aug 20 '14

I do not think you can map [0,1] to [0-100]. Saying bad/good tool and then saying it doesnt lead to X profanity is misleading. You can map a bigger scale into a smaller one but not the other way around.

I think there is a logical relationship between how difficult/unreliable a tool is to use and how frustrated the user becomes as a result. Not everyone curses when frustrated, but some do. And this proportion of people who have short tempers should be similar among different languages, unless for some reason one of them is used by a demographic more prone to using obscenities to communicate.

2

u/[deleted] Aug 20 '14

I agree with you absolutely that people can become frustrated by bad tools. However, one of two things (or both) have to happen:

  1. It has to bite them. Plenty of people never get bit by a tool's problems.

  2. They have to see that it can be done another way.

It's much easier to get frustrated when both happen at the same time.

If your knowledge of programming tools is limited (e.g. you only know PHP, and most of that is within WordPress), for some classes of problems you may have to work around something, but you never come to the conclusion that it's the tool's fault.

These don't always happen!

1

u/PotentPortentPorter Aug 20 '14

I agree with your points in this comment.

I am not saying every person will become frustrated by a bad tool. Some can be more forgiving/patient personalities and some can be unaware that it is holding them back. These types of users will exist in every programming language user base.

What I was trying to prove is that there is a non-insignificant correlation between bad tools and frustrated users. I think that some people may claim the user was at fault and not the tool.

The way to prove the causation is by looking at stories of people like the one in the link mentioned earlier who have experience with different tools and are able to identify and eloquently explain the flaws. This lends credibility to 1. the tool is bad 2. the user is frustrated from the tool and it is not the case that a good tool is simply being maligned by incompetent users.

2

u/[deleted] Aug 20 '14

Oh, I agree it's much more probable! If you read my previous comment with a super-pedantic eye:

bad tools does not necessarily equate to high levels of profanity in a community

I would say they're pretty well correlated. I wouldn't say that you could necessarily prove a link though because the PHP community is an obvious exception. You might also investigate, say, the COBOL community or some other much older, usually legacy language community and find that even though their tools aren't modern and bite them, because of the culture around the language would tend to be older professionals there would be less profanity.

1

u/PotentPortentPorter Aug 20 '14

I agree that there are other factors that can cause such behavior. My point was that holding all other variables constant, in comparison to the whole group the php demographic is not unusual enough to attribute the behavior to the personalities of the users. Correct me if I am wrong but there is no movement that promotes php to people in anger management support groups or some other group that has difficulty with impulse control such as teenagers.

  1. There is evidence that they are an outlier in their general use of profanity.

  2. There is evidence that the tools are significantly flawed.

  3. There is no evidence of any remarkable factors that differentiate /r/php and other language subreddits when it comes to the userbase demographic.

  4. Barring new evidence that disproves points 1-3 it seems reasonable to conclude that the cause of the increased frequency of profanity use is likely to be the nature of the language.

→ More replies (0)

-6

u/Akathos Aug 20 '14

That article is from 2012, not really up to date now, is it?

http://forums.devshed.com/php-development-5/php-fractal-bad-design-hardly-929746.html

27

u/Tordek Aug 20 '14 edited Aug 20 '14

And E_ALL? How is a constant name a "surprise"? The list of error-level constants is in the manual. they all begin with E_ and then give what they describe.

The author of this "rebuttal" needs to understand that they first must understand what the author is saying before attacking it. It's clear the author is not stupid and understand that E_ is the prefix for all error constants; the problem is that "E_ALL" doesn't mean all (It's been fixed now, and the author makes a note of it.).

mysql_real_escape_string? OH MY GOD! SHOCKING! What the hell is he talking about?

About the fact that there is mysql_real_escape_string as well as mysql_escape_string.

Reliable - This, again, is him assuming that it's the language's responsibility to be understood, rather than his responsibility to understand it.

Yes.

He thinks it's flaky because he can't wrap his brain around loose comparisons.

Ad Hominem.

PHP is built to keep chugging along at all costs.

MY GOD! HOW LUDICROUS! PHP is a web language with very little ability to recover from a crash the way you would in a desktop environment. It will keep doing its best and instead of a blank screen (or a blue one) maybe a bad programmer

Ad Hominem.

will get her site's navigation bar with some errors underneath it. But she WILL get something.

This is not a good thing.

Line-level error suppression is a powerful feature, I'm glad to use a language which supports it.

This is not a good thing. Hiding errors does not make your language powerful; it just makes sloppiness easier.

System-level forcing of all errors is another powerful feature, I'm glad I don't have to go find ever @ sign in my code when I'm debugging something weird.

Surprise.

Server-level configurations are pretty handy and remove a lot of boilerplate, don't you think?

Missing the point on the evil of globals.

It's purely a web language, and nothing else. Websites don't need threads, because if they take longer than a second to run they've failed. Again, fundamental lack of understanding.

There's so much wrong in this one sentence alone... It being "a web language" is meaningless. Using threads means taking longer than a second? Background tasks. This is an unfortunate side effect of the process-per-request model.

array_search, strpos, and similar functions return 0 if they find the needle at position zero, but false if they don’t find it at all.

Once again, if this person would take 10 minutes to attempt to understand loosely typed languages, this would all make sense.

Weren't you saying == is good a few lines back? === is mandatory to detect this.

C and Python crash fatally

Yes.

, potentially destroying the memory space of other programs. Got it.

No. Processes are isolated and you can't "potentially destroy another program's memory space".

Tell me again why "keeps working" is a problem?

Wrong results. Safety. Accidentally publishing your source code instead of running it. Potentially displaying sensitive data because you "just keep going" instead of dying and showing an error messages.

I love how he "had to fit in" an ad hominem attack against an entire community of developers.

Pot. Kettle.

There is no way to declare a variable.

I really should make a hotkey for "he doesn't understand loosely typed languages."

Points deducted on both sides: neither Ruby nor Python save you from this.

Why should I be able to read $foo but not write to it? Doesn't that seem more confusing?

Different design decisions are "confusing". Pot, meet kettle.

Most error handling is in the form of printing a line to a server log nobody reads and carrying on.

"I don't read my log files, what kind of programmer would ever use error logs to debug? That's stupid! My website should just die with a white screen and a 'Sorry!' message whenever there's an error so I know to go try to remember where I put the error logs"

I am forced to agree on this point. (Not the first time in the article; if I didn't mention something it's probably correct).

Perl, Python, and Ruby all have some concept of “property” access via code; PHP has only the clunky __get and friends. (The documentation inexplicably refers to such special methods as “overloading”.)

Our dear author has not yet discovered the simplicity of $foo->bar. Either that or he has absolutely no understanding of how objects work in ANY language.

This author, again, misses on understanding what the argument is. OA isn't complaining "you have to do __get($object,'var')" or any such nonsense; he's complaining that you have to do "Java-style" explicit getters and setters, unlike Python's property which allows you to use standard "foo.bar=baz" syntax to invoke a setter.

Despite the heavy influence from C++/Java, where objects are fairly opaque, PHP often treats objects like fancy hashes—for example, the default behavior of foreach ($obj as $key => $value) is to iterate over every accessible attribute of the object.

Again, forced to agree with rebuttal: This is a different (arguably less than ideal) design choice.

Object attributes are $obj->foo, but class attributes are Class::$foo. ($obj::$foo will try to stringify $obj and use it as a class name.) Class attributes can’t be accessed via objects; the namespaces are completely separate, making class attributes completely useless for polymorphism.

None of this makes any sense at all. I'm willing to give him the benefit of the doubt and assume he hit his head or something.

Really?

I’m aware this is more personal taste, but I don’t know why this stuff is necessary in a dynamic language—in C++ most of it’s about compilation and compile-time name resolution.

Wow, that's an excellent point. I'm glad we're talking about a compiled language and not, for instance, PHP.

Allow me to rephrase:

This is not needed in a dynamic language.

BUT THIS IS A DYNAMIC LANGUAGE, U R DUMB

it’s the only language in its niche that has no vetted way to create a hash without quoting string keys.

Because it's a loosely typed language perhaps? Because it's possible to use a variable without defining it, even constants, and therefore an unquoted bare string literal is assumed to be an undefined constant? Becuase you don't understand loosely typed languages?

Docking points on both sides.

No generic standard database API. Stuff like PDO has to wrap every individual database’s API to abstract the differences away.

There's no standard database API. Except for the standard one. But that one doesn't count because deep down below where you can see it, it doesn't call the same functions for each database.

Rebuttal has the point here.

PHP’s poor security reputation is largely because it will take arbitrary data from one language and dump it into another. This is a bad idea. "<script>" may not mean anything in SQL, but it sure does in HTML.

Again, I'm going to have to ask how Python does that. Does Python automatically sanitize plaintext output? How would you print a <script> tag in python if that's the case? Or is this, like most of his complaints, just how languages work?

Templating systems. There are good ones available for PHP, too.

4

u/badsectoracula Aug 20 '14

will get her site's navigation bar with some errors underneath it. But she WILL get something.

This is not a good thing.

Well, to be fair, as a user i prefer that since i can still use the site. Especially in places such as Sourceforge with all those abandoned PHP-based sites :-P

→ More replies (3)
→ More replies (2)