but I would wager 95% of the people on the planet don't.
Now we could argue that most software developers belong to the upper range of IQ and skills, but I still would bet 50% of all software developers don't know the rules.
Meanwhile there may be an operations manager panicking because he thinks billing software will screw up if they feed in 25 hours in a single day. That is one of the points why "time problems" are not trivial, even if they look like that.
In my experience (in software engineering) basically everything that looks trivial on the first glance gets pretty quickly quite complex.
And migrating away from time zones and DST is amazingly hard to do, even if some programmers think otherwise. Exactly.
I first stumbled over the complexity of "time" when I did a project in the university. It was actually a pure database problem, but I'm not sure if it was in an SQL database or a graph DB. (We had several problems to solve and used both versions of DBs, I just don't remember which for which).
Anyway, you have to plan flight crews. Restrictions are the ratings of the crew, every pilot or cabin crew is only "capable/allowed" to be a crew member on two plane types. Then comes flight times. Is a flight not longer than 6h, the same crew can take the next flight (typical a return flight) 12h later. If the flight is longer than 6h but less than 10h, the flight crew can be scheduled 24h after landing for the next flight. Is the flight longer, it is 32h or 36h. (*)
Now, the problem starts: how long is a flight when you depart local time 12:00PM and arrive local time 16:00PM but flew 4 time zones to the east. How does it look if you fly to the west?
At that time the times where stored as strings in the DB. And an extra column told you if you gained a day or lost a day.
That is just simple math, not that complicated, but 75% of the students did not grasp the problem with timezones and flight direction.
(*) Those numbers I just made up, no idea how they actually are, that was nearly 25 years ago, that I had that stuff. Now imagine you fly from a non DST time zone into one with DST, or timezones that have their DST at different times in the year. Well, that is not so complicated as the times are always local time... I don't remember if the actually scheduled "flight duration" was in the DB... I think it was not, because that was the core problem.
To exploit Specter and Meltdown an attacker needs physical or remote access to the machine to install a "malware" to exploit it. And needs a way to run that malware, as in remote access.
A typical server would have no access from the internet besides HTTP or what ever protocol you expose.
My Mac is a little bit vulnerable because in theory one could have a Javascript exploiting one of the two, but that is so hypothetical, I doubt anyone will ever be able to actually steal some sensitive data from my Mac with that.
but the idea is that if you have an integer unit and a floating point unit, hyper-threading lets you treat them as two cores. No, that is not the idea. How would that work?
The floating point "core" suddenly is able to interpret integer instructions? A magical process is translating integer instructions to floating point instructions, so the FPU can execute them? Another magic knows that 100.0 +1.0 is not 100.99999 and transforms it magically back into an int with the value of 100?
Hyperthreading works by having every register 2 times. While one thread e.g. is waiting for a register to be filled from memory, the other thread can do register to register arithmetic. Ofc there are more things that can be paralleled...
"The Germans" did not exist at that time. It was an area with perhaps 100 small and larger principals, small kingdoms and earlships. Despite the success with the Kogge, a trading ship, they were not great sailors anyway.
The fact that "one german" wrote about it, does not mean many german (rulers?) knew about it. Heck, it was not even common knowledge 50 years ago in the western world...
DST in Europe ends last WE of October... just in case you are wondering where the bugs come from.
Uh, and if you don't know how software is tested I would refrain from stupid statements like "Oh, wait. Apple doesn't actually test stuff, but somewhere in the rest of the world someone does..."
Last time I made an omelet, I burned it on one side. How would testing prevent me from burning it? It does not. The only test I can make is: put it on the plate for the customer and realize: oh, it is burned.
For time related problems it is often the case that you are in the same situation: I can only test at the time when the time is... or how exactly do _you moron_ test an App on an iWatch shifting time around for every time zone, every DST and prevent the watch from seeing GPS time? Yeah, can be done, ist actually not that hard, but why do you idiot claim that Apple is not testing its OS?
if that were the case the banking industry, Internet, phones, etc. would fall over at the same time because of the same problems.
I wold dare to say: at least the banking industry is completely uneffeced by DST, and I'm pretty sure phone companies and internet companies are neither.
And they didn't bother to check (i.e. test) adequately enough before releasing millions of dollars of mass-market products. Checking/testing for time bugs is a pain in the ass. If you have a solution you are a millionaire over night, literally.
The problem is lax development and testing. No it is not. It is the unimaginable complexity in a simple problem. With your outrageous claims you failed into the same trap.
However, as I worked quite a long time in the energy business: DST is a pain in the ass. Not only because of programmers making mistakes (I would not call that incompetent... what again are the rules for a leap year? Are you sure you know them all? It is only 2 rules, though, or 3, depending how you count)
Mistakes are also made in the requirements/business analysis. And if a programmer says: "uh, that does not look right" often he gets stared down and challenged: who are you to know better than me.
Regarding "energy business": You have every day a kind of spread cheat with 24 hours as columns down. For every power plant you have 4 rows, planned power production for every quarter hour.
Two days of the year are an exception. One day has 23 columns, one has 25.
Then again if you e.g. want to sent power from Germany to France or to Poland, you have to prepare a "schedule" for your grid feed in, 24h ahead (erm, 23h? 24h? 25h?).
The grid operator is working his grid, similar as pointed out above, with 24h columns and his balancing/reserve power plants according to the schedule. But: two times in the year the schedule has not 24 but 25 or 23 columns.
One unix idiot... idiot because I considered him a friend, until he started bullying me in some jobs... once said: "it is so easy! Just schedule everything in UT!" What he did not grasp is: everything is scheduled in UTC. But you nevertheless want one day in the year to see your whole day as a 25h day, and the other day in the year you want to see your whole day as a 23h day...
It is quite important that my French or my Polish power company friends agrees that we are at 2:00A or 2:00B at night for a power feed into the grid.
The idea that wind turbines kill huge amount of birds is bollocks. However the idea (yeah, that was discussed on/. often enough) that cats kill close to 4billion birds per year in the US is bollocks, too. If every american had a cat, his cat would need to go outside and kill 10 birds per year. While you now can shift around numbers about how many cats there are in the US, you can shift up the numbers of bird kill per cat.
I have no clue why people have problems with big numbers. They are just numbers... like small numbers.
Wow, people with no mind... all over the world only idiots.
Again, WHEN yellowstone blows then 90% or 99% of all humans will die over the course of a hand full of years.
Wether there are mainly nuklear plants or mainly solar plants is completely irrelevant if you have no food to eat and winters you can not survive outside of half way modern buildings...
And no, it was NEVER designed to prevent escape into environment if a melt down occurs.
Yes it was, all old school reactors are designed for that: but failed in Fukushima. E.g. TMI (it did not fail though, but was designed for preventing it, or more precisely: coping with it.)
Fukushima was designed at least to prevent a core melt down, and failed at that. Or more precisely, if a melt down happens: prevent escape of the fuel into the environment, and it failed at that.
As in martial arts, stunt people learn how to go to the ground while minimizing the impact on their body. So a fake fall is quite different from a natural fall, even if it looks for the audience the same (or similar).
An iranian group, and some traveling iranian politician was involved, probably planned to assassinate another iranian living in France... so: no terrorist attack.
Iran just got caught red-handed planning a terrorist attack in France Pretty unlikely. Why would Iran attack one of its biggest (if not THE BIGGEST) trade partners?
Since about ten years we have in the news every month or every second month findings reported about this or that gene being transferred from Neanderthals to modern humans... so I doubt it is all based on two or three findings. Basically every news article is referring to many examinations, not just a single one.
Why is Apple trying so hard to deny a story that Bloomberg insists is accurate and very well sourced? Because the Bloomberg story is bollocks? No idea, but the stuff they wrote about Germanies renewable energy was usually all the time I bothered to read it: bollocks.
We found thousands of hybrids and hundred thousands of genes that got exchanged from one species to the other. E.g. "red hair" genes and "pain tolerance" jumped from neanderthaliens to sapiense sapiense.
Bottom line they looked like us anyway with just minor differences, depicting them like hairy apes is out of fashion since 50 years.
Slashdot Mirror
So did I,
but I would wager 95% of the people on the planet don't.
Now we could argue that most software developers belong to the upper range of IQ and skills, but I still would bet 50% of all software developers don't know the rules.
Meanwhile there may be an operations manager panicking because he thinks billing software will screw up if they feed in 25 hours in a single day.
That is one of the points why "time problems" are not trivial, even if they look like that.
In my experience (in software engineering) basically everything that looks trivial on the first glance gets pretty quickly quite complex.
And migrating away from time zones and DST is amazingly hard to do, even if some programmers think otherwise.
Exactly.
I first stumbled over the complexity of "time" when I did a project in the university. It was actually a pure database problem, but I'm not sure if it was in an SQL database or a graph DB. (We had several problems to solve and used both versions of DBs, I just don't remember which for which).
Anyway, you have to plan flight crews. Restrictions are the ratings of the crew, every pilot or cabin crew is only "capable/allowed" to be a crew member on two plane types. Then comes flight times. Is a flight not longer than 6h, the same crew can take the next flight (typical a return flight) 12h later. If the flight is longer than 6h but less than 10h, the flight crew can be scheduled 24h after landing for the next flight. Is the flight longer, it is 32h or 36h. (*)
Now, the problem starts: how long is a flight when you depart local time 12:00PM and arrive local time 16:00PM but flew 4 time zones to the east. How does it look if you fly to the west?
At that time the times where stored as strings in the DB. And an extra column told you if you gained a day or lost a day.
That is just simple math, not that complicated, but 75% of the students did not grasp the problem with timezones and flight direction.
(*) Those numbers I just made up, no idea how they actually are, that was nearly 25 years ago, that I had that stuff. ... I don't remember if the actually scheduled "flight duration" was in the DB ... I think it was not, because that was the core problem.
Now imagine you fly from a non DST time zone into one with DST, or timezones that have their DST at different times in the year. Well, that is not so complicated as the times are always local time
The attack vector is extremely limited anyway.
To exploit Specter and Meltdown an attacker needs physical or remote access to the machine to install a "malware" to exploit it. And needs a way to run that malware, as in remote access.
A typical server would have no access from the internet besides HTTP or what ever protocol you expose.
My Mac is a little bit vulnerable because in theory one could have a Javascript exploiting one of the two, but that is so hypothetical, I doubt anyone will ever be able to actually steal some sensitive data from my Mac with that.
but the idea is that if you have an integer unit and a floating point unit, hyper-threading lets you treat them as two cores.
No, that is not the idea.
How would that work?
The floating point "core" suddenly is able to interpret integer instructions? A magical process is translating integer instructions to floating point instructions, so the FPU can execute them? Another magic knows that 100.0 +1.0 is not 100.99999 and transforms it magically back into an int with the value of 100?
Hyperthreading works by having every register 2 times. While one thread e.g. is waiting for a register to be filled from memory, the other thread can do register to register arithmetic. Ofc there are more things that can be paralleled ...
"The Germans" did not exist at that time.
It was an area with perhaps 100 small and larger principals, small kingdoms and earlships.
Despite the success with the Kogge, a trading ship, they were not great sailors anyway.
The fact that "one german" wrote about it, does not mean many german (rulers?) knew about it. ...
Heck, it was not even common knowledge 50 years ago in the western world
DST in Europe ends last WE of October ... just in case you are wondering where the bugs come from.
Uh, and if you don't know how software is tested I would refrain from stupid statements like "Oh, wait. Apple doesn't actually test stuff, but somewhere in the rest of the world someone does..."
Last time I made an omelet, I burned it on one side. How would testing prevent me from burning it? It does not. The only test I can make is: put it on the plate for the customer and realize: oh, it is burned.
For time related problems it is often the case that you are in the same situation: I can only test at the time when the time is ... or how exactly do _you moron_ test an App on an iWatch shifting time around for every time zone, every DST and prevent the watch from seeing GPS time? Yeah, can be done, ist actually not that hard, but why do you idiot claim that Apple is not testing its OS?
if that were the case the banking industry, Internet, phones, etc. would fall over at the same time because of the same problems.
I wold dare to say: at least the banking industry is completely uneffeced by DST, and I'm pretty sure phone companies and internet companies are neither.
And they didn't bother to check (i.e. test) adequately enough before releasing millions of dollars of mass-market products.
Checking/testing for time bugs is a pain in the ass. If you have a solution you are a millionaire over night, literally.
The problem is lax development and testing.
No it is not. It is the unimaginable complexity in a simple problem. With your outrageous claims you failed into the same trap.
Well, from one point of view you are right.
However, as I worked quite a long time in the energy business: DST is a pain in the ass. Not only because of programmers making mistakes (I would not call that incompetent ... what again are the rules for a leap year? Are you sure you know them all? It is only 2 rules, though, or 3, depending how you count)
Mistakes are also made in the requirements/business analysis. And if a programmer says: "uh, that does not look right" often he gets stared down and challenged: who are you to know better than me.
Regarding "energy business": You have every day a kind of spread cheat with 24 hours as columns down. For every power plant you have 4 rows, planned power production for every quarter hour.
Two days of the year are an exception. One day has 23 columns, one has 25.
Then again if you e.g. want to sent power from Germany to France or to Poland, you have to prepare a "schedule" for your grid feed in, 24h ahead (erm, 23h? 24h? 25h?).
The grid operator is working his grid, similar as pointed out above, with 24h columns and his balancing/reserve power plants according to the schedule. But: two times in the year the schedule has not 24 but 25 or 23 columns.
One unix idiot ... idiot because I considered him a friend, until he started bullying me in some jobs ... once said: "it is so easy! Just schedule everything in UT!" What he did not grasp is: everything is scheduled in UTC. But you nevertheless want one day in the year to see your whole day as a 25h day, and the other day in the year you want to see your whole day as a 23h day ...
It is quite important that my French or my Polish power company friends agrees that we are at 2:00A or 2:00B at night for a power feed into the grid.
The idea that wind turbines kill huge amount of birds is bollocks. /. often enough) that cats kill close to 4billion birds per year in the US is bollocks, too.
However the idea (yeah, that was discussed on
If every american had a cat, his cat would need to go outside and kill 10 birds per year. While you now can shift around numbers about how many cats there are in the US, you can shift up the numbers of bird kill per cat.
I have no clue why people have problems with big numbers. They are just numbers ... like small numbers.
Wow, people with no mind ... all over the world only idiots.
Again, WHEN yellowstone blows then 90% or 99% of all humans will die over the course of a hand full of years.
Wether there are mainly nuklear plants or mainly solar plants is completely irrelevant if you have no food to eat and winters you can not survive outside of half way modern buildings ...
Hint, for a old fuck like you, you should finally take the guts and open the wikipedia article: https://en.wikipedia.org/wiki/...
I'm tired of idiots who think a solar plant can not provide base load ...
And no, it was NEVER designed to prevent escape into environment if a melt down occurs.
Yes it was, all old school reactors are designed for that: but failed in Fukushima. E.g. TMI (it did not fail though, but was designed for preventing it, or more precisely: coping with it.)
oO!
I smell Butler's Jihad here!!
Offshore usually implies, they are so far away, you don't see them from shore. :D
However, your milage may vary
Fukushima was designed at least to prevent a core melt down, and failed at that.
Or more precisely, if a melt down happens: prevent escape of the fuel into the environment, and it failed at that.
As in martial arts, stunt people learn how to go to the ground while minimizing the impact on their body.
So a fake fall is quite different from a natural fall, even if it looks for the audience the same (or similar).
I'm an expert in energy production and transmission, not an expert about "controlling wind", what ever you mean with that.
As I said before: you misunderstood something.
I read up a bit on it.
An iranian group, and some traveling iranian politician was involved, probably planned to assassinate another iranian living in France ... so: no terrorist attack.
Iran just got caught red-handed planning a terrorist attack in France
Pretty unlikely. Why would Iran attack one of its biggest (if not THE BIGGEST) trade partners?
Since about ten years we have in the news every month or every second month findings reported about this or that gene being transferred from Neanderthals to modern humans ... so I doubt it is all based on two or three findings. Basically every news article is referring to many examinations, not just a single one.
I'm not aware that someone is controlling wind ... you seem to have misunderstood something
Decent is very well defined.
Get a dictionary. Or did I spell it wrong and yo can not guess which word I meant ... then get psychiatric help.
Why is Apple trying so hard to deny a story that Bloomberg insists is accurate and very well sourced?
Because the Bloomberg story is bollocks?
No idea, but the stuff they wrote about Germanies renewable energy was usually all the time I bothered to read it: bollocks.
On what planet do you live?
We found thousands of hybrids and hundred thousands of genes that got exchanged from one species to the other. E.g. "red hair" genes and "pain tolerance" jumped from neanderthaliens to sapiense sapiense.
Bottom line they looked like us anyway with just minor differences, depicting them like hairy apes is out of fashion since 50 years.
Nonsense. ... what a brain dead idea.
Immune system traits are not trade offs
From your fucking cellphone.
Hm, interesting. He might soon have some baby cell phones, I volunteer to raise one!