Snapshots are great, but they assume all your data is on the snapshot. It's harder to roll back if your new version goes ahead and corrupts some database or something on the NAS.
It's even harder to roll back if your data stores are on some multi-clustered beast that wasn't designed to be rolled back.
Of course, you should have caught that in test, right?
These days, whenever someone tries to build something nice people are all "what about the poor?"
Well, what about the poor? Are the poor going on those Moon or Mars missions that/. readers love to think about? No. Are the poor gaming on i7s in their mom's basement while posting on Facebook? Are the poor worrying about how to spend their bitcoins?
Fuck worrying about the poor. They don't worry about you. Most of the poor would steal all your stuff and pawn it.
Maybe that's the secret to CSNs: ramification. Somehow trick the staffers into coming up and exploring new strategies via online corporate games. Like "see what happens when you fire the marketing department", or "the teamsters have gone on strike: now what?"
That would be hilarious, and might even be useful.
Oceanographers are at a loss to explain the lack of plastic floating in our oceans. "Where the fuck did it go?" asked Omar Roberts, head of oceanography at the Skips Institute. "We've thrown shit-tons of plastic into the ocean. Where is it?"
Omar, though, has a theory. "The Kraken ate it. We're feeding the fucking Kraken. Jeeeesus!"
It's odd - I'm not sure if a phone would drive more amazon services. What's their motivation? They already see what I buy, when, and in many cases for whom, but they don't really seem to use that information very effectively.
I see some targeted stuff, but not as much as I would expect given my ridiculously long shopping history. A phone would allow them to know more, but they don't seem to be using the data the have...so the extra data would be pointless.
They're not like google, in that their mobile is not a stalking horse for targeted ads. They're not really like Apple, since they don't really make high-end hardware. Launching a cellphone because you're feeling left out isn't really a great business case. Amazon doesn't really need to control the experience, since you can buy anything on amazon on other platforms.
Maybe they got a good deal on bulk minutes and cheap hardware, and want to pass the savings onto the public?
Well, this is an unfortunate simplification of reality.
Apple has changed processor architectures for various reasons, but the generally accepted reason for moving to the x86 architecture from PowerPC was that IBM was unwilling to continue to invest in a low-power version of the PowerPC line. You can't build a Macbook air with a PowerPC unless you have a lap made of asbestos.
There were other benefits as well, but that was a significant one.
Apple didn't move to x86 because it was popular, Apple moved to x86 because Intel was able to provide them the thermal envelope they wanted.
If you kill enough leaders, you are left with a bunch of bureaucrats. And as everyone knows, bureaucrats don't do much of anything.
So yes, killing leaders works, in the sense that removing people who are able and willing to take risks will eventually cause their organization to atrophy and die.
The main problem with javascript is it's hard to debug. If you can get past that it's a pretty OK language.
The runtimes are so variable that I'd think you'd need to really standardize on one runtime and stick with it forever.
There are times where being able to pass functions around in objects, etc is kind of handy, especially since you can pass them in as json at runtime. Again, that makes debugging really hard. If you persist them you can have objects that look the same with totally different implementations, which can be really confusing.
But as languages go, it's no more horrible than perl.
If you need an easy problem that quickly turns into a nightmare, try writing a program that allows the user to map one set of database/data structure/XML fields to another set of database/data structure/XML fields.
For bonus points the user can use javascript to do the transform, as well as using a nice GUI.
If you really want to freak out, take a look at how much money municipalities pay for police pensions. It's not the administrators that are munching the budget, it's the retirees.
Slashdot Mirror
Snapshots are great, but they assume all your data is on the snapshot. It's harder to roll back if your new version goes ahead and corrupts some database or something on the NAS.
It's even harder to roll back if your data stores are on some multi-clustered beast that wasn't designed to be rolled back.
Of course, you should have caught that in test, right?
old smartphones are to today's smartphones as:
A BMW 7 series is to a model-T ford
GPS is to maps
Color TV vs Stereoscopes
I'd put my iPhone 1 up against a psion any day of the week.
These days, whenever someone tries to build something nice people are all "what about the poor?"
Well, what about the poor? Are the poor going on those Moon or Mars missions that /. readers love to think about? No. Are the poor gaming on i7s in their mom's basement while posting on Facebook? Are the poor worrying about how to spend their bitcoins?
Fuck worrying about the poor. They don't worry about you. Most of the poor would steal all your stuff and pawn it.
Maybe that's the secret to CSNs: ramification. Somehow trick the staffers into coming up and exploring new strategies via online corporate games. Like "see what happens when you fire the marketing department", or "the teamsters have gone on strike: now what?"
That would be hilarious, and might even be useful.
Oceanographers are at a loss to explain the lack of plastic floating in our oceans. "Where the fuck did it go?" asked Omar Roberts, head of oceanography at the Skips Institute. "We've thrown shit-tons of plastic into the ocean. Where is it?"
Omar, though, has a theory. "The Kraken ate it. We're feeding the fucking Kraken. Jeeeesus!"
Taxi medallions are so expensive because medallion owners want them that way. By restricting the medallions, they restrict the competition.
Has this resulted in better service? In NY, ask the people in the outer boroughs if they can get cabs.
I (and they) can do this already with Amazon PriceCheck and the normal Amazon app. Why bother making a whole cellphone just do reinvent the wheel?
It's odd - I'm not sure if a phone would drive more amazon services. What's their motivation? They already see what I buy, when, and in many cases for whom, but they don't really seem to use that information very effectively.
I see some targeted stuff, but not as much as I would expect given my ridiculously long shopping history. A phone would allow them to know more, but they don't seem to be using the data the have...so the extra data would be pointless.
They're not like google, in that their mobile is not a stalking horse for targeted ads. They're not really like Apple, since they don't really make high-end hardware. Launching a cellphone because you're feeling left out isn't really a great business case. Amazon doesn't really need to control the experience, since you can buy anything on amazon on other platforms.
Maybe they got a good deal on bulk minutes and cheap hardware, and want to pass the savings onto the public?
Title 47
http://www.ecfr.gov/cgi-bin/te...
I don't particularly want to understand the FCC's area of authority, so here is Title 47.
If it's stripe data, that implies the POS readers were compromised, just like Target. Interesting.
From what little I understand, the public WiFi stuff is on a separate upstream channel.
It's not using your bandwidth, but it is using bandwidth that Comcast doesn't want to make available to you, which isn't quite the same thing.
Well, this is an unfortunate simplification of reality.
Apple has changed processor architectures for various reasons, but the generally accepted reason for moving to the x86 architecture from PowerPC was that IBM was unwilling to continue to invest in a low-power version of the PowerPC line. You can't build a Macbook air with a PowerPC unless you have a lap made of asbestos.
There were other benefits as well, but that was a significant one.
Apple didn't move to x86 because it was popular, Apple moved to x86 because Intel was able to provide them the thermal envelope they wanted.
The only report I was able to find with real numbers estimated kindle sales at 20.5 million:
http://allthingsd.com/20131212...
"A ton of them" is not how most people represent sales figures.
Just look at Samsung's sales reporting. They lied like crazy about sales.
Amazon has never told anyone how many kindles they've sold. Where did that 40 million number come from?
This has been happening forever. Did the OP just get online recently? What planet is the OP from?
As our limited experiences with radiation has shown, you don't get:
* monsters
* superpowers
* aliens
You just get dead, mostly. Then after that, not much.
Turn a bureaucrat into a leader? That's like turning a software developer into a manager.
If you kill enough leaders, you are left with a bunch of bureaucrats. And as everyone knows, bureaucrats don't do much of anything.
So yes, killing leaders works, in the sense that removing people who are able and willing to take risks will eventually cause their organization to atrophy and die.
"Because the university ran nightly backups, they were able to restore all the PCs to the correct state later that afternoon."
If they had a centralized SCCM server, they should have a central backup server as well.
The main problem with javascript is it's hard to debug. If you can get past that it's a pretty OK language.
The runtimes are so variable that I'd think you'd need to really standardize on one runtime and stick with it forever.
There are times where being able to pass functions around in objects, etc is kind of handy, especially since you can pass them in as json at runtime. Again, that makes debugging really hard. If you persist them you can have objects that look the same with totally different implementations, which can be really confusing.
But as languages go, it's no more horrible than perl.
My guess is that the amount of space this takes is comparable to a couple of full-sized pngs that the graphics guy forgot to scale down.
Some memories get stronger the more they're accessed, not weaker.
That doesn't imply that the details are more or less accurate - just that by remembering something over and over you makes it easier to remember.
If you need an easy problem that quickly turns into a nightmare, try writing a program that allows the user to map one set of database/data structure/XML fields to another set of database/data structure/XML fields.
For bonus points the user can use javascript to do the transform, as well as using a nice GUI.
If you really want to freak out, take a look at how much money municipalities pay for police pensions. It's not the administrators that are munching the budget, it's the retirees.