Actually, it was tariffs on cars that convinced Japanese auto makers to manufacture cars in the U.S. That employed a lot of people. I agree that it doesn't solve all problems. Eventually better and better automation starts taking over. I look forward to that as long as we implement the Basic Income before that happens so everyone can benefit from progress. The tariffs just give us time to get the needed changes in place.
Nonsense. They are designed to protect our entire economy from being drained dry due to an "impedance mismatch". They do have the effect of protecting domestic producers from foreign producers who pay their workers less than it costs to live here. They also protect the domestic workforce from foreign workers who's expenses are a tiny fraction of ours. No worker, no matter how good will ever be able to compete if he has to come up with $1500/month to get by when the other guy needs $50 or less.
Agreed. Obamacare did implement a few insurance reforms, but fundamentally insurance cannot fix the problem that even the most routine healthcare is 4 times more expensive than it has any right to be.
They also cause employment and rising salaries to help you pay for those increased prices. So there's your choices, have a good job that pays well and you have to save for a couple months for more expensive goods but you can also afford food, clothing, and shelter along with health care or you can have cheap phones and a crappy job that barely pays so you can't afford those other things.
That's because they keep wanting to make phones thin enough to chop onions. That and instead of just some bounds checking and such, they use a Java like VM.
Most commonly, when some other function of module breaks a contract in the API, or string manipulation is in play.
For example, a function is supposed to never return more than 2K characters but it returns 2K+1. Perhaps because someone forgot that a null char would be appended.
Or for example, you build a string in a buffer but forget to NULL terminate it. Then you strcat a newline. Unfortunately, strcat scans the string until it hits a null somewhere after the end of the buffer and then overwrites it with newline and the next byte with zero, Exactly where that is will be somewhat random. You might get away with it for millions of iterations and then one day something elsewhere in the program mysteriously fails a few minutes after the buggy code ran.
In part, the standard libraries are to blame. Too many functions in it don't offer any sort of sane limits. The string functions that do have limits leave off the NULL terminator if they reach them. Fortunately one of the worst offenders, gets, now causes a compiler warning.
Much of this is because when C and it's standard libraries were created, CPU cycles were expensive. That and for every function you might want to make safer, there's a very good reason why an unsafe version is necessary.
A nice excuse of sorts, but it's not like it was his first campaign and he was managing OK so far. Meanwhile, they misjudged horribly as far as fallout is concerned. They actually got people who were more or less on the democrat's side to vote for Trump! They gave their own foot both barrels.
Then, after the primary, the Ds just assumed people would eat whatever slop they plopped down in front of them. Not even an effort to offer an olive branch to Bernie supporters. Had they tried, they could have easily captured enough votes to make the difference.
Again, going by the first article, relocating people implied that disconnecting it from the internet wasn't a viable solution. The onlyu reason that would be is if it depended on tyhe internet. Is that hard to grok?
No need to argue further over the name. Call it purple parakeet poop if you like. No skin off of my nose if someone says cloud and you look like a fool because you don't know what it might mean. (Why not, they look like fools for not knowing it's just the same-old with a shiny new name.)
According to TFA, the system failed as a result of the DDOS and they were talkiong about relocating people.
I have seen a followup article from another source saying that the system was actually maintaining the last temperature set and could be disconnected from the internet. That does put a very different light on the situation, but it is from a different article and different information.
But you're still missing it. The only thing new about "The Cloud" is calling it "The Cloud". One of it's more famous complainants is just virtual server rental with more automation and a shorter timeframe.
It is notable that most analysis showed Sanders being stronger against Trump than Clinton. If they had really wanted the best chance of having someone at least nominally a Democrat in office, they shouldn't have pushed the coronation.
Those few points advantage Sanders was projected to have over Clinton would have likely turned the election. Not to mention they would have avoided the defections that hurt them in the House and Senate.
"The Cloud" is just marketing speak for being utterly dependent on a remote server on the internet. How did you miss that one? Marketers like calling it the cloud because it's so fluffy.
OP's point stands, it was stupid as hell to make the thing so that a flood or any other loss of connectivity would cause it to fail at it's most important function. Which end of the connection is DDOSed is of little importance to determining the level of stupidity.
In the sense that Cloud is more a marketing term than a technical one, yes. It's basically just the hipster way to say internet. It often indicates some sort of dependence on a remote server somewhere, generally unwarranted.
It's a reference to the cloud icon in old style data flow diagrams.
In other words, the device was connected to the cloud so that it could be attacked. And since they apparently can't fix it by disconnecting the controller from the internet (they're talking about relocating tenants), it is cloud dependent. Cloud doesn't JUST mean a massive provider like Amazon.
Actually, neither problem is that hard to solve with appropriate hardware. You just have to rate limit the network interrupt by only re-enabling it if there is room in the Rx queue. Another answer is to use a dedicated I/O processor for networking and a main processor that polls it only when idle. You can get WiFi devices with such a dedicated CPU built in these days. If it gets a DDOS, the I/O processor gets overloaded and polls from the main CPU just time out and the device continues to operate normally in local mode (even accepting local control inputs). No need for real time at all. Perhaps it turns on a status light to indicate network failure.
That's exactly it. An intranet controllable thermostat suitable for control from a browser and a well documented REST based API would be potentially useful. Ideally it should have a switch to take it off of the network and operate in local-only mode in case of trouble. A thermostat that has to phone home to work is a terrible idea.
I can't decide if the big push for the cloud when it comes to the (id)IOT is based primarily on incompetence or a cynical move to lock people in.
The whole thing was screwed from the start. I doubt most of the voters even understood the likely consequences of Brexit. Effectively, they voted that every person shall receive a paddling and a money pooping unicorn. Guess which one turns out not to happen?
I am simply an outside observer from across the pond, but given all the trickery, flat out lies, and buyer's remorse over the referendum (including, apparently, claiming that the referendum carried any more legal weight than a Gallup poll), and how narrowly Brexit prevailed, it isn't at all clear that the referendum represents the current will of the people.
Unfortunately, Americans won't get a similar reprieve in the Trump v. Clinton question.
The hack was to pass emissions without including a urea system. With or without the hack, nobody in the market for an F350 or similar was ever going to choose the VW. With the urea system, they could pass emissions without the cheat.
As for the trucks, I'm all for tightening up regulations there, particularly when they are used exclusively as passenger vehicles for no good reason. Rolling coal should carry a hefty fine due to the willfulness.
Slashdot Mirror
Actually, it was tariffs on cars that convinced Japanese auto makers to manufacture cars in the U.S. That employed a lot of people. I agree that it doesn't solve all problems. Eventually better and better automation starts taking over. I look forward to that as long as we implement the Basic Income before that happens so everyone can benefit from progress. The tariffs just give us time to get the needed changes in place.
Nonsense. They are designed to protect our entire economy from being drained dry due to an "impedance mismatch". They do have the effect of protecting domestic producers from foreign producers who pay their workers less than it costs to live here. They also protect the domestic workforce from foreign workers who's expenses are a tiny fraction of ours. No worker, no matter how good will ever be able to compete if he has to come up with $1500/month to get by when the other guy needs $50 or less.
Agreed. Obamacare did implement a few insurance reforms, but fundamentally insurance cannot fix the problem that even the most routine healthcare is 4 times more expensive than it has any right to be.
They also cause employment and rising salaries to help you pay for those increased prices. So there's your choices, have a good job that pays well and you have to save for a couple months for more expensive goods but you can also afford food, clothing, and shelter along with health care or you can have cheap phones and a crappy job that barely pays so you can't afford those other things.
That's because they keep wanting to make phones thin enough to chop onions. That and instead of just some bounds checking and such, they use a Java like VM.
My phone runs 500 times faster than the mini that C was designed on.
If you need all that, use ATM. Ethernet is meant to be a low cost technology for the vast majority who don't need those features.
Most commonly, when some other function of module breaks a contract in the API, or string manipulation is in play.
For example, a function is supposed to never return more than 2K characters but it returns 2K+1. Perhaps because someone forgot that a null char would be appended.
Or for example, you build a string in a buffer but forget to NULL terminate it. Then you strcat a newline. Unfortunately, strcat scans the string until it hits a null somewhere after the end of the buffer and then overwrites it with newline and the next byte with zero, Exactly where that is will be somewhat random. You might get away with it for millions of iterations and then one day something elsewhere in the program mysteriously fails a few minutes after the buggy code ran.
In part, the standard libraries are to blame. Too many functions in it don't offer any sort of sane limits. The string functions that do have limits leave off the NULL terminator if they reach them. Fortunately one of the worst offenders, gets, now causes a compiler warning.
Much of this is because when C and it's standard libraries were created, CPU cycles were expensive. That and for every function you might want to make safer, there's a very good reason why an unsafe version is necessary.
A nice excuse of sorts, but it's not like it was his first campaign and he was managing OK so far. Meanwhile, they misjudged horribly as far as fallout is concerned. They actually got people who were more or less on the democrat's side to vote for Trump! They gave their own foot both barrels.
Then, after the primary, the Ds just assumed people would eat whatever slop they plopped down in front of them. Not even an effort to offer an olive branch to Bernie supporters. Had they tried, they could have easily captured enough votes to make the difference.
Again, going by the first article, relocating people implied that disconnecting it from the internet wasn't a viable solution. The onlyu reason that would be is if it depended on tyhe internet. Is that hard to grok?
No need to argue further over the name. Call it purple parakeet poop if you like. No skin off of my nose if someone says cloud and you look like a fool because you don't know what it might mean. (Why not, they look like fools for not knowing it's just the same-old with a shiny new name.)
Nominally as in so-called. He is necessarily nominally a republican since he ran as one and won the Republican primary.
You are arguing that he is effectively>/i> a Democrat.
According to TFA, the system failed as a result of the DDOS and they were talkiong about relocating people.
I have seen a followup article from another source saying that the system was actually maintaining the last temperature set and could be disconnected from the internet. That does put a very different light on the situation, but it is from a different article and different information.
But you're still missing it. The only thing new about "The Cloud" is calling it "The Cloud". One of it's more famous complainants is just virtual server rental with more automation and a shorter timeframe.
It is notable that most analysis showed Sanders being stronger against Trump than Clinton. If they had really wanted the best chance of having someone at least nominally a Democrat in office, they shouldn't have pushed the coronation.
Those few points advantage Sanders was projected to have over Clinton would have likely turned the election. Not to mention they would have avoided the defections that hurt them in the House and Senate.
"The Cloud" is just marketing speak for being utterly dependent on a remote server on the internet. How did you miss that one? Marketers like calling it the cloud because it's so fluffy.
OP's point stands, it was stupid as hell to make the thing so that a flood or any other loss of connectivity would cause it to fail at it's most important function. Which end of the connection is DDOSed is of little importance to determining the level of stupidity.
In the sense that Cloud is more a marketing term than a technical one, yes. It's basically just the hipster way to say internet. It often indicates some sort of dependence on a remote server somewhere, generally unwarranted.
It's a reference to the cloud icon in old style data flow diagrams.
In other words, the device was connected to the cloud so that it could be attacked. And since they apparently can't fix it by disconnecting the controller from the internet (they're talking about relocating tenants), it is cloud dependent. Cloud doesn't JUST mean a massive provider like Amazon.
Thinking about it, if they're actually thinking of relocating tennants rather than just unplugging the internet connection, it must be #1 :-(
Actually, neither problem is that hard to solve with appropriate hardware. You just have to rate limit the network interrupt by only re-enabling it if there is room in the Rx queue. Another answer is to use a dedicated I/O processor for networking and a main processor that polls it only when idle. You can get WiFi devices with such a dedicated CPU built in these days. If it gets a DDOS, the I/O processor gets overloaded and polls from the main CPU just time out and the device continues to operate normally in local mode (even accepting local control inputs). No need for real time at all. Perhaps it turns on a status light to indicate network failure.
That's exactly it. An intranet controllable thermostat suitable for control from a browser and a well documented REST based API would be potentially useful. Ideally it should have a switch to take it off of the network and operate in local-only mode in case of trouble. A thermostat that has to phone home to work is a terrible idea.
I can't decide if the big push for the cloud when it comes to the (id)IOT is based primarily on incompetence or a cynical move to lock people in.
They also investigated the Kingsmen's Louie Louie for 31 months for obscenity before deciding the lyrics were indecipherable.
Oddly enough, 200 years ago, few people needed a lawyer (or could even find one). Your representative was generally just the smartest person you knew.
Then in the winter months we can eat raw marshmallows and shiver in front of a recording of a roaring fire.
The whole thing was screwed from the start. I doubt most of the voters even understood the likely consequences of Brexit. Effectively, they voted that every person shall receive a paddling and a money pooping unicorn. Guess which one turns out not to happen?
I am simply an outside observer from across the pond, but given all the trickery, flat out lies, and buyer's remorse over the referendum (including, apparently, claiming that the referendum carried any more legal weight than a Gallup poll), and how narrowly Brexit prevailed, it isn't at all clear that the referendum represents the current will of the people.
Unfortunately, Americans won't get a similar reprieve in the Trump v. Clinton question.
The hack was to pass emissions without including a urea system. With or without the hack, nobody in the market for an F350 or similar was ever going to choose the VW. With the urea system, they could pass emissions without the cheat.
As for the trucks, I'm all for tightening up regulations there, particularly when they are used exclusively as passenger vehicles for no good reason. Rolling coal should carry a hefty fine due to the willfulness.