Not sure if you know this or not but they're already pivoting to avocados...
270 karma · joined January 27, 2015
I guess I see information (esp with regards to video tutorials/demos) as agnostic. If you're reading a tutorial online, there's no telling whether the person who wrote it was completely naked while doing so. Does the information change simply because you thought they should at least throw a robe on before trying to share info? As long as she's sharing good info, I don't see why it matters what she's wearing. And no, I cannot see what issue other people have other than a difference in taste (which, again, has no bearing whatsoever on whether what she's sharing is factual and helpful or not...).
That said, I think the slutshaming you pointed out is just as damaging as what's going on in Wu's case. Who gives a shit if @sexyengineer is wearing a speedo in all of his tutorials? The point is the information and if he's not sharing bad info I don't see the problem other than the fact that you and I have differences in taste.
I.e., don't yuck in other people's yum :)
Where in "Akins also argues that the district court erred by granting the motions todismiss and for summary judgment filed by the defendants and by denying his ownmotion for partial summary judgment" is there anything about filming anyone?
But again, the judgement wasn't at all about him filming public officials, only about whether or not the judge should've presided over the case.
"The hypothesis turned out to be correct: V-Max bullets started fragmenting within the first sheet of drywall and completely blew to pieces on their way out of the second sheet, leaving dramatic craters." http://how-i-did-it.org/drywall/results.html
Relevant excerpts:
"Tests 1-6: Bare gelatin, heavy clothing, automobile sheet metal, wallboard, plywood, and vehicle windshield safety glass, were shot a distance of 10 feet from the muzzle."
"Tests 7-13: All involved shots through heavy clothing, safety glass and bare gelatin at 50 to 100 yards, concluding with internal walls, external walls and body armor at 10 feet."
"The Bureau’s research also suggests that common household barriers such as wallboard, plywood, internal and external walls are also better attacked with pistol rounds, or larger caliber battle rifles, if the objective is to "dig out" or neutralize people employing such object as cover or concealment."
"If an operator misses the intended target, the .223 will generally have less wounding potential than some pistol rounds after passing through a wall or similar structure."
Really unsure as to how you could possibly have come to that conclusion after reading the link....
Edit: now that I think about it, people unfamiliar with ballistic testing might not know that gelatin is almost always used to find out data about efficacy downrange regardless of what other things are being tested, so I can kinda see how you might take my comment at face value and feel that it was immediately contradicted if you didn't read the entire summary (which is a bit long).
[0] http://www.olyarms.com/index.php?option=com_content&task=vie...
I trust that you're a psychiatrist but you could be spewing old or incorrect numbers just as easily as anyone else who may unknowingly make a mistake.
Pretty sure it's because they assumed IC was Individual Contributor but to downvote the "least common answer" is weird seeing as how, in this case, it's the source...
[0] https://en.wikipedia.org/wiki/Floppy_disk#/media/File:Image3...
It definitely should not have been requested of them, but it's possible laws were broken.
This is kinda the point of OP, police violence has become so common-place that we take it as normal happenstance when it's used. There's an air of expected guilt for anyone on the receiving side of the violence but no doubt whatsoever on whether the violence was necessary in the first place.
That said, I think you're missing the point most others are making, which is that your argument is missing the point others are trying to make, "where there's a will, there's a way" or perhaps more aptly, "prohibition doesn't work" as we've seen countless times through history.
edit: I also think at the heart of what everyone else is getting at is perhaps anger at the fact that while they feel their argument is perfectly logical ("prohibition doesn't work"), they know, like you, that it's not very convincing (again, look to history, we've had a 4 decade war on drugs after several failed prohibitions throughout our country's history that did all of nothing for stopping revenue streams and usage of prohibited substances).
That said, you're going to have to come up with an argument stronger than "this was forked ages ago" to suggest Dragonfly and FreeBSD are different enough to warrant thought. Ubuntu forked before 2004 and you don't see anyone being called out for comparing it to Debian.
Then the folk whom build the processors/architecture/assembly languages (and open source advocates when businesses ultimately ignore LLVM for a bit) will be writing the conversion from IR down to some specific machine code. This allows Intel to convert the IR line "COMPLICATEDFUNCTION $r2 5" to some advanced x86 call that has some significant speed or memory increase and is only one line while TI can still call the 26 lines of MIPS they need to call and both will be semantically equivalent.
That way you can, from the the software side, be relatively agnostic with how you're writing code and the chipset side is able to get every ounce of optimization using advanced functionality (if available). More importantly, software side is then able to ignore any processor features (be they speed ups or slowdowns) because every chipset manufacturer should have some toolset to convert your IR down to the best machine code they've got based on some desires (speed, space, power, etc). Inevitably, there will still be differences in performance between chipsets but being able to build down to IR (even with performance issues for some chipsets while everyone gets on board) and not some large set of assembly languages should be very nice.
I don't necessarily agree nor disagree with the particular event at hand being labeled as a terror attack, but I'd implore you to analyze your homebrew definition.
What's added? What's left out? Why should the "mainstream" definition be changed? Is it not specific enough for the people you think we should target with that term? Is it too specifically targeting people you don't think we should care about?
Also, I'm relatively positive that JJ (in the sci-fi works he actually, well, worked on), himself, knew nothing (see Armageddon for sources) and that his script supervisors dealt with any discrepancies with reality JJ had.
At least, I'm assuming that's what OP meant. Not simply that "free nights and weekends" would be anti-net neutrality on its own, but that it could very easily be made more proprietary than it initially sounds. And we've seen it done in the past when free nights and weekends were were restricted to those within your telco, the x-amount of people within your network that are free to call[I believe AT&T made it 10?], the free mobile to mobile that was eventually restricted to free mobile to mobile only within the same telco again, etc., etc.
That said, I think the biggest difference is the parity between OSes in in the 70s vs ARM/Intel's current dominance. That's definitely going to make it more difficult to get people to adopt RISC-V. I'd imagine if there was any likelihood that IBM, RedHat, Google, or Intel could customize a RISC-V chipset to outperform (whether it's TWP, flops/sec, whathaveyou) any current offerings they'd pour dumptrucks of money into it just the same.
They aren't suggesting using compile flags requires code changes...