boulos

Compared to roll-your-own with S3 or GCS it does :)

Will do. I wanted mostly to (re)inform the submitter.

Please don't editorialize titles unless they're clearly clickbait.

"Designing AI for Disruptive Science" is a bit market-ey, but "AI Risks 'Hypernormal' Science" is just a trimmed section heading "Current AI Training Risks Hypernormal Science".

Our sixth generation sensor suite is intended for winter driving: https://waymo.com/blog/2025/10/creating-an-all-weather-drive... for some nice visuals.

On recent podcasts, Ilya says he's no longer assuming they can jump straight there.

Maybe the author isn't aware that Chainguard is going to keep patching MinIO for CVEs:

https://www.chainguard.dev/unchained/secure-and-free-minio-c...

You wouldn't get the other changes in this post (e.g., restoring the admin console) but that's a bit orthogonal.

> The entire global software industry is worth less than $1 trillion dollars

Are you saying "worth" as a shorthand for something like annual profit? If you sort the 2025 data by earnings, you get pretty large numbers quickly: https://en.wikipedia.org/wiki/List_of_largest_technology_com...

That's not how you should measure "worth". In that world, you'd have a P/E ratio of 1. Comparing to a bond, it would be like expecting to get paid the face amount in a single year. Many people are quite happy with 5-10% interest as a risky benchmark, so 10-20 P/E isn't wild. That puts the market cap for tech itself at 10-20T as a reasonable baseline.

I feel vindicated :). We put in a lot of effort with great customers to get nested virtualization running well on GCE years ago, and I'm glad to hear AWS is coming around.

You can tell people to just do something else, there's probably a separate natural solution, etc. but sometimes you're willing to sacrifice some peak performance just have that uniformity of operations and control.

