The problem is, AM generally requires a big ferrite bar antenna, which isn't generally going to fit into a typical smartphone. Also, it's really susceptible to noise from the computer bits that it would be sitting right next to.
I had heard that a valve got stuck, causing the throttle and gymbaling to get out of sync. Now that I see the video, it looks like it was coming down really well until that last moment. It probably wanted to make a final course adjustment, but the rocket bits didn't work the way the computer bits expected them to. It even seemed a bit like the kind of crashes I would get in Gravitar after getting a bit confused.
A larger landing area would have just meant no bits to fall into the water after the kaboom.
The main problem with that is that the walls are relatively very thin. Imagine something the size of a paper towel roll, but made of one thickness of aluminum foil, and some rocks at one end to represent the weight of the engines and remaining fuel. Now drop it from the roof of a building and try to catch it with a net. It's not going to be very round after you do that.
Yes, but they don't have to also be at zero vertical and horizontal velocity when they hit. Both of the past SpaceX landings have landed roughly on target. Their problem has been those velocity vectors in a non-vertical direction.
I hate it when my low-security password is rejected by some ego-driven web site that thinks I should memorize a special password just for them.
I also hate it when a web site locks you out completely, requiring you to contact someone to do a manual reset, for failing your password three times. At work, the "enter my goals for this year for the stupid review" site is like this. It's not like this is something that lets people steal money from me, sheesh! Sure, if it was an online banking, etc. password, but most of the sites that do this don't have any information worth a lock-out with a manual admin reset.
The whole point of lock-outs was to prevent someone from trying hundreds of different passwords with a program, not "I forgot which password I have to use this month, and I fumble-fingered one of my three tries". Even a five minute automatic reset should be more than enough to prevent random automated guessing.
Even worse, do they even do a proper check that it's really you when they do the reset, especially if they have to give you a NEW password to do a reset, because their security policy is even more out of proportion with the kind of data they have?
For those who didn't click on the link, the "HD" in "HD Radio" means "Hybrid Digital", not "high definition", and it was probably intended to be confusing like that. It's about 128Kbps on FM and 40Kbps (presumably mono) on AM. That's the level of data compression that people turn up their noses for in their MP3 player. Okay, so it uses AAC instead of MP3, but that's like saying it's not got as much boiled spinach in it.
And it's proprietary on top of that. Anyone can build an analog AM or FM receiver out of a few electronic parts, but you have to have a computer and a bunch of algorithms to decode this audio slush.
They do not pay the artists or the record companies
"American Society of Composers, Authors and Publishers"
Well, "performers" certainly isn't in there. A publisher seems to be the company that holds the copyrights for the songs, not the record label that actually manufactures the recordings.
Twenty plus years ago, I used to hang out on alt.religion.kibology, where trolling was invented. Someone would post bait (hence the word troll derived from "trolling for newbies") to a newsgroup, adding an "audience" group such as alt.religion.kibology to the newsgroups header line. Stuff like mentioning "Majel Barrett Shatner" on a star-trek group, or intentional misspellings of whatever the group was obsessed with. Then you just sit back and enjoy your popcorn while you watch all the threads from one place. It wasn't even about annoying people as much as it was about what you could get with really pathetic "bait".
Later, cross-group trolling was added, where a message would be posted to two or more groups plus the audience group. If you picked your groups right, they would flame each other quite nicely, and it would be time to get another bag of marshmallows.
But yes, today's meaning of "troll" has shifted to what used to be just plain flames or flame-baiting.
I can sort of see near-UV as well. When I look at a prismatic spectrum, there is a bit of gray after the deep violet. I wouldn't be surprised to find this normal but that most people just don't notice it, since UV reflectivity is what makes "whiter whites" in your laundry.
I also happen to have partial color-blindness (not sure whether prot- or deuter- anomaly, but I can't distinguish some brownish colors), but that's clearly unrelated, since my UV vision is clearly from the rods, not the cones.
I guess the best part would be when they adjust the poverty line up so that they can whine about how many people still live in poverty and we need more money for them, it would also bump up the H1B minimum.
As I understand it, DDT sprayed out in the open (swamps, etc.) is bad. But DDT that doesn't make it to water (spraying it on the walls of a third-world hut) is just fine. But no, we have to react as though just saying its name out loud once will kill a thousand birds.
Right now, smoke from fires (whether wild or due to slash-and-burn agriculture I do not know) in southern Mexico is drifting up through Texas, and expected to last a month or so until rains can put them out. But I guess the smoke qualifies as an "immigrant", so it is probably okay with Obama.
But of course Texas is still expected to maintain air quality by having "ozone action days" and such, even when the problem comes from outside its borders.
The 8085 actually had an undocumented instruction to add a constant value to SP and put the result in DE. But apparently all this was happening roughly at the time the 8088 was coming out, and one of their advertised "advantages" was being able to cross-assemble 8080 code to the 8086, so they memory-holed those instructions. Most 8085 clone cores had them though. And yes, I have also seen the result of trying to compile C for the Z-80, and it isn't pretty.
You should look into the 6809 to see what you get when the instruction set isn't chosen "completely at random". It was really nice, and I even got paid to do it for a few years. The only real trouble I had was feeling like I needed just one more register, but you could always cheat by putting stuff on the stack at the cost of cycles.
Back in the mid '90s, I think everyone was surprised to find that you needed at least a 486DX-25 to emulate the Atari 2600. It was because the 2600 required cycle-accurate timing to emulate it properly. You could, and everyone did, do stuff with the Stella chip (which I call a "1-D" graphics chip) in the middle of a scan line, sometimes abusing its counter registers in interesting ways.
The N64 was a different beast with emulation. I think the biggest problem was needing a lot of RAM to emulate it properly on the Xbox, and I think RAM was also the problem on PSP. But at some level it abstracted the 3-D hardware such that you could usually emulate it with better looking graphics than the original hardware.
And yeah, then there's the sound hardware. That was a big problem for SNES emulators, because there was so much that the sound CPU could do. You either make it work for most cases, or you eat up a lot more CPU time emulating it properly.
A while back I found a Heathkit ET-3400 at a thrift store. I tried writing a simple program for it when I realized that holy shit, the original 6800 doesn't even have the ABX instruction, that was in the 6801/6803 core. I mean, I knew all those other instructions like ADDD and MUL wouldn't be there, but I didn't know ABX would be missing too. And I was doubly annoyed because I had done a lot of 6809 programming so I already knew I was going to miss a lot of things.
And the 6809 was the most superior 8-bit CPU when it came to string processing.
I started on the Z-80 and later had 6809, so I never could find much love for the 6502. But it started a revolution by being designed for high yield, and initially sold for $20 each quantity one when the 6800/8080/Z-80 processors were more like $200 each Q1.
I once got to use an Ohio Scientific Challenger III. It had 3 processors, 6502, 6800, and Z-80, but the people who owned it only ever used the 6502 with a version of Microsoft BASIC. It supported multi-user by having a 48K RAM card for each user at 0000-BFFF. That's one way to get an extra zero page.
The 6809 had a direct page register to select which page was the "zero" page, and the 65816 did as well. Then each independent task could have its own zero page, though you would have to use up entire 256 byte chunks for each task's data area to do that.
And my guess as to why Moto didn't use the 6809 as the basis of the 6811/6812 is because they wanted to use microcode, and it would have been harder because of the post-byte index modes.
And then there was the 68000... apparently the marketing guys back in the day were dead set on only selling thousands of 68000s for full-blown Unix-type systems, and against selling millions of 68000s as an embedded processor. By the time of the Macintosh/Amiga/Atari ST when they finally wised up, it was too late, the IBM PC had already happened.
My piecing together of various legends about IBM choosing the 8088 was that they were interested in the 68008, Motorola didn't want to commit to IBM's deadline, IBM said never mind, then Motorola ended up releasing it by that date after all. And that is how you lose a war that you didn't even know had started. In my opinion, the lack of a large flat address space in the leading architecture set the industry back by ten years.
Slashdot Mirror
The problem is, AM generally requires a big ferrite bar antenna, which isn't generally going to fit into a typical smartphone. Also, it's really susceptible to noise from the computer bits that it would be sitting right next to.
I had heard that a valve got stuck, causing the throttle and gymbaling to get out of sync. Now that I see the video, it looks like it was coming down really well until that last moment. It probably wanted to make a final course adjustment, but the rocket bits didn't work the way the computer bits expected them to. It even seemed a bit like the kind of crashes I would get in Gravitar after getting a bit confused.
A larger landing area would have just meant no bits to fall into the water after the kaboom.
The main problem with that is that the walls are relatively very thin. Imagine something the size of a paper towel roll, but made of one thickness of aluminum foil, and some rocks at one end to represent the weight of the engines and remaining fuel. Now drop it from the roof of a building and try to catch it with a net. It's not going to be very round after you do that.
Yes, but they don't have to also be at zero vertical and horizontal velocity when they hit. Both of the past SpaceX landings have landed roughly on target. Their problem has been those velocity vectors in a non-vertical direction.
I hate it when my low-security password is rejected by some ego-driven web site that thinks I should memorize a special password just for them.
I also hate it when a web site locks you out completely, requiring you to contact someone to do a manual reset, for failing your password three times. At work, the "enter my goals for this year for the stupid review" site is like this. It's not like this is something that lets people steal money from me, sheesh! Sure, if it was an online banking, etc. password, but most of the sites that do this don't have any information worth a lock-out with a manual admin reset.
The whole point of lock-outs was to prevent someone from trying hundreds of different passwords with a program, not "I forgot which password I have to use this month, and I fumble-fingered one of my three tries". Even a five minute automatic reset should be more than enough to prevent random automated guessing.
Even worse, do they even do a proper check that it's really you when they do the reset, especially if they have to give you a NEW password to do a reset, because their security policy is even more out of proportion with the kind of data they have?
To be fair, proper trolling works best on uptight people, and SJW egos are usually wound around themselves really tightly.
For those who didn't click on the link, the "HD" in "HD Radio" means "Hybrid Digital", not "high definition", and it was probably intended to be confusing like that. It's about 128Kbps on FM and 40Kbps (presumably mono) on AM. That's the level of data compression that people turn up their noses for in their MP3 player. Okay, so it uses AAC instead of MP3, but that's like saying it's not got as much boiled spinach in it.
And it's proprietary on top of that. Anyone can build an analog AM or FM receiver out of a few electronic parts, but you have to have a computer and a bunch of algorithms to decode this audio slush.
They do not pay the artists or the record companies
"American Society of Composers, Authors and Publishers"
Well, "performers" certainly isn't in there. A publisher seems to be the company that holds the copyrights for the songs, not the record label that actually manufactures the recordings.
The only good use I can see for it is to put a big bright light behind it, add some lenses, and project it on a wall.
Shouldn't that be a bool... oh crap, IHBT.
And they still won't be able to identify the "I earned $4623.58 a month by searching for shit on Google!" spam.
Back in my day, trolling meant nothing!
Twenty plus years ago, I used to hang out on alt.religion.kibology, where trolling was invented. Someone would post bait (hence the word troll derived from "trolling for newbies") to a newsgroup, adding an "audience" group such as alt.religion.kibology to the newsgroups header line. Stuff like mentioning "Majel Barrett Shatner" on a star-trek group, or intentional misspellings of whatever the group was obsessed with. Then you just sit back and enjoy your popcorn while you watch all the threads from one place. It wasn't even about annoying people as much as it was about what you could get with really pathetic "bait".
Later, cross-group trolling was added, where a message would be posted to two or more groups plus the audience group. If you picked your groups right, they would flame each other quite nicely, and it would be time to get another bag of marshmallows.
But yes, today's meaning of "troll" has shifted to what used to be just plain flames or flame-baiting.
And then if we got another cone, what would it even look like?
I can sort of see near-UV as well. When I look at a prismatic spectrum, there is a bit of gray after the deep violet. I wouldn't be surprised to find this normal but that most people just don't notice it, since UV reflectivity is what makes "whiter whites" in your laundry.
I also happen to have partial color-blindness (not sure whether prot- or deuter- anomaly, but I can't distinguish some brownish colors), but that's clearly unrelated, since my UV vision is clearly from the rods, not the cones.
Congratulations ! The domain DISCO.sucks is available for Registration.
I'm waiting for the .shit domain. Then I can register "is.shit" and sell sub-domains!
I guess the best part would be when they adjust the poverty line up so that they can whine about how many people still live in poverty and we need more money for them, it would also bump up the H1B minimum.
As I understand it, DDT sprayed out in the open (swamps, etc.) is bad. But DDT that doesn't make it to water (spraying it on the walls of a third-world hut) is just fine. But no, we have to react as though just saying its name out loud once will kill a thousand birds.
Right now, smoke from fires (whether wild or due to slash-and-burn agriculture I do not know) in southern Mexico is drifting up through Texas, and expected to last a month or so until rains can put them out. But I guess the smoke qualifies as an "immigrant", so it is probably okay with Obama.
But of course Texas is still expected to maintain air quality by having "ozone action days" and such, even when the problem comes from outside its borders.
The 8085 actually had an undocumented instruction to add a constant value to SP and put the result in DE. But apparently all this was happening roughly at the time the 8088 was coming out, and one of their advertised "advantages" was being able to cross-assemble 8080 code to the 8086, so they memory-holed those instructions. Most 8085 clone cores had them though. And yes, I have also seen the result of trying to compile C for the Z-80, and it isn't pretty.
You should look into the 6809 to see what you get when the instruction set isn't chosen "completely at random". It was really nice, and I even got paid to do it for a few years. The only real trouble I had was feeling like I needed just one more register, but you could always cheat by putting stuff on the stack at the cost of cycles.
Back in the mid '90s, I think everyone was surprised to find that you needed at least a 486DX-25 to emulate the Atari 2600. It was because the 2600 required cycle-accurate timing to emulate it properly. You could, and everyone did, do stuff with the Stella chip (which I call a "1-D" graphics chip) in the middle of a scan line, sometimes abusing its counter registers in interesting ways.
The N64 was a different beast with emulation. I think the biggest problem was needing a lot of RAM to emulate it properly on the Xbox, and I think RAM was also the problem on PSP. But at some level it abstracted the 3-D hardware such that you could usually emulate it with better looking graphics than the original hardware.
And yeah, then there's the sound hardware. That was a big problem for SNES emulators, because there was so much that the sound CPU could do. You either make it work for most cases, or you eat up a lot more CPU time emulating it properly.
A while back I found a Heathkit ET-3400 at a thrift store. I tried writing a simple program for it when I realized that holy shit, the original 6800 doesn't even have the ABX instruction, that was in the 6801/6803 core. I mean, I knew all those other instructions like ADDD and MUL wouldn't be there, but I didn't know ABX would be missing too. And I was doubly annoyed because I had done a lot of 6809 programming so I already knew I was going to miss a lot of things.
And the 6809 was the most superior 8-bit CPU when it came to string processing.
I started on the Z-80 and later had 6809, so I never could find much love for the 6502. But it started a revolution by being designed for high yield, and initially sold for $20 each quantity one when the 6800/8080/Z-80 processors were more like $200 each Q1.
I once got to use an Ohio Scientific Challenger III. It had 3 processors, 6502, 6800, and Z-80, but the people who owned it only ever used the 6502 with a version of Microsoft BASIC. It supported multi-user by having a 48K RAM card for each user at 0000-BFFF. That's one way to get an extra zero page.
The 6809 had a direct page register to select which page was the "zero" page, and the 65816 did as well. Then each independent task could have its own zero page, though you would have to use up entire 256 byte chunks for each task's data area to do that.
It's a 1980's hipsterism. So clearly it's someone getting too senile to use II or 2.
The Vectrex video game system also used the 6809.
And my guess as to why Moto didn't use the 6809 as the basis of the 6811/6812 is because they wanted to use microcode, and it would have been harder because of the post-byte index modes.
And then there was the 68000... apparently the marketing guys back in the day were dead set on only selling thousands of 68000s for full-blown Unix-type systems, and against selling millions of 68000s as an embedded processor. By the time of the Macintosh/Amiga/Atari ST when they finally wised up, it was too late, the IBM PC had already happened.
My piecing together of various legends about IBM choosing the 8088 was that they were interested in the 68008, Motorola didn't want to commit to IBM's deadline, IBM said never mind, then Motorola ended up releasing it by that date after all. And that is how you lose a war that you didn't even know had started. In my opinion, the lack of a large flat address space in the leading architecture set the industry back by ten years.