Python has wonderful set of libraries so it is probably going to stay with us for a while. However, I suspect major takeover by Typescript (despite I like Python more).
My money would be on Go and Rust. Most of the major downsides of either language go away if you let the agent write almost all of the code Go might have the advantage because it's easier to read outside the IDE
Is Python Becoming Pinyin?
11–20 of 82 posts
Re: Is Python Becoming Pinyin?
#12Python has wonderful set of libraries so it is probably going to stay with us for a while. However, I suspect major takeover by Typescript (despite I like Python more).
Re: Is Python Becoming Pinyin?
#13Python has wonderful set of libraries so it is probably going to stay with us for a while. However, I suspect major takeover by Typescript (despite I like Python more).
Re: Is Python Becoming Pinyin?
#14Python has wonderful set of libraries so it is probably going to stay with us for a while. However, I suspect major takeover by Typescript (despite I like Python more).
Interesting. Can you please elaborate more? Is it due to the combination of popular foundation (js) and the addition of strong typing? The runtime environment differences? The ease of integration with other languages / tools?
Re: Is Python Becoming Pinyin?
#15Earlier quoted context omitted.
Interesting -- I still think that Python is an easier onramp than TypeScript for new developers. But given the popularity and depth of JavaScript, and the clear advantages (and popularity) of TypeScript in serious development, that's not a bad prediction.
js is a web scripting language that can be strong-armed into running scripts through a runtime. Python is a general development language that can be used to build servers and web pages, but does a lot more besides. They're not really comparable. Having said that - I wouldn't be surprised if Python drifts towards stronger typing, although it will probably remain optional.
Re: Is Python Becoming Pinyin?
#16Re: Is Python Becoming Pinyin?
#17Earlier quoted context omitted.
Interesting -- I still think that Python is an easier onramp than TypeScript for new developers. But given the popularity and depth of JavaScript, and the clear advantages (and popularity) of TypeScript in serious development, that's not a bad prediction.
js is a web scripting language that can be strong-armed into running scripts through a runtime. Python is a general development language that can be used to build servers and web pages, but does a lot more besides. They're not really comparable. Having said that - I wouldn't be surprised if Python drifts towards stronger typing, although it will probably remain optional.
Re: Is Python Becoming Pinyin?
#18Python has wonderful set of libraries so it is probably going to stay with us for a while. However, I suspect major takeover by Typescript (despite I like Python more).
Interesting. Can you please elaborate more? Is it due to the combination of popular foundation (js) and the addition of strong typing? The runtime environment differences? The ease of integration with other languages / tools?
* Most applications run on the web nowadays. With TypeScript, you can write both the front end and the back end. * TypeScript shares many syntactic-sugar ideas with Python, but it is also statically typed. Whether that is good or bad is a hot topic, but it gives you a lot of confidence through compile-time checks. * Running Node for system tasks is as easy as running the Python interpreter. However, Python is still slightly ahead there.
Re: Is Python Becoming Pinyin?
#19So that it's easy for humans to review it. Same reason as ever. Obviously Python isn't always the correct choice, but the overlap with cases where vibe coding is the correct choice is pretty high.
Also wtf is Pinyin?
Re: Is Python Becoming Pinyin?
#20It’s funny because I consider myself a Python veteran - about a decade or so of Python, and I had exactly the same thought. 99% of my code now is Java. It’s much less pleasant but the “enterprise nobs” just work. Static types, fast with Graal, awesome threading, and the quality of tooling are great - those are all areas that Python severely lacks in and has no interest expanding into, because it is a “fast prototype…
I do not think subpar means what you think. Or maybe you rewrote the sentence and forgot to change that word? Anyway, this does not make sense.