News for hackers. Stuff that matters.

A comment on Schedule – Python job scheduling for humans. Parent comment

Re:Schedule – Python job scheduling for humans by icebraining on Saturday October 03, 2015 @10:44AM (#10324048)
Monkeys? Where did that come from? The idea of "for humans" just means that the UI was developed with an humane approach - as opposed to an undesigned UI, or one designed merely for the simplicity of the implementation, and that doesn't take into consideration things like our need for consistency to make up for a non-perfect memory.

That said, I personally don't think Celery suffers from this problem, but API that was being replaced by the first project to used this moniker - urllib2 - definitively did.

[ Parent | on HN ]
Re:Schedule – Python job scheduling for humans by mpdehaan2 on Saturday October 03, 2015 @11:30AM (#10324212)
It's a stand in for something "not for humans". On second thought, monkeys would require an even easier UI. Perhaps "people that like pain".

I don't think it's fair to say the other tools weren't designed, or merely designed the easy way.

urllib2 has some rough edges - and some things should be better, but it can also do some things requests can't do, and I've had to reach for it on a few occasions. requests has basically optimized for the easy case, where

urllib2 wished to be more flexible in certain areas, so it deserves some merit there too.

[ Parent | on HN ]
Re:Schedule – Python job scheduling for humans by Drdrdrq on Saturday October 03, 2015 @11:30AM (#10324209)
> API that was being replaced by the first project to used this moniker - urllib2 - definitively did.

For curious: that was python library requests. And the claim was more than deserved in that case.

[ Parent | on HN ]