As an embedded stick-in-the-mud Python2 developer, I'm mildly frustrated. It seems that the python community has been taken over by people trying to compete with NodeJS. Other use cases exist!
2019 Python Developer Survey
11–20 of 34 posts
Re: 2019 Python Developer Survey
#12Even if (or especially if) you are not on the latest and greatest Python version(s), I think it is still valuable to take the survey. We are locked in at 2.6 no matter what on one of our projects. We slowly whittle it away into other services, but making it modern is not feasible.
Should Python2 be consigned to history? Should C have been? I'm not so sure now. Python3 has a lot more to know, but not necessarily a lot more that's useful for what I do.
Re: 2019 Python Developer Survey
#13Seems like the survey was HEAVILY weighted to learn about how people use python for web / big data / cloud. As an embedded stick-in-the-mud Python2 developer, I'm mildly frustrated. It seems that the python community has been taken over by people trying to compete with NodeJS. Other use cases exist!
The fact of the matter is simply that Py3 has established itself as the main version of the language, and that datascience and web are two sectors where Python usage is currently ballooning. It may or may not stay that way in the future, but that’s how it is at the moment.
Re: 2019 Python Developer Survey
#14Seems like the survey was HEAVILY weighted to learn about how people use python for web / big data / cloud. As an embedded stick-in-the-mud Python2 developer, I'm mildly frustrated. It seems that the python community has been taken over by people trying to compete with NodeJS. Other use cases exist!
Re: 2019 Python Developer Survey
#15Is there actual hard data out there that suggests that Python provides significant benefits over a statically typed compiled language? I’ve been thinking quite a bit about how it seems that despite how fun Python is to write the dynamic types are really just a determinant with upsides that are essentially anecdotal. Why would one take a performance hit and give up a type system without hard evidence that there would…
Re: 2019 Python Developer Survey
#16Re: 2019 Python Developer Survey
#17Seems like the survey was HEAVILY weighted to learn about how people use python for web / big data / cloud. As an embedded stick-in-the-mud Python2 developer, I'm mildly frustrated. It seems that the python community has been taken over by people trying to compete with NodeJS. Other use cases exist!
Re: 2019 Python Developer Survey
#18Even if (or especially if) you are not on the latest and greatest Python version(s), I think it is still valuable to take the survey. We are locked in at 2.6 no matter what on one of our projects. We slowly whittle it away into other services, but making it modern is not feasible.
The reality is that Python2 and Python3 are really two different languages, not unlike C and C++. This is being recognized more as time passes. Should Python2 be consigned to history? Should C have been? I'm not so sure now. Python3 has a lot more to know , but not necessarily a lot more that's useful for what I do.
Re: 2019 Python Developer Survey
#19Seems like the survey was HEAVILY weighted to learn about how people use python for web / big data / cloud. As an embedded stick-in-the-mud Python2 developer, I'm mildly frustrated. It seems that the python community has been taken over by people trying to compete with NodeJS. Other use cases exist!
Probably the biggest reason to use Python back in early 2000's.
Re: 2019 Python Developer Survey
#20Even if (or especially if) you are not on the latest and greatest Python version(s), I think it is still valuable to take the survey. We are locked in at 2.6 no matter what on one of our projects. We slowly whittle it away into other services, but making it modern is not feasible.
The reality is that Python2 and Python3 are really two different languages, not unlike C and C++. This is being recognized more as time passes. Should Python2 be consigned to history? Should C have been? I'm not so sure now. Python3 has a lot more to know , but not necessarily a lot more that's useful for what I do.
I'm still surprised that python survived it, the update was so incompetently done. Just the huge amount of wasted developer resources on this mostly unnecessary update is staggering.