Hacker Newsnew | past | comments | ask | show | jobs | submit | archmaster's commentslogin

check again!


somewhat better now! added a bit more concurrency. lesson learned: use tokio next time


It's like when your uncle squeezes you at Christmas. You're glad to see him again, but it's just a liiiitttleee... too... much... for... your... lungssss,.,.,.,


Anecdotally, I've run a bunch of traceroutes and reverse traceroutes to different locations and they tend to follow the same AS paths — although sometimes the traceroute will surface more routing through your ISP (especially from college networks). In general you are correct, though, and I would love to explain more about hot-potato vs. cold-potato (and other interesting routing decisions) in the future. Either way, the results the reverse traceroute provides are good enough for the purposes of explaining the internet, IMO!


I did a traceroute to how-did-i-get-here.net, and it went through a completely different network to the one they reported for the reverse.


Yup. Those paths are cached bidirectional.


check the html :)


Nice!


oh yeah i saw this! newer than the website though :)


This is awesome! To anyone interested in learning more about this, I wrote https://cpu.land/ a couple years ago. It doesn't go as in-depth into e.g. memory layout as OP does but does cover multitasking and how the code is loaded in the first place.


I love cpu.land! Thanks for creating such a fun resource.


Had the pleasure of helping rack drives! Nothing more fun than an insane amount of data :P


Thanks for helping!!!


Interesting. Got 19/20 too, and also missed #14!


i don't think it's your fault. spotify's entire website is down for me right now, i'm getting "upstream request timeout" and "upstream connect error or disconnect/reset before headers. reset reason: overflow" just trying to load the homepage. this happens every couple of months.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: