One of the big advantages of pallets over boxes or containers is that they are cheap enough that shipping them back isn't something you need to worry about in many cases. Yes, if there's a load (or a regular truck) going back to where they need to be loaded it's often better to ship back and re-use, but if they are delivering something and there's no load going back any time soon, they are cheap and easy enough to take apart that they can be discarded and used for other purposes.
Just because we think the suit should continue to it's end doesn't mean we support DRM. Or even that we think the plaintiff should win. There is precedent to be set in this case, and continuing the suit to set it may well be a better outcome then getting it dismissed on a technicality.
'Busy' and 'constructive use of time' are separate concepts. If you just want people to busy to rebel, making them work on non-constructive projects is ideal: You'll never run out, and they'll never be done.
Or that that being employed makes people feel their time is being used in any way constructively.
The second is a fair point: the main problem with coal and other fossil fuels is the external cost exported to society at large. (CO2 and other emissions.) If you could factor in that cost - and make the generators pay it - the cost of electricity from fossil fuels would go way up. (And, if they can afford to pay it - actually clean up their emissions to the point where they aren't harmful to the environment - then we don't actually have a problem with fossil fuels, except for the limited supply.)
Actually, at this point it's exactly a share taxi. I wonder when Americans will realize they've just re-invented a form of semi-formal public transport that's common in undeveloped countries without real public transport.
Ditto; just tested to be sure - my email from my self-hosted domains gets through just fine. This is not a 'Comcast is blocked' problem. This is a 'submitter's IP address is blocked' problem.
I actually think the 'I Robot' movie is anti-Asimov. One of the reasons the 'I Robot' stories are so famous is because Asimov treated robots as machines: They generally work as designed, but break or have flaws in their design that need to be fixed, and can be. They are complex machines, so they have complex flaws, but the flaws are the same types of flaws that you have in other complex machines, and the robots do not become monsters because of those flaws. Robot stories before him (and many after him, and nearly all in Hollywood...) tend to either treat robots as monsters, just waiting to get lose from their creators, or gods, able to fix all problems. The movie 'I Robot' is a prime example of the 'monster' archetype.
(People tend to bring up a couple of later stories he wrote when I bring up this argument - stories where his robots do start to evolve into fitting the god archetype. But: 1 - it's 'evolve', they were machines that were being perfected, not instant fixes, and 2 - they were later stories, where Asimov was subverting expectations about his own writing.)
Depends on which books, and where in his career he was. He got fairly blatant around mid-career, although rarely actually explicit. When they say 'Foundation Series' it's open to interpretation on which books are likely meant - The original three were early in his career, and didn't really have much sex in them. The later two (mid-career) at the end have sex as a major plot driver/enabler, and the two prequels (end-career) feature it without making it a huge point. So it depends somewhat on where they start. I'm betting they'll start with the prequels - they have a strong central character, and can lead into the rest without much issue even after he dies. (And a fair amount of sex if they want it.)
The other point I'd be worried about is violence - the Foundation Series is about the fall of an empire and the rise of a new one, but actual fighting doesn't occur often. There are several places where it looks like it's about to, but then the forces of history make it unnecessary. (Or the populace gets mind-controlled, in one case...) It'd be very tempting for a director of a drama series to ramp up the violence, but it would change a large part of the point of the stories.
Oh, and in response to a couple levels up: They didn't use robots for sex in the stories. They didn't use robots for anything, in fact. There was a complete ban on higher-level AIs and on humanoid machines, to the level of taboo. (Although there were a few characters who where extremely humanoid robots in the prequels and sequels - and were basically the reason for the bans.)
Setting up SPF correctly for your domain does have the side-effect of stopping a lot of bounceback spam (where they forge your address and send it to someone else, so you get the rejection), and can be useful for that reason alone.
But yeah, incoming mail it's not really a big discriminator. Worth looking at slightly, but not really all that useful. (Which means in general it's just more work you'll need to do to set up an email server, which doesn't have much benefit.)
I used both BASIC and HyperCard - they were dramatically different approaches. If you want a modern BASIC, try Perl or Python or Ruby or - you get the picture. There are dozens of suitable replacements; simple direct languages that can write a short command-line program easily.
And you show the result to the average user out there and they won't even think it's a program. If you want a GUI - like everything out there today - you'll have to work on a major lift, some complex API that takes months to master, and days even for an experienced programmer to learn.
HyperCard could get you a simple GUI-based program in minutes, that even a beginner could do. You could actually get quite a ways without writing a single line of 'code' - though you still needed to think about the structure of how you moved through the application. It could even be argued that you can teach that structural thought easier to certain types of learners, as you get a more dramatic and visual result.
But the largest thing for a beginner that HyperCard could offer was a feeling of accomplishment: In a few minutes you had what 'felt' like a real application, with a GUI and everything. It doesn't look like a cliff to get to the point of writing a program that they can show off to their friends - even if it's a simple program.
There are roles for both, but to get someone interested in programming, I think HyperCard is probably better. Once you have that pull out the major arcania of complex API's and huge libraries.
I just had an excellent counter-argument today: Work uses one password to log into their benefits site and into the handheld scanner used on the floor. The handheld scanner has a keyboard of less than 20 keys - numbers are easy, letters are hard, capital letters are really hard, and special characters are impossible. And there's no other input.
My login to my benefits is now controlled by the password I can type into what's basically a telephone keypad. Because that's where I need to type it a couple of times a day.
Because the average human being can actually read it better off of a changing analog-style dial than they can understand a bare number. It has to do with us being well developed at judging distances for throwing and jumping. (And an analog dial allows you to read both off of one instrument.)
The other place analog (or analog-style) gauges shine is when the rate of change is more important than the value. Speedometers and tachometers are good examples: You usually care more if you are speeding up, slowing down, or keeping the same speed than whether you are going 65 or 66mph.
Depends on what PHP is doing. If it makes a call to system(), anywhere... No, you are not. (Assuming you have bash as
If it stays entirely within PHP, then you are. But that'd be a lot of work to double check - You need to check every line of code you run, and the php interpreter itself to see where it calls out.