2,485 karma · joined November 3, 2009
Sad and cowardly, hardly surprising.
Whose? Isn't that exactly the issue?
These sjws are complete parasites. They never fork. Just go after vulnerable people at the top and insinuate their way into established institutions.
And they seem to be winning.
* IDs are returned in sorted order
* IDs are generated one after another, ie could be implemented as a generator or coroutine
* No additional space required during the computation
Resulting in a single pass.
1. centralization of all dns lookups is worrisome
2. Dns should not be handled by applications. It should be handled by the operating system.
I see a lot of people conflating the two in the comments.
http://charlesleifer.com/blog/new-features-planned-for-pytho...
It is sad that there are people out there who will try to ruin your day if you don't do what they want. Especially considering the work we put into these libraries.
Python is great, but it will never be perfect. But the outrage stuff, the entitlement stuff, essentially anything that happens on Twitter... Python seems like a victim of it's own success. Once it got popular, it couldn't scale the checks that might have stopped this runaway train of shit-tweets and bickering on the mailing list.
Personally I don't like a lot of the things that have happened in 3 (asyncio, type whispering, fstrings). I can't help but wonder if, again, this is due to becoming too popular too fast. I say that because aesthetically these features seem to go against the Zen of python.
May you never have users, but if you do, may they not have Twitter accounts!
http://www.inf.puc-rio.br/~roberto/lpeg/
The operator overloads are a lot to reckon with, beyond just the concepts, but it seems like there's something there worthwhile of study and learning. Hope to give it another try.
Be interested in any introductory material, if anyone has some good links.
As you can probably tell, I'm not at all a fan of the way Redis is moving. It hit a sweet spot as a "better memcached" but apparently aspires to be a real database, so now this nice simple tool is all crazy. The new protocol just kinda sucks for synchronous use.
I'd go with a hand-written in-memory caching scheme before I ever considered a Redis sandwich with this feature. Seems like a complexity nightmare and very difficult to reason about. Yeah maybe I'm being crusty, but I'm just thinking about maintaining and debugging something like this and having cold sweats. The linked redisconf talk clearly bears this out. Sounds like they had a hell of a time. But then that also provides some measure of job security?
Forgot to add: sleep shit. What's up with that?