Comment Ah shucks! (Score 1) 67
And I was hoping to rip the disk to MP3. Darn it, Universal!
One good anachronistic music format deserves another, I always say!
And I was hoping to rip the disk to MP3. Darn it, Universal!
One good anachronistic music format deserves another, I always say!
The question isn't 'are they number 1' or 'are they number 2' but 'did they sell enough hardware and software, or otherwise benefit from having the brand, to make it worth their while?'
After all, you mention the Wii, but a lot of people who bought a Wii never bought a game past Wii Sports. Many people bought PS3s to be Blu-Ray players, just like many people bought a PS2 to be a DVD player.
ED: Looks like it's 24(!) hives per beehome, and they charge $2k delivery ($83/hive) plus $400/mo ($400/hive/yr) for maintenance.
Clearly not something of use to amateurs, and I'm not sure whether you can make that economics work out for professionals, either. I guess it depends on how truly independent it is, vs. your local labour costs.
There is little correlation between "presence or absence of pollution" (what a general term to begin with...) and CCD. There is a strong correlation with the presence / absence of varroa. And this system treats varroa.
I've been thinking about getting into beekeeping (I first need to increase the accessibility of my ravine where they'd be), and had been thinking about a sort of high tech solution, with electric blankets, heat-exchanging baffles, a flow hive, and maybe some mass and/or noise sensors for monitoring colony health. But this is WAY more high-tech than I envisioned, and honestly I'm scared to even look up the price
The best correlation between the presence and absence of CCD is varroa. CCD is probably not single cause, but if you had to pick only one, varroa is that one.
And glyphosate is probably WAY down on the list. At least pick an insecticide as your culprit.
Not with far-UV (~222nm) you didn't.
Leaders aren't there out there e.g. building the rockets or doing the vast majority of the engineering. Musk doesn't get credit for that. But they do set the culture and direction for their companies. And in this regard, the "build quickly, launch quickly, fail quickly, learn quickly, and iterate quickly" culture developed for SpaceX happens to be very effective. Musk gets credit for instilling that. Another thing he should get credit for is the broad design strokes such as "focus on designs that are cheap enough that they can be mass produced, gaining you economies of scale and the ability to iterate quickly during testing, but are still capable of being reused" (this differs from the two previous predominant paradigms, either super-expensive low-volume reusables, or cheap high-volume disposables).
I don't like the guy, but absolutely, credit where it's due.
Except that Musk is allowed to show up at work or not whenever he feels like it, so he's a giant hypocrite who forces everyone else to do that which he himself is not willing to do.
I think a lot of people miss the fact that SpaceX engineers know very well that what they're doing might fail spectacularly, and that this is the cost of speed.
A random example: autogenous pressurization.
It's beneficial to have a rocket's engines pressurize the tanks themselves rather than to haul up pressurant tanks and a separate pressurant. But it's surprisingly tricky. For a methalox rocket, you ideally want hot methane injected into the methane tank, and hot oxygen into the oxygen tank. But hot oxygen is very difficult to work with in an engine, as it tends to eat your engine.
If you're still working on reliably producing hot oxygen, there is a hack available to you, but it's not pretty: just inject exhaust into the oxygen tank; after all, it's not combustible. BUT, it is water and carbon dioxide. Both can settle out as frosts or plated ices, and in the liquid, the water ice will float at the top, while the CO2 will form a snow at the bottom. Frosts / ice plating can block e.g. your RCS jets. The CO2 snow will kill your engines. You can put in filters around their intakes, but it'll clog your filters. You might try expanding the filters, and maybe that'll work for a while, but then you rotate the rocket, the snow rushes ti one side, and a bunch of engines die from clogging. You may put some big mesh plates across the whole tank to keep the snow off the bottom, but they can cause their own problems with fluid flow and still sometimes clog or let snow through during maneuvers. Etc.
So then comes the question: put Starship on hold while working on getting the engines to reliably produce hot oxygen, potentially for years, or forge ahead with a hack solution that you know has a reasonable chance of killing your rocket?
To SpaceX, the question is obvious. You cannot afford to give up years of critical flight data just to avoid some booms. The decision is immensely lopsided in favour of "put in the hack solutions and launch, while you work on the proper solutions". Because you learn SO much from every launch that can be used to evolve your design. And you also learn so much from every rocket that you build, whether you launch it or not, so you might as well launch it.
To be clear, you don't want to lose rockets due to doing stupid things. Like, for example, if it turns out that some SpaceX engineer installed the wrong COPV and caused the recent pad explosion**, basically the only thing they would learn from that is "have tighter controls on your COPV processes", which isn't at all worth the cost of the explosion. But in general, if you launch and it clears the pad, you're getting good, important data from it, it's worth it even if it blows up seconds later, and it's on to the next evolved version of the rocket in your production sequence with both production- and flight lessons learned.
** It's clear that the recent explosion was from a COPV failure, but it's unclear why. Some claimed leaks state that a COPV may have been coded to a higher pressure than it actually was during production, so when they scanned it it checked out as being the right tank, but actually was not designed to handle the needed pressures. But I'll wait for official confirmation on this. SpaceX only makes some of their COPVs, usually not the smaller ones - ones that have washed up ashore were made by Luxfer. So this could be a supplier problem, like the strut failure on a 2015 Falcon flight. But again, too early to say.
"What am I missing?"
That the author of this article is an idiot.
Yes, humans went to the moon in the 1960s. It also consumed a huge chunk of the federal budget. Adjusting for inflation by NASA's NNSI inflation index, the entire Lunar program cost $288,1B. If the US were to prioritize a project to the same degree today as then, accounting for GDP growth in inflation-adjusted terms, it would be $702,3B. NASA's annual budget is around $25B.
The cost of access to space today is a tiny fraction of what it used to be, when accounting for inflation. And keeps pushing lower. No, it's not "easy", but it absolutely is being done.
Yeah, I once looked into them and got sticker shock
It makes sense. Clavascidium laciniatum forms a biological soil crust in harsh areas like Joshua Tree. And it's incredibly slow growing. So the rate at which it accumulates UV damage versus the rate at which it can repair itself is super-high. Hence it's been under intense selective pressure to develop good resistance to the ionizing radiation damage caused by UV.
When the British were regularly poaching our waters, we pushed them back incrementally in a series of three "Cod Wars". We didn't just sit there and allow it to happen.
Still wondering about those upload speeds, though.
It's kind of a complex question. It depends on where you are and what plan you currently have.
If you're in a mid-split area (where Comcast is using a larger range of frequencies for upload traffic) and had a plan to take advantage of it - which it sounds like you are - then the new plans actually regress on upload speeds. The old ~1Gbps and ~2Gbps plans had 300Mbps nominal uploads (closer to 360Mbps due to overprovisioning), while all other plans were 150Mbps nominal. The new plans drop this down to 100Mbps nominal for everything except the new ~2Gbps plan, which gets 250Mbps nominal.
Unfortunately, you're facing an either/or proposition. Comcast won't remove the data cap for existing plans, you have to transition to a new plan. But if you do that, then you'll get the new, lower upload speeds. With that said, Comcast isn't forcing anyone to upgrade, so current customers can stay on their legacy plans indefinitely.
Other nations regularly poach in the Georges Bank? That's pretty crazy.
In specifications, Murphy's Law supersedes Ohm's.