685 karma · joined January 13, 2015
I never said anything about "gun free zones". I'm not sure what they are, I don't know how effective they are, but I don't see how they hurt either. To me, it seems like more guns, easier and cheaper availability of guns, more destructive guns, less strict and less comprehensive / universal background checks are all things that lead pretty clearly to more gun violence. That's why I'm against those things. I'm willing to change my mind. But the NRA is too busy disparaging victims of gun violence.
I really don't see how arming teachers helps. I've heard arguments for it, but those arguments really just don't ring true to me, and it seems that more guns will lead to more violence. I haven't read studies that seem credible and support what you are saying. Do you have any? I've looked, and there is a lot of really contradictory stuff out there. I'm willing to support anything that will reduce gun violence, in general.
I've been thinking about this thread for a while, and I think what bothers me is this. If you think expanded background checks (for example) will help reduce gun violence, why will you only support it if you get something else in return? Why can't we find things both sides thinks will help, and enact those things? Why must you hold those things hostage until you get some other thing that the other side fears will make the situation worse?
"I'll agree not to shoot your kids today, but only if you let me beat up your cousin instead." That's more or less what your argument sounds like to me. Can we agree that gun violence is a problem in the US, on a level vastly higher than many other parts of the world? Can we talk about how to move towards a society with less gun violence? Let's work together to find things that will help reduce gun violence. I'm willing to give up a lot of things I care about to move that way. You seem to only be willing to head that direction if you get something else you want in return. And it's especially jarring when the thing you want in return seems a to always move things back in the exact opposite direction, expanding access to and availability of guns.
This is exactly my point. You point to extremism as justification for yet more extremism in the opposite way. This won't end well for anyone. I'm not sure how, but as a society we need to find a way just sit down and walk things back. I'm willing to work towards a compromise. It seems you would rather not budge, and so the extremism continues.
There are plenty of people like me who don't care about 100yr old rifle historians, or hunters, or sport shooting, or the rest. We just want our kids to not get shot, and think that the current level of gun violence is far too high. Where can we turn to? Gun lovers and the NRA specifically don't seem to be able to offer any response at all beyond "my cold dead hand" and "don't give an inch".
As for the argument that the ban is a bad idea because it is ineffective. I don't know if the ban will help. I'm not an expert, though it seems pretty obvious that our current situation isn't working so well. Do you think a ban will increase gun violence? How sure are you?
Can't we all agree to get the extreme videos off youtube, before we worry about some corner cases with niche communities? Because if some random guy's fascination with 100yo rifles means kids in my son's classmates are more likely to shoot the place up, then screw that.
I was trying to specifically call out the parent's reaction. Not "youtube is part of the problem and yes we should do something about and yes banning most of this stuff is reasonable but but maybe youtube could carve out some careful exemptions for my harmless hobby". It seemed dismayed at even the concept of any limitations whatsoever.
Conservatism, I though, was all about making slow and slight tweaks to society, rather than radical changes. But refusal to allow even the slightest evolution or deviation on some issue, like gun rights, leads to the opposite: at times it feels like we are heading towards outright civil war.
In the face of an obvious societal problem like gun violence, real conservatism would say sure, lets make some small changes to gun regulation, see how that goes for a few years or decades, then re-evaluate our position to see if society is better or worse off. Instead, seemingly obvious minor tweaks to gun regulation get cast as the first giant step towards impending repeal of the 2nd amendment. Maybe we are past the point of no return, I don't know.
Just as a direct anecdotal comparison, in very recent years our school tried to hire in both math and CS. For math, there were nearly 200 applicants, most of which which were at least superficially qualified, and 30-40 of which were deemed "top contenders". These candidates were from top universities, with stellar track records, multiple awards, a few years of postdocs at great schools, multiple papers in top journals, and recommendations saying things like "best postdoc I have seen in 30 years". We are a good, well-known school, but this was still surprising to me. It certainly appears there are plenty of very strong math candidates and few math positions available.
For the CS position, there were fewer than 25 applicants total in the pool. Two thirds were effectively spam (e.g. foreign applicants only minimal English language skills, applicants who think we are a company or an R1 university with grad students). Half the remainder were people with degrees only tangentially related to CS and/or no formal training in CS, but who apparently can't get teaching jobs in their field. Of the four or so candidates left, most had multiple tenure-track offers on the table before we even had a chance to talk with them on the phone. Others dropped out before we could schedule an on-campus interview.
All our peer colleges are telling us they are seeing the same things.
So yes, I would completely buy the premise of the article.
[1] https://cra.org/crn/wp-content/uploads/sites/7/2017/05/2016-...
Aside from outside uses (decks, patios, landscaping etc.), pressure treated lumber of one sort or another might be used for a few select applications for home construction, such as sill plates or a bathroom subfloor. Nearly all of the wood used for regular homes is non-pressure treated, at least everywhere I have seen in the US.
Or writing an essay with the pencil tool in mspaint while using a 50-radius sized brush.
Hi! Serious question: can you explain more about what you mean here? I'm having trouble imagining what "development platform" means here, or how/why a division would use Ethereum as one. I'm guessing you mean something other than software development?
Yes, in the bad old days, we had dozens or hundreds of different drivers for specific network cards, serial cards, parallel port chips, audio cards, floppy controllers, disk drivers, etc., plus the tangled mess of scsi and ata/sata/pata storage stacks, tcp/ip/tokenring/ethernet/netbios/smb/appletalk network stacks, tty/vtty/serial terminals, and so on. Bugs in the higher-level stacks, like sata, would be impact very broadly. But a bug in one specific network card driver would, generally, only affect the subset of people who actually had that specific network card. And many of those old drivers were not really all that complicated, because they were specific and narrowly tailored. Buggy as anything too, of course, and didn't get much scrutiny due to the huge variation in software.
Now everything is subsumed under a massive IO controller-hub chip driver. At least the last time I checked, all those tangled upper-level stacks are still there, but they are just entwined with a hugely complex mess of usb/thunderbolt/usb-c mess. So you'd still have all the complexity of a sata stack, but that's nested on top of a scsi stack, sitting on a PCI stack, all nested inside a USB-C stack.
For example, <newline>~~~~ will send <newline>~~~ to the remote side.
Yes! As an author of many CS conference papers, a few CS journal papers, and a few papers in other related fields, piracy affects me. It has been entirely beneficial, and I completely support sci-hub.
Collaborators, other authors, and other researchers have been able to read and find my work more cheaply and easily than they otherwise would have. Some would not have paid to buy my papers sight unseen. Some can't afford to buy them. A larger audience is always good for me.
I have also never directly earned even a single cent from any published work of mine. No royalties, no copyright payments, no publisher payments, etc. And I've paid thousands to publishers over the years to publish my own work.
`--preserve-root'
Fail upon any attempt to remove the root directory, `/', when used
with the `--recursive' option. This is the default behavior.For (1), for curiosity sake, I tried benchmarking the cuckoo.go file you posted. I'm curious if these numbers are in line with what you found. The first test I did was a Rand test, Putting 10,000 random string values under random string keys, then Getting the same 10,000 keys, then Getting 5000 more random keys. The first line below uses default code you posted, which uses
type keytype string
type valuetype string
The second line specializes the code to just using the string type directly for keys and values. The third line uses interface{} instead for values, which is the code style HN doesn't like. BenchmarkRandInsert-8 100 13474408 ns/op
BenchmarkStringStringRandInsert-8 100 13585071 ns/op
BenchmarkStringVoidStringRandInsert-8 100 14126666 ns/op
That third line shows the cost of casting to/from interface{}. The difference in the code was about as you might expect, with the "void" example needing a cast on each put and a cast on each get.If I use uint32 for value instead, I get:
BenchmarkStringIntRandInsert-8 200 9431584 ns/op
BenchmarkStringVoidIntRandInsert-8 100 10485785 ns/op
The 9.4ms result is using a version of your code hand-specialized for string key and uint32 values. The 10.4ms result uses interface{} for values.I ran a sequential-insert test as well, with keys and values generated sequentially instead of randomly. The results are much the same, though the cost of casting to/from interface{} seems to get mostly lost in the noise.
BenchmarkSequentialInsert-8 100 12185272 ns/op
BenchmarkStringStringSequentialInsert-8 100 12233946 ns/op
BenchmarkStringVoidStringSequentialInsert-8 100 12543980 ns/op
BenchmarkStringIntSequentialInsert-8 200 8823747 ns/op
BenchmarkStringVoidIntSequentialInsert-8 200 8709242 ns/op
I also tried some tests using uint32 as the key type. This int key specialized version is 3x faster than any of the string key versions, but it's not really a fair comparison... a small part of the code is specific to string keys (getinthash), so it's not as obvious what the generic equivalent of that function would be. The keys need to be Hashable or some such, not just interface{}. I'm also allocating and formatting random strings in one case, vs just picking random numbers in the other case.I didn't find the interface{} casting in any of the above code too horribly "gross", just a bit ugly, but that's entirely subjective. Yes, all of the cuckoo versions seemed about 30% slower than the corresponding builtin map type, but my benchmark numbers don't show if that is the price of boxing, of supporting concurrency, or maybe function call overhead, or something else. I'm guessing you did more detailed benchmarks that point to the source of the slowdown.
One last comment: keytype and valuetype really need to be exported, don't they? I wasn't able to use the library without changing them to exported symbols.
And that's just in your first sentence.
My impression has always been that the Go core team is very open to the possible addition of generics, but also very wary of the very real downsides that generics have. Nothing I've ever seen from Rob or other core team members contradicts that. I'm open to citations if you can give any.
In contrast, a lot of Go users and proponents seem to be vehemently against generics, for wildly differing reasons. Some seem to be against them just for the lulz, others for crazy conspiracy theory or obscure philosophical reasons.
Me, I miss generics sometimes, but not enough to get riled up about it. I hope the Go folks come up with a clean, simple, and efficient way to get them, but until then I'm happy with the features Go has.
Why would one be forgetting and grepping for tmp? That's the kind of variable that would be inside a function (so max one or two screenfuls, according to the guidelines here), and more realistically would usually be declared and used entirely within the same block of a dozen or so lines of code. Nobody is going to forget whether it is temp or temp while reading those 12 lines of code. And using temporary is just silly -- I can't think of a single time I've ever seen that used in any language.
> How many nails does it take to build a house? a) hundreds b) thousands c) millions d) billions
> How many rooms are in a house? a) tens b) hundreds c) thousands
> How thick is a house wall? a) inches b) feet c) miles
func Fahrenheight(f int) Celsius {
return Celsius(5*(f-32)/9)
}Also, assuming what you say is true, was this known at the time? Because that would seem to make a big difference -- opposing dumping "sludge that's so toxic on land" into an environment where you don't know the effects seems to be more than "PR and feelings", but rather caution and prudence.
> Number of underfull warnings : 5 > Number of overfull warnings : 0 > Number of undefined references : 0 > Number of missing citations : 0
> E37: No write since last change (add ! to override)