I could be wrong, but I think DAB uses DQPSK (which can be thought of as a special version of QAM 4 if you squint a bit) and not anything like the higher QAM constellations because it's deliberately designed for mobile (road, train etc) where you don't have a steady signal, it can vary a lot with motion, so QAM 64 wouldn't really be possible.
Though I did a quick check and apparently DRM+ uses QAM-16, so perhaps my knowledge is far too out of date :S
> so for peak loudness (someone shouting or the loudest spike in music) it can take an extra 50% power to create the upper and lower sidebands
Some people save energy by turning their appliances off at the plug rather than leaving them on standby. Clearly Radio 4 chose to avoid having Brian Blessed on too frequently instead ;)
DAB+ uses EEP (and RS) which was deliberately chosen to give better signal quality all the way to the point of losing reception. Old DAB used UEP which degrades faster, but instead of having no signal, it went to a muddier / warbling kind of sound that characterised early DAB receivers.
And technically while some people do call it MPEG2, it's actually MP2, also known as MPEG-1 Audio Layer 2, an audio codec in the same family as MP3 (MPEG-1 Audio Layer 3).
I imagine that today they'd probably use something like Opus and a fountain code or similar, yes... But you can't expect everyone to replace their radio every 10-15 years ;)
Starship isn't a proven manned transport vessel yet. And Boom was founded in 2014.
If I was to hazard a guess, the BFS concept is 2035 at the earliest, most likely 2040 -- and it'll be at a much smaller scale than previously advertised.
Boom is planning to operate at Mach 1.7 (approx. twice that of current aircraft) with a range of about 4250 nautical miles (4900 miles, 7900 km). Over land they're only going to fly at Mach 1.3 to reduce sonic boom effects.
That's not enough range to do London - Sydney, it's not enough to do Los Angeles to Sydney either, or Los Angeles to Tokyo, it's basically a replacement for trans-Atlantic flights only because even US cross-continental Mach 1.3 is only about 50% faster than a 737 (3h vs. 5h)... It's pretty much geared to the prestige market only.
Under an hour to anywhere on the planet, meanwhile, is absolutely someone would be a premium for -- and they'll do it for most/all long haul flights if it was available.
All markets are finite. But you're thinking too finitely -- remember that there was a proposal to use Starship (BFS?) as a point-to-point method of people transport too (London to Sydney in under 50 minutes I seem to remember).
You also have other services: Starlink is an obvious one they're pursuing now, but there's many other things that they could branch into with no effective competition right now, from harvesting resources such as Helium-3 to Rare Earths (ironic name), to... (thinks for several minutes) banishing people to the Phantom Zone?
But you get what I mean, it's not just about rockets, it's about the things cheap and reliable rocketry enables.
I genuinely worked somewhere that used the term API to mean "a person in India". The same company had someone order me not to use the term "postmortem" as part of the SRE function. I did not stay long after that.
The use of the word "chore" in many users of conventional commits has always riled me. I've always tended to favour the "linux kernel"[0] style of commit subject, which thankfully gets a mention here.
I'd have thought that by now, most would have been swapping to WebAssembly. It's really nicely sandboxed, you expose it to only what you want, and you can compile a lot of languages into a WASM form meaning you're not stuck with only Javascript or similar. Am I naive for thinking that?
I have done extensive research on CDC and it almost never works out because most utilities don't create compressed archives in an "rsyncable" (rsync does CDC) format, I actually saved a lot of storage using restic when I switched my backups of certain things so that files were stored in archives uncompressed, and sorted in a stable order. I know syncthing eventually removed CDC and just went with constant-size block sizes.
Bazel, on the other hand, is completely in control of this, and it makes perfect sense to do this at that point -- and it seems to be a relatively efficient implementation too, really nice to see!
As someone who predominantly writes in Go, cider-v was a massive step backwards compared to cider. I eventually moved entirely over to using vim (with the set of internal plugins for blaze etc) which became so much more useful, but I still missed the features of a proper IDE that cider just excelled at.
I imagine a lot of it came from that push to "use outside world tools more rather than writing our own" which is great in theory, but really felt like a huge leap backwards in terms of convergence.