No no, he's TOTALLY right. I saw once a SSgt E-5 cook and his potato peeler guy working on the specs for a new laser-based missile-defense program. Supposedly the same tech would serve to improve the potato peeling efficiency ratio by an order of magnitude.
No it isn't. Up until the point where the guy decided to sell the ISK to ISK sellers for real money, it was all perfectly ok. Worse thefts and scams have happened, and it's all sanctioned by CCP.
Actually, it's more like the government 'promised' that the law would be revised, and clear signals would be sent from the politicians for how monitoring of filesharers should be treated. The Datatilsynet, the department responsible for ensuring people's digital privacy, etc are protected, gave that license under the assumption that the law/policies would be revised soon.
It didn't happen.
And the Datatilsynet are very strong on protecting people's privacy, and thus they didn't want to be providing the loop-hole that allowed politicians to leave this hot topic on ice.
Well, you would rather ask a doctor who's average, but used to be severely overweight. Because you know he's been through the same thing you need to go through, and thus can emphasis better than that doctor that's lean and always did exercise.
I was in the same situation a few years ago. (And it was starting to affect my mental health in ways that couldn't end well)
My solution was; I moved to Japan and put myself in a situation where I was forced to deal with other people to manage daily life, and by trying to learn a (rather difficult) language I had the excuse not to be an excellent at talking with people. This allowed me to gradually build up my verbal communication skills and deal with my paranoia, etc.
This might however been a bit over the top for some people.
Your categorical denouncement of the previous post shows you do _not_ understand as much as you think.
The source data can often be _MUCH_ smaller than the resulting cached data, and as such reading the cached data from RAM can be more expensive than reading the source data plus processing it.
It's not a problem as while the agency responsible for pushing companies to secure, delete or reorganize the information they hold on individuals, they haven't really gone after web-server logs and systems used to track virus infected bots. But if you try using logs to catch filesharers, you might suddenly get in trouble.
I guess we're just a bit more flexible when it comes to applying common sense.
Demand is through the roof as some of us--the ones who believe that the government is answerable to its people--are stocking up in case of future interruptions in supply.
I'm sorry... Maybe it's cause I'm from Europe, but what does guns have to do with government being answerable to the people?
If they don't answer, you'll shoot them? Hell, in Norway we got 1.5 million weapons with a population of 4.7 million. Yet we don't go around having wet dreams of a future where the government becomes totalitarian so we can shoot people we don't like in an excuse of a revolution.
We got the 11th lowest murder rate in the world. I think you guys just need to stop being so angry at the world.
No... It's _EVEN_ better/worse/weird_as_hell than that. People who aren't very familiar with EVE always get shocked when they hear it the first time and putter on in denial for the longest time.
Brace yourselves:
When a ship gets destroyed in EVE, the amount of ISK in the gameworld _INCREASES_. It doesn't disappear, it doesn't stay balanced. That is to say; loss of ships is not an ISK sink, it's an ISK faucet.
The reason for this is that the player you bought the ship from, or the players that did the mining for minerals, still got the ISK so it's still in the system. And the you, the player, just received a payout on the in-game insurance that covers all ships. This insurance (for T1 ships) gives you back almost as much ISK as it cost on the markets.
Sorry, but thinking in 'half-year terms' is _not_ short-sighted for 15 year old kids. And isn't this actually _exactly_ the kind of lessons kids need?
Work hard for an extended period of time and you'll be rewarded.
Really, shouldn't one ideally reward, in what ever form and in appropriate amounts, kids starting with short time-spans when very young and increasing the lenght, reward and demands as they get older? Kids 3 years old won't understand planning a week ahead, 8 year olds won't understand planning half a year ahead, 16 year olds... etc
These conclusions were challenged in a separate meta-analysis which found that tangible rewards offered for outperforming others and for performing uninteresting tasks (in which intrinsic motivation is low) lead to increased intrinsic motivation.
Which makes sense... Cause rewarding children purely for painting (no matter how good or bad) does not reward advancement of skills. What the school is doing here is rewarding long-term planning, hard work and competitiveness. Usually that reward was on an extremely-long-term, like 'when you get old, you'll have a better life'.
The problem is probably that the developers of that voting software was probably exactly like the OP, thinking: I'm pretty sure I could write a program with a couple of buttons and a counter for each.
Really, the very first step you'd need to make, is separating the system into a GUI client, operator client and vote server. The vote server would be easier to verify due to very few libraries and unrelated code being used. The GUI client would not be able to mangle _all_ vote results in an instance due to memory corruption issues. And requiring the operator to clear the vote server for receiving the next vote would avoid 5000 votes being registered due to a bug of any kind.
The server and GUI client would be separate users with different privileges and cryptographically signed log to append-write only medium. Hell, the final confirmation to the user should be displayed on screen by program using a plain-text message sent by the server to a different client process, just to ensure the GUI is showing a different choice from what it registers with the vote server.
And I'm sure there's plenty of other stuff that would need to be done to make a truly secure and reliable voting system.
Exactly... why would it fail on a single-threaded program?
The problem is much more that just simple race-conditions on instruction level. What do you do if the program crashes? You have no way of recovering if all you do is increment an array.
It really should keep a cryptographically signed logs of each vote, on hardware designed to be read only using specialized key+hardware. The GUI app and the vote management app should be separate programs, with different user/privileges. This would avoid the more complicated UI code having memory corruption issues affecting the vote registration. Each vote would need to do a proper syn/ack message passing to confirm the vote was registered, and a separate sequence sent to the operators controlling the voting booth so they can see the voter successfully cast a vote and tell the vote server when it can accept another vote.
Slashdot Mirror
Yet they both mean exactly the same, son of Lars.
No no, he's TOTALLY right. I saw once a SSgt E-5 cook and his potato peeler guy working on the specs for a new laser-based missile-defense program. Supposedly the same tech would serve to improve the potato peeling efficiency ratio by an order of magnitude.
Your high BMI is Gods gift to you, and one day you'll be _JUST_ like the Hulk. Don't let anyone tell you any differently!
I hate people like you, who arbitrarily drop curly braces from else blocks. Be consistent or I'll take a shit on your lawn after fixing your code.
In other places the ones in power oppress you, while in Japan you oppress yourself.
What he really wanted to say was; When will the space vixens invade earth? And will they make us their sex slaves.
No it isn't. Up until the point where the guy decided to sell the ISK to ISK sellers for real money, it was all perfectly ok. Worse thefts and scams have happened, and it's all sanctioned by CCP.
Yet the population is kept in check by hungry salarymen eating anything with tentacles.
The first 300 degrees Kelvin due to the sun might be all well and good, but when you add 20 degrees more by man-made causes you get big problems.
Actually, it's more like the government 'promised' that the law would be revised, and clear signals would be sent from the politicians for how monitoring of filesharers should be treated. The Datatilsynet, the department responsible for ensuring people's digital privacy, etc are protected, gave that license under the assumption that the law/policies would be revised soon. It didn't happen. And the Datatilsynet are very strong on protecting people's privacy, and thus they didn't want to be providing the loop-hole that allowed politicians to leave this hot topic on ice.
So what else am I supposed to mate with? Socks are much harder to clean.
Well, you would rather ask a doctor who's average, but used to be severely overweight. Because you know he's been through the same thing you need to go through, and thus can emphasis better than that doctor that's lean and always did exercise.
I was in the same situation a few years ago. (And it was starting to affect my mental health in ways that couldn't end well)
My solution was; I moved to Japan and put myself in a situation where I was forced to deal with other people to manage daily life, and by trying to learn a (rather difficult) language I had the excuse not to be an excellent at talking with people. This allowed me to gradually build up my verbal communication skills and deal with my paranoia, etc.
This might however been a bit over the top for some people.
Your categorical denouncement of the previous post shows you do _not_ understand as much as you think.
The source data can often be _MUCH_ smaller than the resulting cached data, and as such reading the cached data from RAM can be more expensive than reading the source data plus processing it.
It's not a problem as while the agency responsible for pushing companies to secure, delete or reorganize the information they hold on individuals, they haven't really gone after web-server logs and systems used to track virus infected bots. But if you try using logs to catch filesharers, you might suddenly get in trouble. I guess we're just a bit more flexible when it comes to applying common sense.
Demand is through the roof as some of us--the ones who believe that the government is answerable to its people--are stocking up in case of future interruptions in supply.
I'm sorry... Maybe it's cause I'm from Europe, but what does guns have to do with government being answerable to the people?
If they don't answer, you'll shoot them? Hell, in Norway we got 1.5 million weapons with a population of 4.7 million. Yet we don't go around having wet dreams of a future where the government becomes totalitarian so we can shoot people we don't like in an excuse of a revolution.
We got the 11th lowest murder rate in the world. I think you guys just need to stop being so angry at the world.
I thought the Slashdot community was open for all kinds of fetishes... ;(
I thought it was knowledge for the sake of pork.
No... It's _EVEN_ better/worse/weird_as_hell than that. People who aren't very familiar with EVE always get shocked when they hear it the first time and putter on in denial for the longest time.
Brace yourselves:
When a ship gets destroyed in EVE, the amount of ISK in the gameworld _INCREASES_. It doesn't disappear, it doesn't stay balanced. That is to say; loss of ships is not an ISK sink, it's an ISK faucet.
The reason for this is that the player you bought the ship from, or the players that did the mining for minerals, still got the ISK so it's still in the system. And the you, the player, just received a payout on the in-game insurance that covers all ships. This insurance (for T1 ships) gives you back almost as much ISK as it cost on the markets.
Well, the guy can't both demand people have less personal information protection _AND_ demand people have more personal information protection.
Sorry, but thinking in 'half-year terms' is _not_ short-sighted for 15 year old kids. And isn't this actually _exactly_ the kind of lessons kids need? Work hard for an extended period of time and you'll be rewarded. Really, shouldn't one ideally reward, in what ever form and in appropriate amounts, kids starting with short time-spans when very young and increasing the lenght, reward and demands as they get older? Kids 3 years old won't understand planning a week ahead, 8 year olds won't understand planning half a year ahead, 16 year olds... etc
These conclusions were challenged in a separate meta-analysis which found that tangible rewards offered for outperforming others and for performing uninteresting tasks (in which intrinsic motivation is low) lead to increased intrinsic motivation.
Which makes sense... Cause rewarding children purely for painting (no matter how good or bad) does not reward advancement of skills. What the school is doing here is rewarding long-term planning, hard work and competitiveness. Usually that reward was on an extremely-long-term, like 'when you get old, you'll have a better life'.
The problem is probably that the developers of that voting software was probably exactly like the OP, thinking: I'm pretty sure I could write a program with a couple of buttons and a counter for each.
Really, the very first step you'd need to make, is separating the system into a GUI client, operator client and vote server. The vote server would be easier to verify due to very few libraries and unrelated code being used. The GUI client would not be able to mangle _all_ vote results in an instance due to memory corruption issues. And requiring the operator to clear the vote server for receiving the next vote would avoid 5000 votes being registered due to a bug of any kind.
The server and GUI client would be separate users with different privileges and cryptographically signed log to append-write only medium. Hell, the final confirmation to the user should be displayed on screen by program using a plain-text message sent by the server to a different client process, just to ensure the GUI is showing a different choice from what it registers with the vote server. And I'm sure there's plenty of other stuff that would need to be done to make a truly secure and reliable voting system.
Exactly... why would it fail on a single-threaded program? The problem is much more that just simple race-conditions on instruction level. What do you do if the program crashes? You have no way of recovering if all you do is increment an array. It really should keep a cryptographically signed logs of each vote, on hardware designed to be read only using specialized key+hardware. The GUI app and the vote management app should be separate programs, with different user/privileges. This would avoid the more complicated UI code having memory corruption issues affecting the vote registration. Each vote would need to do a proper syn/ack message passing to confirm the vote was registered, and a separate sequence sent to the operators controlling the voting booth so they can see the voter successfully cast a vote and tell the vote server when it can accept another vote.
Yes, I much prefer my Zune!