I've printed and used intake manifolds for (automotive) engines in the past, without issue. Obviously that's not the same stakes as an aircraft, but I don't see why it wouldn't be possible to do safely.

I’m not necessarily saying it can’t be done. But these are plastics that fail under heat. I’d test part for non critical applications and I’m just a nobody amateur.

These guys are messing with planes and don’t test enough? Is there an explanation these people aren’t just incompetent?

Not that I can think of, honestly. I'd be extremely hesitant to use a part I printed on an aircraft. If I had to, I'd make very sure to test multiple copies to destruction.

> But these are plastics that fail under heat.

All materials ultimately succomb when exposed long enough at some high enough temperature.

What is the temperature range to match here?

> All materials ultimately succomb when exposed long enough at some high enough temperature.

I'm not a material scientist, but I don't believe that to be true. Metals don't to my knowledge; they suffer oxidation, which is allayed by the presence of oil.

If you mean plastics in particular, then PEEK would be ideal to my knowledge - it's suitable for immersion in gasoline and similar solvents, and I've used it in the past for a fuel pump mounting bracket that sits inside the fuel tank of a (gasoline) vehicle. I checked it after a year and it doesn't seem to be any worse for wear.

It's just a huge pain to print!

> What is the temperature range to match here?

I'm not sure, and likely couldn't be sure without a fair amount of research. If I had to print this for a plane, I'd want to do that and measure temperature in use and under high load and destructively test several drafts to ensure performance.

From what I've seen in this instance though, the failed part showed a Tg (glass transition temperature) of 55ºC - basically exactly that of PLA-CF. The pilot believed it was ABS-CF, which has a Tg of ~100ºC. If we assume that 100ºC was at least higher than the expected operating temperature, PEEK (Tg: 143ºC) would have given a ~50% safety margin.

My daily driver is a '91 GMC, with a 350 (5.7L TBI). It's got 140k miles on it, burns no oil, and I fully expect it to outlive me.

I would buy a brand new Toyota 22RE today if they still made them.

Could it be part of a broader effort to establish a false digital footprint?

In that vein - if they are upvoted by real people, does it matter?

Of course it does. People are using forums and social media to connect, however flimsily, with other people.

Replacing that with bots and thinking that's equivalent is actually really sad

For what it’s worth, I agree - I’m just no longer certain I could tell.

I read the article, so I realize this is only relevant to the title… but others might find it amusing.

I recently found out that my state university has livestock stalls for rent for student use. My daughter is considering attended and asked if she could take her sow with her. She said they didn’t even react like it was an uncommon request!

Surely "admissions" does not include scheduled doctor's appointments?

Based on the data it seem it does.

"HES contains records of all admissions, appointments and attendances at NHS-commissioned hospital services in England."

One could limit the data to accidents and illnesses. Outcome of pregnancy would then not qualify unless there were complications.

As a Staff+ Engineer -- Principal in a couple of weeks -- for me it's about "batteries included", support availability, and ability to hire.

Using a cloud platform means that while your needs are small, you're overpaying. Where it pays off is when you have a new requirement that needs to be met quickly.

I've done my share of managing database instances in the past. I can spin up a new RDS Postgres instance in much less time than I can configure one from scratch, though. Do we need a read replica? Multi-site failover? Do we need to connect it to Okta, or Formal, so we can stand up a process to provision access to specific databases, tables, or even columns? All of those things I can do significantly faster and more quickly on AWS than I can do it by hand.

What if a NoSQL database is the right solution for us? I have much less experience adminning those, so will either have to allocate a fair amount of my time to skill up or hire someone who already has those skills.

Need a scheduled task? Sure, I could set up a Jenkins server somewhere and we could use that... or we could just add an ECS scheduled task to our existing cluster.

Need an API endpoint to handle inbound Zoom events and forward them to an internal queue? Sure, I can set up a new VPC for that... that'll be a couple of days... or we whip up a Lambda, hook it up to API Gateway, and be up and running in a couple of hours.

AWS helps me do more in less time - and my time is a cost to the business. It's also extremely flexible, and will let us add things far more quickly than we otherwise could.

IMO, the correct comparison isn't "what would it cost to run this platform on Hetzner?" - it's "What would it cost to run it, plus what would cost to acquire the talent to build it, plus retain that talent to maintain it?"

AWS isn't competing with other infrastructure providers. They're competing with other providers and the salaries of the engineers you need to make them work.

I’ve been using ChatGPT Atlas since release on my personal laptop. I very often have it generate a comprehensive summary for YouTube videos, so I don’t have to sit there and watch/scrub a half hour video when a couple of pages of text contains the same content.