Python past, present, and future with Guido van Rossum [audio]
1–10 of 151 posts
Re: Python past, present, and future with Guido van Rossum [audio]
#2I've only started this particular episode, but the Talk Python to Me podcast is pretty stellar and has contributed a lot to my addiction to technical podcasts.
Re: Python past, present, and future with Guido van Rossum [audio]
#3After years with Python, it's still a mystery to me how the same constructs are so intuitive and readable in Python (think it acceptable that they are less in C++, Java or javascript etc, even Ruby)
Re: Python past, present, and future with Guido van Rossum [audio]
#4The unofficial python 2.8 is here:
Re: Python past, present, and future with Guido van Rossum [audio]
#5I've recently had to start writing python professionally and I'm not super impressed. My previous python experience was writing small services and fixing others code. Now that I'm working on larger "apps" it feels like a 90's language with all the rough edges and warts. I'd rather being working in a language with better language services and tooling, but python has numpy and all these data viz libraries so whatcha gonna do? At least I get a little reprieve with TypeScript; never thought I'd be so happy to work with the node platform, but there you have it.
3.5 looks attractive but there are just fundamental issues with the lang and language services. It's a bit like lipstick o... Well, I'm not going to say it.
Re: Python past, present, and future with Guido van Rossum [audio]
#6I've recently had to start writing python professionally and I'm not super impressed. My previous python experience was writing small services and fixing others code. Now that I'm working on larger "apps" it feels like a 90's language with all the rough edges and warts. I'd rather being working in a language with better language services and tooling, but python has numpy and all these data viz libraries so whatcha go…
What do you mean by "language services and tooling"?
Python 3.5+ supports gradual typing, too so I'd be interested in a real comparison to Typescript.
Re: Python past, present, and future with Guido van Rossum [audio]
#7I've recently had to start writing python professionally and I'm not super impressed. My previous python experience was writing small services and fixing others code. Now that I'm working on larger "apps" it feels like a 90's language with all the rough edges and warts. I'd rather being working in a language with better language services and tooling, but python has numpy and all these data viz libraries so whatcha go…
Try PyCharm if you need that kind of support. I'm usually happy with just pyflakes and linters.
Re: Python past, present, and future with Guido van Rossum [audio]
#8I've recently had to start writing python professionally and I'm not super impressed. My previous python experience was writing small services and fixing others code. Now that I'm working on larger "apps" it feels like a 90's language with all the rough edges and warts. I'd rather being working in a language with better language services and tooling, but python has numpy and all these data viz libraries so whatcha go…
What rough edges and warts? And what fundamental issues?
Re: Python past, present, and future with Guido van Rossum [audio]
#9I've recently had to start writing python professionally and I'm not super impressed. My previous python experience was writing small services and fixing others code. Now that I'm working on larger "apps" it feels like a 90's language with all the rough edges and warts. I'd rather being working in a language with better language services and tooling, but python has numpy and all these data viz libraries so whatcha go…
[deleted]
Re: Python past, present, and future with Guido van Rossum [audio]
#10The unofficial python 2.8 is here: https://github.com/naftaliharris/tauthon
But didn't Guido say that everything what could be backported was already backported?
> There are a small handful of backwards incompatibilities introduced by Tauthon.
How to understand this?
Anyway, something like this was expected to happen. I wonder if it wouldn't be better if Guido would not halt python 2 development and just let it evolve.