I imagine, though I don't know, that the requirement to use the index name and contents also dictates allocation.
4,617 karma · joined July 20, 2010
I imagine, though I don't know, that the requirement to use the index name and contents also dictates allocation.
If you watch The Simpsons DVD commentary on the very first season DVDs, they talk about how Matt Groening's team would draw the key frames and then they would ship them to an asian animation studio to provide the animation frames. The very first time they did this, they got an animation style that was all over the place - not just the quality of drawing, but the actual animation style was jello-y and way more wobbly than they wanted. You can see it on YouTube here: https://www.youtube.com/watch?v=sx-wjF5AMmk
The main reason that they sent it back was that the style and physics represented in the cartoon wasn't the one they were going for, and it changed how the show felt. I feel like the rapid cut references they adopted from Family Guy did a very similar thing. It changed the flow of the show, which, maybe (?) is actually more of a sign of the times and attention span than animated show style, but still, I wasn't a fan and I didn't feel like The Simpsons did it naturally or that it fit, and it takes me out of the narrative every time they do it.
I opted to upgrade my seat to premium for $100/mo, and I've used it to write code that would have taken a human several hours or days to complete, in that time. I wish I would have done this sooner.
This feels like a stretch to say that this happens independent of weight loss, and much more like we may have underestimated the impacts of weight loss on all of these other facets of life.
[1] - https://pmc.ncbi.nlm.nih.gov/articles/PMC12431743/
[2] - https://med.stanford.edu/news/insights/2025/04/ozempic-addic...
really?
This only works so long as the atmosphere being displaced weighs more than the balloon plus the payload. As soon as the air gets thin enough that the weight of the balloon+payload is equal to the weight of the air that would fill the volume of the balloon, then it stops rising. (Or, more likely the balloon rips open because it expanded farther than it could stretch).
Usually, this is really high in the atmosphere, but it's definitely not space.
This is all ignoring that orbit requires going sideways really, really fast (so fast, actually, that it requires falling, but going sideways so fast that the earth curves away and you miss).
It seems easier for the cloud provider to implement the equivalent of a dry-run flag in API calls that validate that the call would succeed (even if it's best effort determination) which could be used by tools like Terraform during the planning and dependency tree generation.
Instead, you have platform providers like AzureRM that squint at the supplied objects and make a guess as to whether that looks valid, which causes a ton of failures upon actual application. For instance, if you try to create storage with a redundancy level not supported by the region you're adding it to, Terraform will pass a plan stage, but the actual application of the resource will fail because the region doesn't support that level of redundancy.
There are unlimited other examples in a similar vein, all of which could be resolved if API providers had a dryrun flag.
I would agree with the small adjustment of, 'every device should be able to have a globally routable IP'.
There are a lot of devices, like the ones we're talking about, that should not be accessible to the internet at large. You're not preventing them from getting a public IP because you don't have enough, you're preventing them from having a public IP as part of the belt-and-suspenders approach because there's no need to have one.
I mean, I agree with them. I think people who say 'NAT is not security' are only correct in the absolute most pendantic way and that the way NAT is commonly configured is literally the only reason the internet doesn't consist mostly of botnets.
But I also suspect that if IPv6 were more common, we as a society would be better at it, and not do dumb things like hand out globally routable IPs via DHCP6
For anyone who is reading this but hasn't use IPv6, IPv6 addresses are a large flat 128-bit contiguous address space, but they are not universally routable. The prefix of any specific address determines what group of other IPs can get to it.
We often think of a computer as having an IP address, but with IPv6, computers will have several addresses, all with different prefixes to handle different types of traffic.
This site does a decent job of explaining - https://networklessons.com/ipv6/ipv6-address-types