This isn't strictly correct: you probably mean wrt compressed size. Compression is a tradeoff between size reduction and compression and decompression speed. So while things like Bellard's tz_zip (https://bellard.org/ts_zip/) or nncp compress really well they are extremely slow compared to say zstd or the much faster compression scheme in the article. It's a totally different class of codec.

IIRC, Google contributed +-400 racks last year to Open Compute: https://cloud.google.com/blog/topics/systems/enabling-1-mw-i...

I haven't benchmarked them myself yet, but the C++23 flat map containers are supposed to finally have fixed this. Chrome lists them as TBD: https://chromium.googlesource.com/chromium/src/+/main/styleg... .

Wait, really? I haven't been up this season, but it's always been there! I understand removing the printed ones when the bars have them (and the big boards at the top). Is it all just ads now?

Every lift at Snowbird has the map printed on the bar. So you can plan your route on the way up. I agree that when you get lost, that map won't save you, but I think an offline PDF is also fine.

You can get by pretty well with the ~$20/month plans for either Claude or Gemini. You don't need to be doing the $200/month ones just to get a sense of how they work.

I dunno. The folks at Physical Intelligence are showing remarkable progress for being such a small team and relying on Gemma as their base model.

https://www.pi.website/blog/pistar06 has some reasonable footage of making espresso drinks, folding cardboard boxes, etc.

This seems to be the only online source for Loren's passing that contains much information.

How would you distinguish the article from an honest write up about transistors? That is, you know about his crusade in ML, but if you didn't, how would you decide that this article is written in bad faith or not?

I agree that context matters, and I had the same thought as you. But does that mean that anything he writes on the topic of "who was first" is inherently tainted?

Disclosure: I used to work on GCE.

Nice write up and very clever work. I'm surprised by the AWS response that you linked to though (https://aws.amazon.com/blogs/security/ec2-defenses-against-l...).

While I was sure they'd note that Nitro doesn't have this vulnerability due to its design, it seems weird not to talk about Firecracker and Lambda and so on. Maybe those are always on Cascadelake+ hardware? (I also haven't followed this space for 5 years, so maybe I'm asking the wrong question)

Ehh, PHP fits that bill and is clearly optimizable. All sorts of things worked well for PHP, including the original HipHop, HHVM, my own work, and the mainline PHP runtime.

Python has some semantics and behaviors that are particularly hostile to optimization, but as the Faster Python and related efforts have suggested, the main challenge is full compatibility including extensions plus the historical desire for a simple implementation within CPython.

There are limits to retrofitting truly high performance to any of these languages. You want enough static, optional, or gradual typing to make it fast enough in the common case. That's why you also saw the V8 folks give up and make Dart, the Facebook ones made Hack, etc. It's telling that none of those gained truly broad adoption though. Performance isn't all that matters, especially once you have an established codebase and ecosystem.

He was pretty open about his design process, and I think he did voice this: https://www.youtube.com/watch?v=ENa2Hmh3lGU

I can't seem to find the 2007 webpage (maybe it was one of the wiki-based ones?) but the 2008 syllabus looked very hands on: https://web.archive.org/web/20081208171743/http://stanford.e...

I never took 193p, but I always found 148 to be hands on, and I made it very hands on for the year I contributed: https://web.archive.org/web/20130522184434/https://graphics.... .

I regret that we put my subdivision assignment as the last one, and we allowed students to skip one assignment. Most students skipped it, but those that did the work thought it was super cool to have their own subdivision tool for making smooth meshes.

They linked directly to https://alexgaynor.net/2019/apr/21/modern-c++-wont-save-us/ which did exactly what I'd guessed as its example:

> The following code for example, simply returns an uninitialized value:

  #include <optional>

  int f() {
    std::optional<int> x(std::nullopt);
    return *x;
  }

Not at all. We've been working on this for a while, and we're now comfortable with the reliability bar we've hit to begin a gradual rollout to the public. As people said, this has been years in the making.

Make sure to do whatever "express interest" is required inside the app. We've often done a first-come, first-served approach for getting people off of waitlists, so get in now :).

Sorry about that. Please file in-app feedback (now under Help > Leave Feedback) any time you experience something like that. There's a dedicated "Car Condition" tag.

We comply with the posted speed limits. Definitely on 101 near San Francisco where there are 55 mph zones (and maybe even 50 mph?) it's pretty noticeable. But we do hug the right lanes.

That is precisely what this one was. The OP posted a follow-up comment at https://www.reddit.com/r/Terminator/comments/d65pbi/comment/...:

> I have an updated, I found out that T2 4K is an HDR movie that needs to be played with MadVR and enable HDR on the TV itself, now the colors are correct and I took a new screenshot: https://i.imgur.com/KTOn3Bw.jpg

> However when the TV is in HDR mode the 4K looks 100% correct, but when seeing the screenshot with HDR off then the screenshot looks still a bit wrong, here is a screenshot with correct colors: https://i.imgur.com/KTOn3Bw.jpg

Yes, there have been a couple re-render the whole thing. There was a good write up somewhere that I cannot find now where there was a discussion of keeping RenderMan bug compatible with the original or not. They also upped the shading rate and a few other quality knobs.

I recommend interviews with Roger Deakins, like https://m.youtube.com/watch?v=w56rFxPyZno

> A total of 15 participants received CTX310 and had at least 60 days of follow-up. No dose-limiting toxic effects related to CTX310 occurred. Serious adverse events occurred in two participants (13%): one participant had a spinal disk herniation, and the other died suddenly 179 days after treatment with the 0.1-mg-per-kilogram dose.

> Editing of ANGPTL3 was associated with few adverse events and resulted in reductions from baseline in ANGPTL3 levels.

Two out of 15 having adverse advents seems pretty high, especially since one died. The supplemental material rules this as an unrelated death (https://www.nejm.org/doi/suppl/10.1056/NEJMoa2511778/suppl_f...).

Definitely seems promising for a larger-scale trial, but it seems weird to make such a strong conclusion about adverse reactions.