r00tbeer

The first patch release (released on launch day) says: "Messaging to distinguish particular users hitting their user quota limit from all users hitting the global capacity limits." So, collectively we're hitting the quota, its not just your quota. (One would think Google might know how to scale their services on launch day...)

The Documentation (https://antigravity.google/docs/plans) claims that "Our modeling suggests that a very small fraction of power users will ever hit the per-five-hour rate limit, so our hope is that this is something that you won't have to worry about, and you feel unrestrained in your usage of Antigravity."

Avoiding this scenario is why Google will renew all the domains for every startup it has ever acquired in perpetuity.

See https://irenezhang.net/papers/demikernel-sosp21.pdf for a more thorough paper on the Demikernel from 2021. There are some great ideas for improving the kernel interface while still allowing efficient DPDK-style pipelines.

I think that URL gets served by the same single binary. Might look like multiple files and connections to you ...

"To the best of my knowledge, this derivation is more efficient than the standard published Bresenham or midpoint circle formulations I found on-line. All of them seem to require more operations. In the branching version, mine requires only 3 to 6 adds — that’s it. The standard algorithms I’ve seen listed tend to require 9 or more."

This is from June, 2018. (That should be in the title.) I'm curious how the last five years have been for Costco.

Hasn't everyone learned that "store all the history of changes" is an anti-feature? The Legal departments generally do not care for this (its just more data to make sure you deleted). And it makes schema migrations more painful as not only do you have to migrate the data you have now, but all of your historical data too! If you add a new property do you backfill it in your old data (to keep your code working)? Or start special casing old version in your code? Neither is pretty.

If you want historical audit trails, make them intentional and subject to the same rules and patterns as your regular data.

This is systems debugging: "After hacking around for a while I got nowhere, but in so much detail."

I wonder how often it is an advantage to not know English. Then you might have less baggage from outside the computer and you might map the token to what it actually does in the system (rather than what the token was aspiring to be). Assuming you can get to that point, of course.

Here's my playlist. First the good ones that are actively in my queue (in general order of recommendation):

- The Memory Palace: http://thememorypalace.us/ (these are stunningly good historical stories)

- On the Media: http://www.wnyc.org/shows/otm/

- Reply All: https://gimletmedia.com/reply-all/ (this is the one I expected to see on every list at hackernews, and don't)

- The Gist: http://www.slate.com/articles/podcasts/gist.html

- The Daily: https://www.nytimes.com/column/the-daily

- 99% Invisible: http://99percentinvisible.org/

- Economist Radio: https://radio.economist.com/

- New Yorker Radio Hour: http://www.wnyc.org/shows/tnyradiohour/

- Planet Money: http://www.npr.org/sections/money/ (not the juggernaut of content they once were)

- This American Life: https://www.thisamericanlife.org/

Shorter series (or just defunct or really rarely updated) that I can recommend to this crowd:

- Zachtronics Podcast: http://www.zachtronics.com/podcast/

- Revisionist History: http://revisionisthistory.com/ (should be starting a new season soon)

- Mystery Show: https://gimletmedia.com/mystery-show/

- A Life Well Wasted: http://alifewellwasted.com/ (great videogamey series)

- Containers: https://www.flexport.com/blog/alexis-madrigal-containers-pod...

- S-Town: https://stownpodcast.org/

Listening at 1.8x for most of these shows forces me to pay attention, and let's me consume more content. The exception is for The Memory Palace which deserves to be heard exactly as Nate makes it (1x).

Most of the commenters here didn't seem to read James' whole article. He's not saying that you should throw away isolation but that isolation should be taken care of from your architecture, not your programming language. Of all the places that should be up on a microservices architecture and see the sanity of it, you would think that would be here on HN, no?

Sending the SSL keys to the FBI as a multi-page printout in 4-point font when the government doesn't specify what format it wants is pretty funny. (Page 127 - 137.)

Ah, you're right. Its only the thread stacks that were conservatively scanned, not all of memory (see "Mostly Accurate Stack Scanning" for some indirect evidence of such). Its not clear to me if modern JVMs are still conservatively scanning stacks or not. But clearly its much less of a problem than conservatively scanning all of memory.

I know early JVM garabage collectors were also "conservative", but I don't recall JVMs running into these sorts of problems. Maybe folks are just using more of the 4G address space these days than back in the day of conservative GC JVMs?