This helps define some of the challenges with making very very small turbine engines. We have electrical (lithium) powered drones but they are heavy and have low energy density compared to what a liquid fuel + turbine could provide. But could we make a 2 inch diameter turbine engine reliably? Maybe!
>could we make a 2 inch diameter turbine engine reliably
I mean, technically yes, but in practical terms, no - turbines run on the Brayton cycle, where the are under curve efficiency is determined by the peak pressures it can withstand. if you scale down the turbine proportionally, it gets structurally weaker, meaning its efficiency drops. thrust/weight decreases
If you then thickened its walls you would then be able to handle higher pressures, but weight would increase - thrust/weight decreases again.
So the correct answer is if you really wanted to make a small turbine, you could certainly make one, but your design would be less optimal than a bigger one, so unless your goal is to go small, you would make one as big as you can get away with it.
Here’s a breakdown of the networks present, what they mean, and how they relate to the map’s context ...
The first red flags.
Conclusion
The map is a diagram of networks—pipelines, oilfields, terminals, company concessions, and shipping routes—depicting the Middle East’s oil as a vast, interdependent system. These networks are both physical (infrastructure) and abstract (ownership, contracts), making the map a powerful tool for understanding the strategic importance and international entanglement of oil in the mid-20th century. AI analysis.
And now the last paragraph literally says "AI analysis".
> It's not AI slop, it's probably not even AI. You simply are unable to parse the description, or the map, or both.
Tom who is stepping in is an awesome executive. He was OG Pandora and Snap before Quibi and was on the Sonos board. He's a true product person. I'm sure he was enjoying semi-retirement and see him dropping in as CEO is a huge upgrade. :-)
In my experience AirPlay 2 isn’t flawless, pretty much every time I try to use it there are stutters.
This is using an iPhone 16 Pro to AirPlay to a stereo pair of Sonos Five’s that are connected using Ethernet.
AirPlay isn’t a great choice if you are concerned about audio quality anyways - if you’re using AirPlay 2 you’re using 256kbps AAC, so it should sound the same as Bluetooth (or worse if you are comparing something like LDAC).
Buy an older Apple TV, or an Amazon Fire. Connect them to your receiver and you're good to go. Or buy a newer Yamaha or Denon receiver and they'll be ready to go out of the box.
Sonos Amp / Port act as airplay receiver to analog out (with amplifier in the case of Amp). They're meant to act as an input for existing ‘dumb’ speakers/amplifiers/home audio systems, and is extraordinarily fit for that purpose.
How do else could one Airplay to a ‘dumb’ stereo without something to act as an airplay receiver?
AirPlay is as about as good as it gets I think. It’s been thoroughly reverse engineered so there’s lots of open source tools for it and it’s cheap to add speakers since used AirPort Expresses are still supported AirPlay targets.
That makes it easier, but no. Many implementations of both servers and clients (both closed and FOSS) exist, for example AirMusic adds AirPlay casting support to Android and I’ve heard of people using rPi’s as receivers. The protocol is entirely local, there’s no remote server component at all.
Agreed but it has better sync tech than most others that I have tried. Yamaha's is buggy, Denon's buggy, but Apple TVs sync well in my multi level, multi system set up.
reply