I didn't quite get the bit about it being difficult for a person who wasn't outside the US to understand free speech (as I live in the US and understand what free speech is just fine). OTOHZ, I think about how many people in the US are in favor of more restrictions to curtail speech, and I hope that this is merely a local problem, and not a global one. Sadly, I doubt it.
If you really had the breadth of experience to code in "just about anything", you'd surely have picked up an assembly language or three in all those decades. Maybe you don't remember the specific mnemonics, but you should be able to do it with the reference manual at hand. I learned assembler and C right after Pascal.
The problem wasn't using a mere 10 pence of electricity, rather the antisocial behaviour
You fucking cunts and your ASBOs. Go fuck yourself, go fuck your mother, and die in a fire. And to quote gstoddart (one of my favorite lines on Slashdot lately):
Shit piss fuck cunt cocksucker motherfucker and tits. Fuck you, fuck off, go the fuck away, and don't make me tell you again.
Am I doing it right? Thankfully, I live in a country which, in theory, protects offensive speech.
I done me best when I was let. Thinking always if I go all goes. A hundred cares, a tithe of troubles and is there one who understands me? One in a thousand of years of the nights? All me life I have been lived among them but now they are becoming lothed to me. And I am lothing their little warm tricks. And lothing their mean cosy turns. And all the greedy gushes out through their small souls. And all the lazy leaks down over their brash bodies. How small it's all! And me letting on to meself always. And lilting on all the time. I sprang with the quickness like lightning, disappeared. I whistled for a cab and when it came near, the license plate said, "fresh", and it had dice in the mirror. If anything, I could say that this cab was rare. But I thought, "Nah, forget it"--"Never gonna give you up. Never gonna let you down. Never gonna run around and desert you, yo home to Bel-Air."
Sniffer of carrion, premature gravedigger, seeker of the nest of evil in the bosom of a good word, you, who sleep at our vigil and fast for our feast, you with your dislocated reason, have cutely foretold, a jophet in your own absence, by blind poring upon your many scalds and burns and blisters, impetiginous sore and pustules, by the auspices of that raven cloud, your shade, and by the auguries of rooks in parlament, death with every disaster, the dynamatisation of colleagues, the reducing of records to ashes, the levelling of all customs by blazes, the return of a lot of sweetempered gunpowdered didst unto dudst but it never stphruck your mudhead's obtundity (O hell, here comes our funeral! O pest, I'll miss the post!) that the more carrots you chop, the more turnips you slit, the more murphies you peel, the more onions you cry over, the more bullbeef you butch, the more mutton you crackerhack, the more potherbs you pound, the fiercer the fire and the longer your spoon and the harder you gruel with more grease to your elbow the merrier fumes your new Irish stew
Learn how things work. Learn why things work. Build things, experiment, and never make an assumption without clearly identifying it as such, even if it's only a mental note.
Don't take someone else's word--look it up and verify it. Try it out. Play with concepts. I don't recommend using your own crypto in production (at all, since the odds are against you being a qualified cryptographer), but implementing known algorithms for educational purposes and then running attacks against them will give you a much better idea how everything fits together and what should and should not be done.
Shit, is that too hard? Sadly, it probably is. Also, don't give me the "I have no time" excuse. Stop watching your fucking boob tube and spend that time educating yourself and helping those around you.
I browse at -1 and I mod by quality and relevance of comments. If you're moderating by username, AC or otherwise, you're effectively performing a continuous ad hominem.
And who pays for his medical injuries if he gets injured while trespassing in an abandoned building that may well be structurally unsound or otherwise hazardous?
How about personal responsibility? If you break into something, and it falls apart on you, guess whose fucking fault it is? YOURS.
This nanny-state shit has got to go. By the time you're 18, you ought to know damn well you shouldn't be breaking into shit, and if you do, and bad things happen, they're on your head. Of course, often that isn't how it works out in court, but that's how it should. Unsafe or hazardous conditions exist in much of the world, and we shouldn't have to put a guard, sign, fence, and attack dog around every single little thing to prevent people from injuring themselves through their own fucking stupidity by being where they never should have been in the first goddamn place.
Does the probability of an event happening change the ethical considerations?
For example, if you were to calculate your odds of being caught and severely punished embezzling from a business and found them to be extremely low, would it suddenly become ethical to embezzle?
You ought to read Hard-Boiled Wonderland and the End of the World by Murakami. I think you would enjoy it.
Quick summary from Wiki:
The story is split between parallel narratives. The odd-numbered chapters take place in the 'Hard-Boiled Wonderland', although the phrase is not used anywhere in the text, only in page headers. The narrator is a "Calcutec", a human data processor/encryption system who has been trained to use his subconscious as an encryption key. The Calcutecs work for the quasi-governmental System, as opposed to the criminal "Semiotecs" who work for the Factory and who are generally fallen Calcutecs. The relationship between the two groups is simple: the System protects data while the Semiotecs steal it, although it is suggested that one man might be behind both. The narrator completes an assignment for a mysterious scientist, who is exploring "sound removal". He works in a laboratory hidden within an anachronistic version of Tokyo's sewer system. The narrator eventually learns that he only has a day and a half to exist before he leaves the world he knows and delves forever into the world that has been created in his subconscious mind.
The man who buys the meat is brother to the butcher.
If you aren't at least willing to do it yourself, and simultaneously complain about conditions and cruelty while eating McNuggets, then you're a hypocrite. Vote with your actions and stand by your principles, assuming you have any.
Me? I eat meat. I don't hunt (no need to) or slaughter animals, myself, but I understand the process required to bring food to me. Were I suddenly required to do it myself, I would do it myself, not stop eating meat.
My sleep schedule tends to rotate if I don't have any fixed obligations (say, on vacation). I'm naturally a night person (worked overnights for years and really enjoyed that), but I tend to have a daytime awake phase and a nighttime awake phase.
With my current work, I'll go to sleep at 0000-0130, wake up from 0530-0630, work until 1600, come home, nap from 1900-2100, read the news, putz around, and start all over again. One day out of the week, I work from 0730 to 2000, with a couple of 30 minute breaks at 1230 and 1600.
If I don't have any obligations, I tend to sleep 4-5 hours when I get tired, wake up, and work for 6-8 hours, and then go back to sleep and do it again. This causes my sleep/awake times to rotate around, which I don't mind, but other people think I'm crazy. I'll also tend to wake up with the sun and go to sleep when it gets dark, which causes me to be awake much longer during the summer than the winter.
4 hours of sleep is enough to function on, but I prefer 5-6 hours if I have to be awake for an extended period, need to do heavy thinking or strenuous work. I can't sleep for 8 hours at a stretch. I'll just keep waking up every half hour.
JavaScript isn't necessarily such a bad language; otherwise, we wouldn't see Node.js gaining so much popularity.
Bandwagon appeal. With your UID, you ought to know better. Provide a technical argument and/or step away from the keyboard until you've thought it over. Note that I'm not saying there isn't a good reason--only that your given argument is crap.
I would nearly have lost my coffee via my nasal passages. Are the Brits really economically, technically, and industrially capable of doing this anymore? Sure, they have some large aerospace companies, but at a glance, they seem to be focused mostly on conventional passenger flight.
Sometimes I wonder if we (USA) still are. Then, I'm reminded that we have SpaceX. They're at least a small glimmer of hope.
Of course, I'm probably just out of touch with this planet.
You realize you can download software (used to be books) which lists the key bittings for blind codes for basically every manufacturer, except the ones that require you to mail in an ID card issued with the lock (and those are expensive)? This blind code is usually printed somewhere easily accessible.
Right?
Physical security is generally a joke. I place more stock in cryptography properly implemented than any pin tumbler, wafer tumbler, disc, or combination lock (safe or otherwise). Hands down. (That said, my trust in the security of computational hardware is pretty low, and properly implemented has a very high bar.)
Also, when you set up a master keying system, you inadvertently create keys out of the system that still function to open locks, because you need to break up the existing pins into a stack with multiple shear lines.
Want it done right? Do it in depth. Locks are there to keep honest people honest and slow criminals down a bit.
At 3:24, if you step frame-by-frame, you can see what looks like a large object flying up away from the rocket. That might be the capsule. If it survived, that would be amazing.
You're right, it looks like something venting out the side (you can see a little cloud there). Then that area comes apart. The flames from the engines appear to flare up, suggesting oxygen? Then, it starts burning hotter in the area you mentioned, looking like maybe it's burning it's way down into the lower stage. That fire gives out, but it's immediately followed by RUD.
Slashdot Mirror
If only I had mod points. +1, Insightful.
I didn't quite get the bit about it being difficult for a person who wasn't outside the US to understand free speech (as I live in the US and understand what free speech is just fine). OTOHZ, I think about how many people in the US are in favor of more restrictions to curtail speech, and I hope that this is merely a local problem, and not a global one. Sadly, I doubt it.
first actual demonstratable/sellable working vapour-ware product in history
Kids these days. Did we already forget steam engines?
Damnit. Suckered again.
If you really had the breadth of experience to code in "just about anything", you'd surely have picked up an assembly language or three in all those decades. Maybe you don't remember the specific mnemonics, but you should be able to do it with the reference manual at hand. I learned assembler and C right after Pascal.
I would assume putting a nice plague on it 'not for public use' has been done
I thought we all agreed not to engage in biological warfare?
The problem wasn't using a mere 10 pence of electricity, rather the antisocial behaviour
You fucking cunts and your ASBOs. Go fuck yourself, go fuck your mother, and die in a fire. And to quote gstoddart (one of my favorite lines on Slashdot lately):
Shit piss fuck cunt cocksucker motherfucker and tits. Fuck you, fuck off, go the fuck away, and don't make me tell you again.
Am I doing it right? Thankfully, I live in a country which, in theory, protects offensive speech.
I done me best when I was let. Thinking always if I go all goes. A hundred cares, a tithe of troubles and is there one who understands me? One in a thousand of years of the nights? All me life I have been lived among them but now they are becoming lothed to me. And I am lothing their little warm tricks. And lothing their mean cosy turns. And all the greedy gushes out through their small souls. And all the lazy leaks down over their brash bodies. How small it's all! And me letting on to meself always. And lilting on all the time. I sprang with the quickness like lightning, disappeared. I whistled for a cab and when it came near, the license plate said, "fresh", and it had dice in the mirror. If anything, I could say that this cab was rare. But I thought, "Nah, forget it"--"Never gonna give you up. Never gonna let you down. Never gonna run around and desert you, yo home to Bel-Air."
Sniffer of carrion, premature gravedigger, seeker of the nest of evil in the bosom of a good word, you, who sleep at our vigil and fast for our feast, you with your dislocated reason, have cutely foretold, a jophet in your own absence, by blind poring upon your many scalds and burns and blisters, impetiginous sore and pustules, by the auspices of that raven cloud, your shade, and by the auguries of rooks in parlament, death with every disaster, the dynamatisation of colleagues, the reducing of records to ashes, the levelling of all customs by blazes, the return of a lot of sweetempered gunpowdered didst unto dudst but it never stphruck your mudhead's obtundity (O hell, here comes our funeral! O pest, I'll miss the post!) that the more carrots you chop, the more turnips you slit, the more murphies you peel, the more onions you cry over, the more bullbeef you butch, the more mutton you crackerhack, the more potherbs you pound, the fiercer the fire and the longer your spoon and the harder you gruel with more grease to your elbow the merrier fumes your new Irish stew
Solved in approximately 42 seconds.
Made perfect sense over here. Not sure what your issue with English is. It's a bit flowery, but it's coherent.
I'm sorry, could you say that again?
Learn how things work. Learn why things work. Build things, experiment, and never make an assumption without clearly identifying it as such, even if it's only a mental note.
Don't take someone else's word--look it up and verify it. Try it out. Play with concepts. I don't recommend using your own crypto in production (at all, since the odds are against you being a qualified cryptographer), but implementing known algorithms for educational purposes and then running attacks against them will give you a much better idea how everything fits together and what should and should not be done.
Shit, is that too hard? Sadly, it probably is. Also, don't give me the "I have no time" excuse. Stop watching your fucking boob tube and spend that time educating yourself and helping those around you.
FOAD, preferably by DIAF.
I browse at -1 and I mod by quality and relevance of comments. If you're moderating by username, AC or otherwise, you're effectively performing a continuous ad hominem.
And who pays for his medical injuries if he gets injured while trespassing in an abandoned building that may well be structurally unsound or otherwise hazardous?
How about personal responsibility? If you break into something, and it falls apart on you, guess whose fucking fault it is? YOURS.
This nanny-state shit has got to go. By the time you're 18, you ought to know damn well you shouldn't be breaking into shit, and if you do, and bad things happen, they're on your head. Of course, often that isn't how it works out in court, but that's how it should. Unsafe or hazardous conditions exist in much of the world, and we shouldn't have to put a guard, sign, fence, and attack dog around every single little thing to prevent people from injuring themselves through their own fucking stupidity by being where they never should have been in the first goddamn place.
Done ranting.
Does the probability of an event happening change the ethical considerations?
For example, if you were to calculate your odds of being caught and severely punished embezzling from a business and found them to be extremely low, would it suddenly become ethical to embezzle?
You ought to read Hard-Boiled Wonderland and the End of the World by Murakami. I think you would enjoy it.
Quick summary from Wiki:
The story is split between parallel narratives. The odd-numbered chapters take place in the 'Hard-Boiled Wonderland', although the phrase is not used anywhere in the text, only in page headers. The narrator is a "Calcutec", a human data processor/encryption system who has been trained to use his subconscious as an encryption key. The Calcutecs work for the quasi-governmental System, as opposed to the criminal "Semiotecs" who work for the Factory and who are generally fallen Calcutecs. The relationship between the two groups is simple: the System protects data while the Semiotecs steal it, although it is suggested that one man might be behind both. The narrator completes an assignment for a mysterious scientist, who is exploring "sound removal". He works in a laboratory hidden within an anachronistic version of Tokyo's sewer system. The narrator eventually learns that he only has a day and a half to exist before he leaves the world he knows and delves forever into the world that has been created in his subconscious mind.
The man who buys the meat is brother to the butcher.
If you aren't at least willing to do it yourself, and simultaneously complain about conditions and cruelty while eating McNuggets, then you're a hypocrite. Vote with your actions and stand by your principles, assuming you have any.
Me? I eat meat. I don't hunt (no need to) or slaughter animals, myself, but I understand the process required to bring food to me. Were I suddenly required to do it myself, I would do it myself, not stop eating meat.
Er, one day a week, I work from 0730 to 2200. Stupid typos.
My sleep schedule tends to rotate if I don't have any fixed obligations (say, on vacation). I'm naturally a night person (worked overnights for years and really enjoyed that), but I tend to have a daytime awake phase and a nighttime awake phase.
With my current work, I'll go to sleep at 0000-0130, wake up from 0530-0630, work until 1600, come home, nap from 1900-2100, read the news, putz around, and start all over again. One day out of the week, I work from 0730 to 2000, with a couple of 30 minute breaks at 1230 and 1600.
If I don't have any obligations, I tend to sleep 4-5 hours when I get tired, wake up, and work for 6-8 hours, and then go back to sleep and do it again. This causes my sleep/awake times to rotate around, which I don't mind, but other people think I'm crazy. I'll also tend to wake up with the sun and go to sleep when it gets dark, which causes me to be awake much longer during the summer than the winter.
4 hours of sleep is enough to function on, but I prefer 5-6 hours if I have to be awake for an extended period, need to do heavy thinking or strenuous work. I can't sleep for 8 hours at a stretch. I'll just keep waking up every half hour.
JavaScript isn't necessarily such a bad language; otherwise, we wouldn't see Node.js gaining so much popularity.
Bandwagon appeal. With your UID, you ought to know better. Provide a technical argument and/or step away from the keyboard until you've thought it over. Note that I'm not saying there isn't a good reason--only that your given argument is crap.
I would nearly have lost my coffee via my nasal passages. Are the Brits really economically, technically, and industrially capable of doing this anymore? Sure, they have some large aerospace companies, but at a glance, they seem to be focused mostly on conventional passenger flight.
Sometimes I wonder if we (USA) still are. Then, I'm reminded that we have SpaceX. They're at least a small glimmer of hope.
Of course, I'm probably just out of touch with this planet.
You realize you can download software (used to be books) which lists the key bittings for blind codes for basically every manufacturer, except the ones that require you to mail in an ID card issued with the lock (and those are expensive)? This blind code is usually printed somewhere easily accessible.
Right?
Physical security is generally a joke. I place more stock in cryptography properly implemented than any pin tumbler, wafer tumbler, disc, or combination lock (safe or otherwise). Hands down. (That said, my trust in the security of computational hardware is pretty low, and properly implemented has a very high bar.)
Also, when you set up a master keying system, you inadvertently create keys out of the system that still function to open locks, because you need to break up the existing pins into a stack with multiple shear lines.
Want it done right? Do it in depth. Locks are there to keep honest people honest and slow criminals down a bit.
The Soyuz-FG has an incredible record given the difficulty of rocket science. I wonder if its successor will fare so well.
Sorry, it's ~T+2:23 (3:24 is the point in the video I linked elsewhere in the comments).
At 3:24, if you step frame-by-frame, you can see what looks like a large object flying up away from the rocket. That might be the capsule. If it survived, that would be amazing.
Yep, that seems to be it.
There was an overpressure event in the upper stage liquid oxygen tank. Data suggests counterintuitive cause.
You're right, it looks like something venting out the side (you can see a little cloud there). Then that area comes apart. The flames from the engines appear to flare up, suggesting oxygen? Then, it starts burning hotter in the area you mentioned, looking like maybe it's burning it's way down into the lower stage. That fire gives out, but it's immediately followed by RUD.