It's sortof strange that THX 1138:4EB (note the colon, sir) would be included on the registry when his actual feature film version of THX 1138 was declined. The second was much longer and had an actual plot; the original film school version was rather plotless and hard to follow, and as an avant-garde art film there are much more interesting works from that period-- Lucas was just one voice in a chorus of experimental filmmakers from that period. On the other hand, the web informs me that Jonas Mekas's Reminiscences of a Journey to Lithuania and Andy Warhol's Empire are both on the register as well, so I guess this vaguely in line. I had to watch the film when I went to USC for film in the 90s, and at the time it seemed really out-there but nothing terribly special, a very dated piece of the 60s counterculture.
What people don't always realize is that Lucas got much of the funding for the student THX from the US Navy and used primarily US Navy personnel as extras -- he was in USC as a grad student as wad TA'ing a class in documentary filmmaking that the navy was sending enlisted men into, and he drafted them and somehow got the documentary lab fees to pay the expenses. After he graduated he got out of the draft 4F (this was how he got diagnosed with diabetes), and his contacts got him a job with the US Information Agency as an editor for pro-ARVN propaganda films (Marcia was another editor there and that's how they met). Most people attribute Lucas's fascination with technology and military subjects to his work on these years.
And "Apollo" didn't start at 13, 13 was the only movie made about the Apollo program, and it was about the most suspenseful spaceflight that ever launched anywhere.
I suspect a lot of people, maybe not Dykstra, would point to the failure of Lisps to take hold in the marketplace as evidence that Basic has corrupted minds.
Are you saying you can actually read an 8.5" by 11" PDF originally intended for printing on a 4" screen without panning and zooming? That's what I use mine for, I have to read screenplays and the Kindle just never cut it. Works great for manuals too; I just can't see how you could get a page of that legible on a small screen.
While were making up scenarios, why don't we just find a very profitable company that buys us all ponies to complement our phones, too?
There's a bunch of questions to be answered -- does MobileMe have a halo effect on other devices, like the phones? Could it ever? If you can find a way of answering this yes, then you're on to something. Then, you have to figure out if you have enough capacity to service accounts that have zero cost at the point of delivery -- Google does, but Apple doesn't. A low price per month defrays costs but also keeps the demands on the system low. We might see this side of the equation change when this new datacenter opens. If Apple decides it can service all of the customers they presume they'd get for free with this new capacity, and the service will pay for itself in sales, then they're likely to consider doing it. But those factors have to be in place. They can't just offer it today, get swamped for 6 months, cost them a load of money and then have the offer die an ignominious death from getting a bad reputation.
MobileMe is "expensive" (by which we mean $99 a year) precisely because it has no ads and doesn't vend your personal information to third parties. You can't have it both ways-- you either go Google and get your cloud for free with ads and metrics, or you actually pay money for your service.
For those that don't have access to a walk-in oven, the NuWave-style dehydration convection ovens are generally preferred, not least because they're exactly the right size for a 2-inch tape roll. That's what we used for old music tracking masters anyways.
I agree with this to an extent. I went to an elite program at a semi-elite university on a scholarship (USC Film School). I learned a bit, but I also met several influential people and people who were well-positioned to become the next generation of leaders, and when I got out I had no trouble getting work through contacts.
I learnered a lot as well, but if someone asks me how they can learn about production, I tell them to volunteer at the local public access station -- this is how I got started, and no, shooting YouTube videos by yourself doesnt count. If they don't just want to learn but want to have a lucrative career in production, then you have to get out and meet people by any means necessary.
I think you've defined the cloud in such a way that you'll never find it.
1. Distributed - not tied to one provider, but fully abstracted
We've had FTP forever. I think what makes the cloud the Cloud is the service organization that supports it -- the people at the other end of the phone or chat when you have a problem. Customer service is made by providers, and is sortof tied by definition to a vendor.
It used to be you'd call your University or corp IT department when you had a computer problem. The "Cloud" is just an outsourcing of these calls -- that what The Cloud is, it has nothing to do with protocols or servers. It's about commoditizing IT support, and finding clever new ways of paying for it.
2. Encrypted - so that I, and only I can get the data out
The problem with this is, except for a few research projects, it's impossible to keep something encrypted while allowing the "vendor" side to do local processing of it. You can't keep it in a database properly, you can't search it or access semantically-meaningful "parts" of a document, etc... A big part of the fun of having a bunch of EC2 instances is being able to crunch through data much faster than your private machine can. The only price is Amazon gets the results of the computation before you, and all you have is their pinky-swear that they don't use it for their own purposes.
3. Universal - So that I can log into any compatible networked computer anywhere in the world and have my desktop and apps right there
You had this before the Cloud, this always comes down to execution or followthrough on a particular platform. And network connectivity is a service, that's generally going to be tied to a particular vendor.
4. Free - As in price and freedom
Really? Like you pay these people nothing and expect them to hold your bytes? Without paying money there's no contract created to hold the data, and if your data is encrypted the advertising revenue will be terrible!
I think what we might need is a modern digital equivalent of a Bill of Lading.
or maybe we shouldn't entrust anyone with any of our personal information because of what they _could_ do with it.
Human society has used this principle for thousands of years and everything has been just fine -- if you wanted to do business with someone for the last 5000 years you handed them coins, or a document telling them where they could obtain coins and giving your banker permission to disburse them. The biggest innovation before 2000 was you handed them a credit account number, and all that did was replace the old credit accounts merchants used to keep themselves.
But we're not talking about money here, we're talking about your documents and correspondence and personal effects, things that go to the heart of your existence as an individual. If you give someone else your personal information, it isn't personal anymore. They might have some process whereby you're the only one that sees it, but it's just a matter of corporate policy, on some paragraph in a huge TOS that they change constantly. So basically, imagine the privacy of your documents being controlled by the same sort of legal document you get from your credit card company every 6 months.
And while possession isn't 9/10s of the law, in practice it turns what would otherwise be an issue of constitutional rights into a question of lawsuits. And when suing the party with the bigger legal budget has absolute advantage.
CC are evil. I and almost everyone here use a debit card, which requires a PIN to be inserted each time. Even if they could copy the card, they couldn't use it.
In the US the laws controlling how a bank resolves disputes over credit card transactions are significantly stronger (the bank can't charge you interest if it was fraud, and must do an investigation that can't last longer than 10 days) than if someone commits fraud with a debit card, where most banks have a "voluntary" 10 day investigation process and where they may or may not credit you the balance of the fraud provisionally, and in the case of a debit card the fraud has deprived you of hard money, instead of debt, which can significantly screw you if you have tight cash flow.
I have one debit card because my bank refuses to give me a straight ATM-only card. It is never used for any purchase ever.
These tactics are plausible, even childishly simple, and were effective. I don't know, from the perspective of a black hat, what "legitimate" means here.
INTERPOL does not assess the guilt or innocence of the subject of a wanted notice, or even test it for probable cause or whatever. They just repeat what the state party tells them. Take your hate out on the Swedes.
Just because nuclear weapons are invented it doesn't naturally follow that kids should practice hiding under their desk every month. This was about making people feel comfortable with the idea of war, and giving them a way of telling themselves that a nuclear exchange was conscionable, because if they knew the complete truth of the force of the weapons, they might have never supported the Cold War.
It was a way of giving people a thread of hope where none existed, and in that way it was wrong. If the Cold War had to be fought, better to fight it with the people being clear of the risks, and not by generals who talked in megadeaths and "acceptable losses."
I don't know, I never really put much thought into branch policy, namely, what exactly does the "master" branch do and is it necessarily always a safe place to base new revisions? Practice seems to vary.
Also this seems to bring into question how you recognize "good" commits in the system versus "in progress" ones. If I were adding a new feature to source in a repository, would I necessarily start from a release tag, and then merge commits from master since then to get everything that changed since the release? Or do I not merge any commits subsequent to the release tag, or is there a branch in the tree the maintainers keep for known-good bases for new branches?
Some of this could be cured with continuous integration, where you put hooks into your SCM to run unit tests on your tree before it commits, and the SCM will refuse the commit if they fail (you would only apply this policy on certain branches or repositories).
Slashdot Mirror
"Why don't you just buy a faster horse?" the carriagemaker asked Mr. Daimler.
Logic: We need enhanced 911 service and reliable telephony during power outages, therefore block connections to skype.com on port 80.
This thread was about movies. It had nothing to do with space exploration per se.
It's sortof strange that THX 1138:4EB (note the colon, sir) would be included on the registry when his actual feature film version of THX 1138 was declined. The second was much longer and had an actual plot; the original film school version was rather plotless and hard to follow, and as an avant-garde art film there are much more interesting works from that period-- Lucas was just one voice in a chorus of experimental filmmakers from that period. On the other hand, the web informs me that Jonas Mekas's Reminiscences of a Journey to Lithuania and Andy Warhol's Empire are both on the register as well, so I guess this vaguely in line. I had to watch the film when I went to USC for film in the 90s, and at the time it seemed really out-there but nothing terribly special, a very dated piece of the 60s counterculture.
What people don't always realize is that Lucas got much of the funding for the student THX from the US Navy and used primarily US Navy personnel as extras -- he was in USC as a grad student as wad TA'ing a class in documentary filmmaking that the navy was sending enlisted men into, and he drafted them and somehow got the documentary lab fees to pay the expenses. After he graduated he got out of the draft 4F (this was how he got diagnosed with diabetes), and his contacts got him a job with the US Information Agency as an editor for pro-ARVN propaganda films (Marcia was another editor there and that's how they met). Most people attribute Lucas's fascination with technology and military subjects to his work on these years.
Sigh. Nobody talks about The Right Stuff anymore.
You forgot Leonard starting at part 6.
I suspect a lot of people, maybe not Dykstra, would point to the failure of Lisps to take hold in the marketplace as evidence that Basic has corrupted minds.
What's chalk?
Are you saying you can actually read an 8.5" by 11" PDF originally intended for printing on a 4" screen without panning and zooming? That's what I use mine for, I have to read screenplays and the Kindle just never cut it. Works great for manuals too; I just can't see how you could get a page of that legible on a small screen.
While were making up scenarios, why don't we just find a very profitable company that buys us all ponies to complement our phones, too?
There's a bunch of questions to be answered -- does MobileMe have a halo effect on other devices, like the phones? Could it ever? If you can find a way of answering this yes, then you're on to something. Then, you have to figure out if you have enough capacity to service accounts that have zero cost at the point of delivery -- Google does, but Apple doesn't. A low price per month defrays costs but also keeps the demands on the system low. We might see this side of the equation change when this new datacenter opens. If Apple decides it can service all of the customers they presume they'd get for free with this new capacity, and the service will pay for itself in sales, then they're likely to consider doing it. But those factors have to be in place. They can't just offer it today, get swamped for 6 months, cost them a load of money and then have the offer die an ignominious death from getting a bad reputation.
MobileMe is "expensive" (by which we mean $99 a year) precisely because it has no ads and doesn't vend your personal information to third parties. You can't have it both ways-- you either go Google and get your cloud for free with ads and metrics, or you actually pay money for your service.
For those that don't have access to a walk-in oven, the NuWave-style dehydration convection ovens are generally preferred, not least because they're exactly the right size for a 2-inch tape roll. That's what we used for old music tracking masters anyways.
I agree with this to an extent. I went to an elite program at a semi-elite university on a scholarship (USC Film School). I learned a bit, but I also met several influential people and people who were well-positioned to become the next generation of leaders, and when I got out I had no trouble getting work through contacts.
I learnered a lot as well, but if someone asks me how they can learn about production, I tell them to volunteer at the local public access station -- this is how I got started, and no, shooting YouTube videos by yourself doesnt count. If they don't just want to learn but want to have a lucrative career in production, then you have to get out and meet people by any means necessary.
I think you've defined the cloud in such a way that you'll never find it.
1. Distributed - not tied to one provider, but fully abstracted
We've had FTP forever. I think what makes the cloud the Cloud is the service organization that supports it -- the people at the other end of the phone or chat when you have a problem. Customer service is made by providers, and is sortof tied by definition to a vendor.
It used to be you'd call your University or corp IT department when you had a computer problem. The "Cloud" is just an outsourcing of these calls -- that what The Cloud is, it has nothing to do with protocols or servers. It's about commoditizing IT support, and finding clever new ways of paying for it.
2. Encrypted - so that I, and only I can get the data out
The problem with this is, except for a few research projects, it's impossible to keep something encrypted while allowing the "vendor" side to do local processing of it. You can't keep it in a database properly, you can't search it or access semantically-meaningful "parts" of a document, etc... A big part of the fun of having a bunch of EC2 instances is being able to crunch through data much faster than your private machine can. The only price is Amazon gets the results of the computation before you, and all you have is their pinky-swear that they don't use it for their own purposes.
3. Universal - So that I can log into any compatible networked computer anywhere in the world and have my desktop and apps right there
You had this before the Cloud, this always comes down to execution or followthrough on a particular platform. And network connectivity is a service, that's generally going to be tied to a particular vendor.
4. Free - As in price and freedom
Really? Like you pay these people nothing and expect them to hold your bytes? Without paying money there's no contract created to hold the data, and if your data is encrypted the advertising revenue will be terrible!
I think what we might need is a modern digital equivalent of a Bill of Lading.
Human society has used this principle for thousands of years and everything has been just fine -- if you wanted to do business with someone for the last 5000 years you handed them coins, or a document telling them where they could obtain coins and giving your banker permission to disburse them. The biggest innovation before 2000 was you handed them a credit account number, and all that did was replace the old credit accounts merchants used to keep themselves.
But we're not talking about money here, we're talking about your documents and correspondence and personal effects, things that go to the heart of your existence as an individual. If you give someone else your personal information, it isn't personal anymore. They might have some process whereby you're the only one that sees it, but it's just a matter of corporate policy, on some paragraph in a huge TOS that they change constantly. So basically, imagine the privacy of your documents being controlled by the same sort of legal document you get from your credit card company every 6 months.
And while possession isn't 9/10s of the law, in practice it turns what would otherwise be an issue of constitutional rights into a question of lawsuits. And when suing the party with the bigger legal budget has absolute advantage.
In the US the laws controlling how a bank resolves disputes over credit card transactions are significantly stronger (the bank can't charge you interest if it was fraud, and must do an investigation that can't last longer than 10 days) than if someone commits fraud with a debit card, where most banks have a "voluntary" 10 day investigation process and where they may or may not credit you the balance of the fraud provisionally, and in the case of a debit card the fraud has deprived you of hard money, instead of debt, which can significantly screw you if you have tight cash flow.
I have one debit card because my bank refuses to give me a straight ATM-only card. It is never used for any purchase ever.
Monkeys should really be more careful and should never, ever dive into the shallow end of the pool.
If a supplier offered me a LaserJet 4 in this day and age I probably would just test the roof with it.
These tactics are plausible, even childishly simple, and were effective. I don't know, from the perspective of a black hat, what "legitimate" means here.
You didn't get it on every web browser on Earth. Take it from someone in the entertainment business, an eyeball is worth a 1000 good executions.
Teehee. Smart ass.
INTERPOL does not assess the guilt or innocence of the subject of a wanted notice, or even test it for probable cause or whatever. They just repeat what the state party tells them. Take your hate out on the Swedes.
I don't see where we disagree.
Just because nuclear weapons are invented it doesn't naturally follow that kids should practice hiding under their desk every month. This was about making people feel comfortable with the idea of war, and giving them a way of telling themselves that a nuclear exchange was conscionable, because if they knew the complete truth of the force of the weapons, they might have never supported the Cold War.
It was a way of giving people a thread of hope where none existed, and in that way it was wrong. If the Cold War had to be fought, better to fight it with the people being clear of the risks, and not by generals who talked in megadeaths and "acceptable losses."
I don't know, I never really put much thought into branch policy, namely, what exactly does the "master" branch do and is it necessarily always a safe place to base new revisions? Practice seems to vary.
Also this seems to bring into question how you recognize "good" commits in the system versus "in progress" ones. If I were adding a new feature to source in a repository, would I necessarily start from a release tag, and then merge commits from master since then to get everything that changed since the release? Or do I not merge any commits subsequent to the release tag, or is there a branch in the tree the maintainers keep for known-good bases for new branches?
Some of this could be cured with continuous integration, where you put hooks into your SCM to run unit tests on your tree before it commits, and the SCM will refuse the commit if they fail (you would only apply this policy on certain branches or repositories).
Anyways, slightly enlightening.