5 ms·
You keep talking about Python's problems, and I'm trying to talk about the habits I've noticed C programmers form and are rewarded for, but are bad for Python d
by diminoten 8y ago
You keep talking about Python's problems, and I'm trying to talk about the habits I've noticed C programmers form and are rewarded for, but are bad for Python development.
There are literally no habits in your mind that could be good in C but bad in Python?
- sys_64738 8y agoAs I am a veteran C programmer with decades of experience with several years of straight python now, what I see is a people who think they understand how to write complex software but don't grasp the fundamentals. This isn't explicitly a C V Python programmer discussion so much as exposing that Python insulates you from the peculiarities of things like debugging complex problems, writing robust code, good software practices, understanding libraries, scalability, parallel programming. The list is endless for the weaknesses of python and the developer who is comfortable there, which is fine given Python is a scripting language at heart.
- diminoten 8y ago> which is fine given Python is a scripting language at heart This is exactly the problem, and it's actually kind of rare to get an example of what you're talking about to show up in the very comments you're using to explain the problem! Very validating, that is. For the other folks reading this, imagine trying to work with someone who thinks these things. Imagine how unwilling to change their bad habits they'll be, since they think that because they're good at C means they're good at writing software. Any trouble they run into is the language's fault, not theirs!
- sys_64738 8y agoAre you claiming Python _isn't_ a scripting language? If it isn't then what the heck is it?!? What I find generally from Python developers who have lived an breathed the language for many years is that they accept there are fundamental failings and acknowledge the better means to workaround those. In reading back through your comments, it seems you are blinkered by those with the benefit of working in other languages. In particular, you seem to have hang ups about C which are not clear why. Perhaps you'd care to explain those.
- diminoten 8y agoPython is an object oriented programming language, not a "scripting" language. "Scripting" implies writing "scripts" (e.g. #!/usr/bin/python), but that's not it's only (or primary) use case, and in fact creates the problems I've been talking about above. Python the language has plenty of flaws. This conversation was never about Python however, it was about the bad habits C programmers bring to Python enterprise development, and how I struggle to work with C programmers because of those good-in-c-but-bad-in-python habits. I was curious if anyone else experienced these problems, and then you arrived and became a perfect example of the attitudes I encounter regularly from C programmers working in Python. I have no problems with C, it's obviously one of the most (if not the most) important programming languages of our time. My problem is with the habits some C programmers have brought to my Python projects.
- sys_64738 8y agoIt's clear you've had an unpleasant experience in the past. It's sounds like maybe you were burned in that experience and dumped the blame on a particular group.