It definitely floats. It is really light and rides astonishingly high in the water for something its size. It just gets damaged.
A fairing is 5 Million dollars of mainly carbon composite. If it's a pound heavier, that's a pound you can't have for payload. This gets really important with geosynchronous transfer orbit or (worst) direct geosynchronous, where the capability is much lower than LEO. Adding weight means there will be some missions you can't carry. I guess they could have heavier fairings for when they can afford the weight, but SpaceX likes to have only one assembly line for something if at all possible. There is a complexity cost.
While the ship can be as heavy as you want.
In the end, the net recovery just might not work. We'll see.
Both the Arianne 5 first stage and the Falcon 9 first stage landed in high seas. The Arianne sank to the bottom of the ocean to become an interesting reef for fish, as is their usual procedure. The Falcon 9 landed on a barge and will probably be reused. Yesterday's Falcon 9 recovery was pretty "hot" due to its lifting the heaviest satellite (other than space stations) there is to a substationary orbit, and it's not clear there is a 10-flight life in that booster without refurbishment. I've not yeard about the expected life of the booster in today's mission, but I'd assume 10 without refurbishment.
I know. I am trying to clean up the issues in ham radio and the open source world. I do hope people are out there in the gaming world making it clear that the entire mysogynist and incel thing is an illness and that they are not victims of some women's conspiracy.
Hey, I'm really interested in new laptops, especially powerful, light ones with great battery duration. But I don't really fit in this crowd. I won't ever run "Fortnite" or indeed any video game on it. I will develop software for space satellites, I will write and deliver speeches, maybe I'll produce some videos.
Right now I own a whole fleet of Panasonic Toughbooks of different vintages, up to the Core i7 tablet with removable keyboard, because I can drop them and have them keep working, and it is actually specified to stand being hosed off from any angle. All were purchased used.
I don't want an ultra light thin phone. I just put them in a Unicorn Beetle case as soon as I get them, and they aren't thin after that. I want one with a battery door. This is difficult to get in a good phone these days. Similarly, I want to be able to replace the laptop battery and disk.
Microsoft could solve the problem of "Legacy Windows" in one fell swoop by labeling this "Windows 11" and going on with IoT or whatever they're after today. Unfortunately, Elon Musk doesn't run Microsoft, and there isn't another manager that daring in the corporate universe.
Musk will not need to bail out Tesla. Tesla is past that point. They make good solar systems, battery packs, and cars, and there is high demand for each.
However, if he felt like selling some private stock in SpaceX, he would only be able to sell it to accredited investors. People who have millions to play with. Selling to plain folks takes a lot more regulation. And in general accredited investors place realistic values on things. They're not the folks bidding up bitcoin, etc.
Some of the work I do is painful, like arguing over Open Source licensing so that it will continue to be fair for everyone. So, it's nice to hear from people who say I've helped them. I think about them when it gets difficult. Thanks!
Someone else wrote that book. I was the series editor, which was mostly setting policy, doing PR, and looking over book proposals. That was the first Open Publication book series, and preceded Creative Commons.
If you learned a language from a book, you can learn another 30. Time to push yourself. Right now, I really like Crystal. It might become as big as Rails at its peak, eventually. And there is no certification in it yet.
There is an expanding Open Source Space community. You can meet them at the upcoming Open Source Cubesat Workshop. This is actually an interesting precedent for us, because satellites and various space technologies are also "munitions" under ITAR or EAR, both laws have a carve-out for Open Source, and here it has been tested.
Second-amendment issues are out-of-scope for most space research organizations, so nothing said about that.
Nobody is saying that PHP is a nice language. The point of it was that it allowed less-skilled web designers to write software for web presentation. People who never learned the fundamental concepts of computer security. The security problems were a natural result.
We have much better languages today, and I sure help people use them. But I can't make them do so.
It also prevents ridiculous incompetence like hard-coded passwords in production releases.
So true. Most people write better when the world is looking over their shoulder. I'd like to put a certain politician on C-span for all of his waking hours. It would work a lot better than simply reading the brain-farts he emits on twitter and in press conferences.
I have been scandalized, in general, to read commercial embedded systems code. Getting them to actually understand security has been an uphill battle, and surprisingly remains one today.
Similarly having some source code to audit is great but it's meaningless if the company doesn't actually utilize that exact code or finds some sneaky way to circumvent it.
Good point. You need assurance that the code in the device is the code that you see.
This is a way big problem for government. There are many integrated circuits in our fighter jets, etc. How do we assure that what is inside them is what we think? Thus, we have defense assurance programs that follow the production of a chip from design all of the way to the finished product. But these are a poor substitute for having a technical method to verify that the chip actually does what the manufacturer says it does, and nothing more. Nobody's figured out how to do that.
Sure, what you do is what you can do, for due diligence, if you are using proprietary software. But you are of course putting trust in those auditors. And they are a for-profit business, and it's in their interest to do a good-enough job while not spending too much time.
One of the things they do (and most consulting companies bigger than one person do, including law firms) is sell highly-qualified people, and then have lower-qualified people actually do the work, under the "supervision" of the more qualified ones. But ultimately you get less-qualified eyes, and although the quality of the final report will be high, they can and do miss things.
Like the Volkswagen scandal, it takes serendipity to find the problem - the lab was doing some other experiment and just couldn't get their results to fit the emissions figures of the vehicle. Open Source is designed to facilitate that sort of serendipitous activity.
you don't need the source code to verify vehicle emission output, this is why we test the vehicles
You're missing the fact that the code was made to game the test, and changed emission parameters when the vehicle was on a dynamometer, which is the way emissions tests are done. It was found by a little university lab doing an unrelated experiment, that happened to instrument the vehicle while it was in motion, and simply couldn't get their results to agree with the published emission figures.
We've mostly won this battle in the industry. You can't really not use Open Source in your IT department any longer. And IT managers who insist on avoiding it, rather than learn about it, don't get ahead.
If you are thinking of bugs like Heartbleed, there are also economic issues. OpenSSL was issued under a gift-style license. Big companies that were making billions on desktop software used it, and almost never returned either work or money to the project. This one guy, Ben, had most of the load out of his personal time.
Now, this is not something the OpenSSL guys might ever have considered, and I am not representing them. But what if OpenSSL had been dual-licensed? All the Free Software folks would have had it for free, and all of the commercial folks would have had to pay a reasonable fee. In fact everybody would be paying something, either by making more great Free Software or by paying money. There might have been fewer commercial users, but there might also have been an income stream for Ben or other developers, and they might have been able to devote more time to finding bugs. So, there might never have been a Heartbleed.
Slashdot Mirror
It definitely floats. It is really light and rides astonishingly high in the water for something its size. It just gets damaged.
A fairing is 5 Million dollars of mainly carbon composite. If it's a pound heavier, that's a pound you can't have for payload. This gets really important with geosynchronous transfer orbit or (worst) direct geosynchronous, where the capability is much lower than LEO. Adding weight means there will be some missions you can't carry. I guess they could have heavier fairings for when they can afford the weight, but SpaceX likes to have only one assembly line for something if at all possible. There is a complexity cost.
While the ship can be as heavy as you want.
In the end, the net recovery just might not work. We'll see.
Boostback is optional. Yesterday there was only enough fuel for retro and landing burn, and the re-entry was ballistic.
Falcon 9 block 5 can lift 25 tons to LEO with recovery. Block 4 could only do that if expended.
The fairing has a steerable parachute. It's as big as a bus. They didn't manage to get the ship under it, but "they saw it come down".
Both the Arianne 5 first stage and the Falcon 9 first stage landed in high seas. The Arianne sank to the bottom of the ocean to become an interesting reef for fish, as is their usual procedure. The Falcon 9 landed on a barge and will probably be reused. Yesterday's Falcon 9 recovery was pretty "hot" due to its lifting the heaviest satellite (other than space stations) there is to a substationary orbit, and it's not clear there is a 10-flight life in that booster without refurbishment. I've not yeard about the expected life of the booster in today's mission, but I'd assume 10 without refurbishment.
I know. I am trying to clean up the issues in ham radio and the open source world. I do hope people are out there in the gaming world making it clear that the entire mysogynist and incel thing is an illness and that they are not victims of some women's conspiracy.
It doesn't matter that I can get a cheap chromebook for $200 if it happens to fail 5 minutes before a speech.
Yeah, they are very involved in harassing women online, socializing with other incels, and failing to understand sarcasm on Slashdot.
Hey, I'm really interested in new laptops, especially powerful, light ones with great battery duration. But I don't really fit in this crowd. I won't ever run "Fortnite" or indeed any video game on it. I will develop software for space satellites, I will write and deliver speeches, maybe I'll produce some videos.
Right now I own a whole fleet of Panasonic Toughbooks of different vintages, up to the Core i7 tablet with removable keyboard, because I can drop them and have them keep working, and it is actually specified to stand being hosed off from any angle. All were purchased used.
I don't want an ultra light thin phone. I just put them in a Unicorn Beetle case as soon as I get them, and they aren't thin after that. I want one with a battery door. This is difficult to get in a good phone these days. Similarly, I want to be able to replace the laptop battery and disk.
Microsoft could solve the problem of "Legacy Windows" in one fell swoop by labeling this "Windows 11" and going on with IoT or whatever they're after today. Unfortunately, Elon Musk doesn't run Microsoft, and there isn't another manager that daring in the corporate universe.
Fortunately for them, there's more than one way to do it!
I'm 60, and yeah, health things creep up on you. We'll lose the first generation of Free Software / Open Source folks soon.
Musk will not need to bail out Tesla. Tesla is past that point. They make good solar systems, battery packs, and cars, and there is high demand for each.
However, if he felt like selling some private stock in SpaceX, he would only be able to sell it to accredited investors. People who have millions to play with. Selling to plain folks takes a lot more regulation. And in general accredited investors place realistic values on things. They're not the folks bidding up bitcoin, etc.
:-)
Some of the work I do is painful, like arguing over Open Source licensing so that it will continue to be fair for everyone. So, it's nice to hear from people who say I've helped them. I think about them when it gets difficult. Thanks!
Someone else wrote that book. I was the series editor, which was mostly setting policy, doing PR, and looking over book proposals. That was the first Open Publication book series, and preceded Creative Commons.
If you learned a language from a book, you can learn another 30. Time to push yourself. Right now, I really like Crystal. It might become as big as Rails at its peak, eventually. And there is no certification in it yet.
That would be funny, if :CueCat was a munition.
There is an expanding Open Source Space community. You can meet them at the upcoming Open Source Cubesat Workshop. This is actually an interesting precedent for us, because satellites and various space technologies are also "munitions" under ITAR or EAR, both laws have a carve-out for Open Source, and here it has been tested.
Second-amendment issues are out-of-scope for most space research organizations, so nothing said about that.
Nobody is saying that PHP is a nice language. The point of it was that it allowed less-skilled web designers to write software for web presentation. People who never learned the fundamental concepts of computer security. The security problems were a natural result.
We have much better languages today, and I sure help people use them. But I can't make them do so.
Me? Well, there's this long discussion with the Lucky web platform developer the other day. And they just closed a bug I reported in Mailman. That sort of thing goes on all of the time.
So true. Most people write better when the world is looking over their shoulder. I'd like to put a certain politician on C-span for all of his waking hours. It would work a lot better than simply reading the brain-farts he emits on twitter and in press conferences.
I have been scandalized, in general, to read commercial embedded systems code. Getting them to actually understand security has been an uphill battle, and surprisingly remains one today.
Good point. You need assurance that the code in the device is the code that you see.
This is a way big problem for government. There are many integrated circuits in our fighter jets, etc. How do we assure that what is inside them is what we think? Thus, we have defense assurance programs that follow the production of a chip from design all of the way to the finished product. But these are a poor substitute for having a technical method to verify that the chip actually does what the manufacturer says it does, and nothing more. Nobody's figured out how to do that.
Sure, what you do is what you can do, for due diligence, if you are using proprietary software. But you are of course putting trust in those auditors. And they are a for-profit business, and it's in their interest to do a good-enough job while not spending too much time.
One of the things they do (and most consulting companies bigger than one person do, including law firms) is sell highly-qualified people, and then have lower-qualified people actually do the work, under the "supervision" of the more qualified ones. But ultimately you get less-qualified eyes, and although the quality of the final report will be high, they can and do miss things.
Like the Volkswagen scandal, it takes serendipity to find the problem - the lab was doing some other experiment and just couldn't get their results to fit the emissions figures of the vehicle. Open Source is designed to facilitate that sort of serendipitous activity.
You're missing the fact that the code was made to game the test, and changed emission parameters when the vehicle was on a dynamometer, which is the way emissions tests are done. It was found by a little university lab doing an unrelated experiment, that happened to instrument the vehicle while it was in motion, and simply couldn't get their results to agree with the published emission figures.
We've mostly won this battle in the industry. You can't really not use Open Source in your IT department any longer. And IT managers who insist on avoiding it, rather than learn about it, don't get ahead.
If you are thinking of bugs like Heartbleed, there are also economic issues. OpenSSL was issued under a gift-style license. Big companies that were making billions on desktop software used it, and almost never returned either work or money to the project. This one guy, Ben, had most of the load out of his personal time.
Now, this is not something the OpenSSL guys might ever have considered, and I am not representing them. But what if OpenSSL had been dual-licensed? All the Free Software folks would have had it for free, and all of the commercial folks would have had to pay a reasonable fee. In fact everybody would be paying something, either by making more great Free Software or by paying money. There might have been fewer commercial users, but there might also have been an income stream for Ben or other developers, and they might have been able to devote more time to finding bugs. So, there might never have been a Heartbleed.