Raymond Hettinger - the brilliant man that always gets interrupted in tech talks
@yuzhou98936 жыл бұрын
by lunch
@bilbobatista36007 жыл бұрын
te best python lecturer imo
@simonmasters32955 жыл бұрын
Absolutely #TheBest Bilbo
@ugodonini61826 жыл бұрын
I find always something interesting to learn in Hettinger speech
@cosmicallyderived7 жыл бұрын
One interesting thought about the compactness they discovered from Donald Knuth's indexing technique inspired from database work makes me think about the storage constraints and pressures the industry was in during his active period. Those pressures very likely drove him to devise a solution to best satisfy the needs of his time, but as it turns out when attempting to optimize along a dimension that's been perennial you may very well find it best to look at earlier solutions.
@muppalaneninitin6 жыл бұрын
Thank you for another very informative talk Raymond! A level of indirection and such reduction in memory and improvement in hash performance!
@malayagr3 жыл бұрын
"All problems in computer science can be solved by another level of indirection." - David Wheeler.
@bharatggaikwad6 жыл бұрын
Best lecture... 3.6 dictionary ... Thanks a lot Raymond Hettinger.
@joshuafilbert32605 жыл бұрын
Wonderful lecture, lousy display format. Too much screen space for pycon logos and the slides are too small
@RoamingAdhocrat3 жыл бұрын
Maybe 4:3 presentation with the video and logos on the right margin would be better
@victornoagbodji7 жыл бұрын
amazing presenter, amazing talk!
@manoharchowdary14782 жыл бұрын
Amazing talk, very informative..
@wschmidt227 жыл бұрын
So good!
@minyakonga889710 ай бұрын
If you run the script about instance dictionaries at begining in Python 3.11, it will print [280, 280, 280], it is same as Python 2.7, what happened?
@yuzhou98936 жыл бұрын
lunch needs to be eliminated from pycon, so Raymond for once can speak longer.......
@ikickss6 жыл бұрын
Nah. This guy is kinda longwinded, so if they him, he will talk longer for less content.
@simonmasters32955 жыл бұрын
Longwinded? @@ikickss you lack #Discernment
@RoamingAdhocrat3 жыл бұрын
"dr sheldon cooper from the big bang theory" - nice reference to the "the ice planet hoth from star wars" critique of that tedious show
@aoeu2565 жыл бұрын
Hash lookup should be a CPU instruction haha. Lisp machines and small talk machines could do this....
@con-f-use7 жыл бұрын
The links to the slides don't seem to have the slides...
@bobmvideos7 жыл бұрын
I haven't found the Sphinx page presented here, but the one for his talk at SF Holiday Meetup is here: dl.dropboxusercontent.com/u/3967849/sfmu2/_build/html/index.html
@SteelBlueVision6 жыл бұрын
404
@Verrisin4 жыл бұрын
23:10 - Can one not implement .hash() poorly for some class? Of course it would be unsafe.
@peterholzer44812 жыл бұрын
Yes. It is entirely permissible to implement a hash method which always returns 42. Or one which uses only some fields of an object. Git is safe, because it has only a handful of fixed object types and those are controlled by the git developers. A Python program OTOH contains lots of classes implemented by the programmer and if the programmer bothers to implement a hash function at all it is far from certain that they implement one which is as good as SHA-1 over byte streams. So removing that equality test would indeed be very unsafe. (also 64 bits isn't that much, You would expect a collision for a hash of 4 billion entries, which is not impossible. 160 Bits (SHA-1) is *a lot* more.)
[25:58..26:02] shades of blockstore scanning for next free block and policy which followed
@Chandelier-o9n2 жыл бұрын
评论👍支持
@pradeep4226 жыл бұрын
33:49 lol wht?
@rem0rt4 жыл бұрын
damn fantasy tales style is all over nowadays. so pure. just tell the subject please, no farytales.
@MrEnvy9996 жыл бұрын
kuh
@rurban7 жыл бұрын
He speaks like python hash tables are the best of the field. They are not. They use now the same compaction trick as PHP, which saves space for big tables (but is not state of the art due to its added indirection), trash the key cache by storing the computed hash same as Perl (several benchmarks show recomputation or simplier checks are faster for smaller keys), and are generally still 5 years behind state of the art hash tables. They still use seperate chaining without even storing the chains as array (much faster), or move to front (state of the art with this old method). State of the art would be robin-hood or hopscotch hashing of course. Less hype and more technical content please.
@quantum-t6 жыл бұрын
Wow, you seem to be smarter than he (no)
@MMABeijing5 жыл бұрын
@@quantum-t he was factual in his comment, unlike you. good job
@simonmasters32955 жыл бұрын
Assert Dec 2018 = today() 45,000 views, 600 likes, 20 comments #rurban made his comment a year ago Raymond spoke at PyConn in May 2017 TheXmaximX Max and MMABejing made comments within last 3 months *** Q: Do We Have A Development Team ? *** What is the "temperature" of the KZbin comments section for thisVideo?
@seanspicer5165 жыл бұрын
ah the time honored tradition (inherited from our ancestors) of the "technical one-up-ance". personally, if it isn't going to cause some harm due to misinformation, i just cede that the other is smarter. "go-in-dumb". bc u kno, screw conformance.
@GordonAitchJay5 жыл бұрын
Which languages implement state of the art hash tables? It'd be interesting to know how performant V8's hash tables are compared with Python's.