Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Thanks for all of your feedback on this bug. We’ve heard you loud and clear.
We plan to re-enable ext2/3/4 support in Files.app immediately. It will come back, just like it was before, and we’re working to get it into the next stable channel release.""
Link to Original Source
The link that supposedly refutes the argument that people are paying for things they wouldn't otherwise pay for doesn't actually refute anything. Rather, it characterizes the current situation as "socialism"; "Cable TV is socialism that works."
I do not want to contribute to ESPN. Nor the myrid "shopping" channels. Or the "Christian" networks. Or any of the other dreck that pollutes this world. Even if that means the things I do want aren't as well subsidized for the lack of fuhtbawl knuckle-heads.
Whatever.... I can't remember how long ago it was that I last paid a cable bill. My vote has been cast. Join me and cut these bloodsuckers off. You won't miss it.
Link to Original Source
Link to Original Source
As far as I am aware the highest radiation dose
Naturally the `record' must be limited to the subset of known cases. I've been studying the history of Soviet nuclear science and industry for a few years. Things went on in the Soviet Union that beggars the imagination, as they say.
When the waste storage tank blew up in Mayak in 1957, 90% of the high level waste fell in the immediate vicinity. That's 90% of 740 PBq (740E15 decays per second) within about half a kilometer radius, in which there were certainly some number of workers, this being the most urgent period of nuclear weapons development.
There were criticality accidents at Mayak that killed people as well; the Review of Criticality Accidents (2000) mentions seven incidents at Mayak and eight at other Soviet sites.
Then there is Chernobyl. Shortly after the explosion soldiers on the grounds of the plant policed up pieces of graphite and other debris, including fuel, from the reactor core with simple tools, bare hands and no respiratory protection . They were breathing particles of heavy metal isotopes so "hot" that they floated through the air on their own thermal output like little balloons. They were treated as military casualties and their numbers are not publicly known.
The worst case of radiation exposure took place in the Soviet Union. We do not know the circumstances, how severe it was, how many it killed, when or where it happened, but that it did is a metaphysical certitude.
1. The Legacy of Chernobyl, 1992 Medvedev
or does everyone get 140 characters?
Everyone gets 140 NCF normalized UTF-8 Unicode code points. Characters, iow.
This should be rule number one for this type of application.
Perhaps it should be rule number one, but actually it's Rule 16.2 of MISRA-C:2004 (Motor Industry Software Reliability Association, Guidelines for the use of the C language in critical systems):
Functions shall not call themselves, either directly or indirectly.
The rule actually appeared first in MISRA-C:1998. Each rule is accompanied by a detailed rationale that I will not reproduce verbatim here as the standard is not open; one must pay for the privilege. The rationale for 16.2 is that recursion may cause stack overflows. I only cite the rule itself because it appears in public testimony and also on the (first) page linked by this story
Because MISRA also disallows constructs such as function call indirection, self modifying code, etc. a compiler is entirely capable of detecting recursion and reporting the violation as an error. MISRA compliant compilers do exactly that.
Yes Virginia, the largest auto manufacturer on Earth ignores the very thing that was designed to prevent simple, common, easily predictable failures such as stack overflow despite the fact that the cost of compliance is much, much smaller than a rounding error for an outfit like Toyota.
Also, despite the fact that Industry dutifully identified this specific problem in a published standard at least 16 years ago, compliance is apparently not yet a requirement by government regulators. I suspect they're too busy investigating child seat manufacturers or Telsa batteries or whatever other politically high profile crisis that giant, engineer-free gaggle of NTSB lawyers fill their bankers hours with.
And that, kind reader, is why we must outlaw meat.
but I'm surprised so many attribute that to malice.
My accusation was limited to a lack of understanding; never attribute to malice that which is adequately explained by
The immutability of reader comments has always been a prized feature
Amen. Accountability. It's always been obvious to me why simply revising comments isn't tolerable and I'm glad that view predominates.
And AC isn't a counterpoint to accountability either, for whomever might want to throw that one back at me; AC elevates attributed comments, on several levels.
I'm pretty sure contemporary ideas about UX design are inappropriate for Slashdot. The one or two sentences that Twitter/Facebook/WhatsApp accommodate won't work here. This place indulges people that like to write, and people that don't mind lengthy posts.
The beta site shows a serious indifference to that; the amount of wasted space is just amazing. Fully 45% of the comments view is just empty, half of it gone to the infinitely long side bar that Beta fails to wrap into. No one that understands what this site is for could possibly have made that basic mistake for as long as Beta has been in the works.
Bootstrap et al. don't deal with "long form" threaded forums, so that design mentality won't work.
Here is a possibly novel idea that will actually be appreciated by at least this contributor, and probably most others; comment editing with revision control (a la Wikipedia.) It has to be revision controlled or the trolls will abuse editing. Allow readers to punish such trolls with moderation while the rest of us get the benefit of correcting minor mistakes.
There. That wasn't hard. A real improvement that caters to actual contributors, as opposed to hypothetical users that want to scribble a grammatically challenged half sentence 20 times an hour and don't read.
Anyhow, thanks for the step backwards on this and your participation in the conversation. You all could have gone bull-headed and made this situation even worse. So good on your for that.
None at all.
And yes, beta has serious problems. Regressing to having to bang on the "Load More..." button instead of "Load All Comments" while not logged in is one glaring example. The fact that comments don't flow around the end the right side ad bar is another.
This is not Twitter. People write lengthy comments here; please don't piss away space with huge margins and poor layout.