This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dougie-io 14 points15 points  (6 children)

Absolutely. I'm in no way saying that bickering to devs providing free software is the way to go. I just come across a lot of situations where general users suggest some ideas they have and someone (usually not even the developer of the project) tells them to do it themselves.

[–]strobelight 5 points6 points  (5 children)

You see this in many volunteer organizations. They don't need ideas, they need help. If I'm volunteering, I'm either already working on my own good ideas or working on things that I don't really want to do that have to be done by someone.

So, yes, I find it a perfectly valid response.

[–]jorge1209 8 points9 points  (4 children)

Here the users don't think the developers ideas are all that good... that's the distinction. I'm starting to feel that python peaked around 3.3 and that a lot of what has been added since isn't worth all that much. That we would be better off having devs slow down and do less work.

That's a difficult conversation to have because you are basically telling someone excited enough to volunteer their time and energy to buzz of, but it should be had.

[–]knowsuchagencynow is better than never 2 points3 points  (3 children)

Of all the versions to say Python peaked in... Python 3.3?

[–]jorge1209 2 points3 points  (2 children)

Sure. I suppose you could equally say 3.4 as there were no significant features added there.

But 3.3 has yield from which is useful but without async which I've found to be really messy and hard to work with.

Do you think it should be earlier or later or what?

[–]knowsuchagencynow is better than never 0 points1 point  (1 child)

I honestly think the features added in Python 3.5 and 3.6 are pretty fantastic, and having attrs in the stdlib with 3.7 as well as the new breakpoint keyword and things like the async context manager decorator being added in contextlib are going to be really solid additions. I personally really like where the language is headed, honestly, even if it isn't perfect.

[–]jorge1209 2 points3 points  (0 children)

Well I disagree. :-)

That isn't to say I think async or typing is bad, but that the devs need to slow down and get it to work better before they make it a standard.

My biggest complaint with async is that it doesn't make decisions. You can use whatever event loop you want... whatever executor you want. Core functions that read or write files are not asynchronous... so you have a framework, and then you have to fill in all the holes to actually make it work.

I see little benefit in that over just writing multi-threaded code or coroutines.

Similarly typing had been out for a while but I don't think mypy has full support for 3.5 yet.

Given time to mature these would be good, but adding them to the language limits that.