They obviously have a plan....
Azure doesn't scale. The load placed on if by redirecting the domains was probably far less than the surge that a suddenly-popular web host might encounter, yet it failed miserably.
Microsoft might not have to pay any monetary damages for the havok they caused, but they might get a hit to their pocketbooks anyway.
People looking to move their operations to the "cloud" would do well to look at this performance, and consider what might happen to *their* traffic...
This is entirely correct. I fire up to 3" shells (licensed), and those things are *heavy* for their size. They'll go right through your little drone without slowing much if at all. And they won't burst early - that requires fusing, not contact. Low bursts are due to faulty internal fuses, not hitting something. Once the shell bursts, the debris is mostly paper and maybe little bits of clay material. Probably not going to bring down a drone big enough to carry a GoPro.
Now, if you're flying a Predator over my show, we might have an issue. But that's what 6" shells are for...:-)
Sigh. I still have my 1st edition copy, slightly worn. It took 4 of us in high school to type in sections of that Star Trek game (110 baud ASR-33, acoustic coupler). But then we played it until they banned the game due to excessive paper use
The book itself was banned in a number of school computer centers (well, the few schools that *had* computers at the time). Including the one at SPC, where a certain kid named Gates learned BASIC (via dial-up). I got mine from the local DEC rep, who swore me to secrecy.
What if there were TWO octocopters, carrying the PS4 on an HDMI cable between them?
And what exactly is the airspeed velocity of an unladen octocopter?
Aren't PS4s migratory anyways?
Expect every rental car to come with this factory-installed. Not only can the company track it's cars, but they can combine the customer's driving pattern with their profile and sell it. Frequent travellers/renters would be an obvious target, but everyone could be included if it's done cheaply enough. And in real-time, too.
That's what you have grad students for...
Not to mention the rumored love triangle...
Link to Original Source
Especially Halo - hard-light stuff everywhere
Do the mothers still get the extra 8 weeks, even though there was no traumatic (and apparently debilitating) childbirth involved?
Or do adoptions just not count (no leave for you....)?
Um, the Seller does *not* get your mailing address.. just Country/State/City/Postal code. Usually (but not always) just enough to figure out the local taxes.
Google does *not* pass on the home address, or CC number.
No - they allow the developer to set one (and only one) sales tax rate to be applied to an entire state. I believe there are only 4 states in the U.S. that have sales tax. But in addition to the base State rate, counties, cities, school districts, fire districts, etc. can all add their own tax on *top* of the State rate. So the price you are charged for a given item can vary by up to several percent depending on your exact location. Walk a block, save 1/2% or more).
The developer is responsible for locating the purchaser's exact tax district, and computing the sales tax at that address. Google doesn't really give enough information to do this properly, because tax districts don't follow zip code boundaries. So sometimes you have to guess, and hope to avoid a prison term for not properly identifying where that $0.02 tax should go.
If you're going to give Google a faze zip, do the small developers a favor and make sure it's a non-sales tax state. Out of state sales are no problem - that's just a straight business tax.
So how do they report that to *you*, the developer? I have to fill out a sales tax report with my B&O taxes - there's no way of saying "Apple paid it - go ask them". Unless you get some sort of official statement tied to your business license, *or* Apple treats you like a 1099.
Yes, the local taxing districts seriously want their money. Each and every one of them (there are around 100 or so in this state). Since this is an Internet transaction, the rate depends on the location of the consumer. If you are buying something at a phyiscal store, they add their local tax into the purchase price right there. Online, it's determined by where *you* live (or rather, where the credit card registered on Google is).
The way Google has set it up, the developer is responsible for sending in the correct tax to the State. Google technically doesn't collect the tax - they just pass it along. The developer has to account for it, and send in the money and itemize where it should apply. That is, I have to record how much I sold to customers in each of those little tax districts, apply their local rate, and add this in with the State's base rate.
It's a real pain for the small developer, but it only applies in some cases. I don't sell apps outside the U.S., because I'd have to calculate and remit VAT in many countries, and that's just too expensive.