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

Mostly about Go and OS stuff but haven't updated in a while. http://andrestc.com


The technical bar for EMs at Meta is quite high.


As a former EM at Meta, I beg to differ.


Harsh, but potentially fair. I think that pre-2016, there was definitely more expectation that managers should be graduates from IC ranks, but that got lost around one of the (many) doublings of headcount FB experienced over the last decade.


Most of the worst managers I've worked with now work at Meta.


Netflix is in the list.


"The policy document attained by TechCrunch shows Facebook plans to take up to a 30 percent cut of subscription revenue minus fees, compared to 5 percent by Patreon, 30 percent by YouTube, which covers fees and 50 percent by Twitch."

Looks on par with other providers.


How hard would it be to set up a backend payment service to receive $$ for gifts?


It's not that complex. You can have a paypal.me address or set up a stripe account with buymeacoffee.com. There would be many more but these two are at the top of my mind now.


This is amazing! Thanks for sharing


It's not as strong as the kernel. Go does not break APIs but may break undocumented behavior.


Author here.

>Also, while this article is quite rosy-eyed about cgroupv2, there are many many issues that mean that cgroupv2 is not really usable by container runtimes today -- despite what systemd might be trying to do with their "hybrid mode". A friend of mine from the LXC community gave a talk about the wide variety of issues that occur due to cgroupv2's weirdly restrictive API[3]. The blkio writeback cache limits are very useful, but they're really not worth the pain of breaking how container runtimes have to work.

I knew there are some problems with cgroup v2 but haven't quite looked into it. I'm going to watch the talk and probably add a note about that. Thanks!

>You can mount a single cgroupv1 hierarchy with multiple controllers attached to it (that's what 'cpu,cpuset' are), which then could (in principle) know about it each other. But they don't, since a lot of the cgroupv2 code is locked behind cgroup_on_dfl(...) checks. That's interesting, I didn't know about that! I'll add a note to the post.


Great article. Thanks


Nice writeup. Interesting enough, SIGKILL does not work from inside the container: https://andrestc.com/post/killing-container-inside/.


Thats the precise reason that I've started my blog, https://andrestc.com. I'm writing about things I'm learning while studying several topics.


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

Search: