Be a shame if someone looked up this on Google and found that it's not as outsized as some think
1,405 karma · joined May 18, 2009
I will often watch movies with them one, it might be that I grew up with them as my father is deaf; but I find they give me more information than speech alone.
I guess my counter would be:
* It was solved at a greater expense of human life, its easy to say "those people would have died" but that is harder to prove ethically. Could the excess deaths have lived on _longer than a flu season_?
* Is there a good argument that it is in fact over in Sweden?
* Are there other variables that might have made Covid-19 not so bad in Sweden?
If I was to take more direct counters to the article:
> I am willing to bet that the countries that have shut down completely will see rates spike when they open up. If that is the case, then there won’t have been any point in shutting down in the first place, because all those countries are going to end up with the same number of dead at the end of the day anyway.
Maybe, but that could also be a case of thinking that the death rate is a fairly simple linear model, which would fly in the face of the various epidemiological models that we use (not just for covid but since the 1920s)
> No, because influenza has been around for centuries while covid is completely new. In an average influenza year most people already have some level of immunity because they’ve been infected with a similar strain previously, or because they’re vaccinated.
Is Covid-19 completely new? By this reasoning it would as stated be more infectious due to a lack of known immunity. With this line of reasoning why wouldn't a _different_ cornovirus also give a more uniform immunity? Why would a novel Cornovirus strain have a greater impact over a novel Influenza strain?
I could go one but I feel like I am sniping.
Personally I dont think the world wide response has been great, I do think we have overreacted but I also would argue that its not just another influenza and should be ignored as such.
https://www.medrxiv.org/content/10.1101/2020.05.10.20096909v...
https://covid19-projections.com/denmark vs https://covid19-projections.com/sweden
Its also possible Sweden just got lucky with the prevalent strain https://www.biorxiv.org/content/10.1101/2020.08.03.233866v1....
I would love it if Sweden was right and tackled this in a way that does look like a seasonal flu, but I think the science is still out on that. It does seem the science points mildly towards it being quite as deadly as initially thought, but I would not the Swedish death rate a total win.
<snark> Forget all that Sweden is the best approach, we should copy it in America especially the very solid social health care system :) </snark>
> Nowhere did I say you should be on one incredibly large server, nor that you should have a single point of failure. That wouldn't be simple, either, because it would fail to support the prime directive, or would require a great deal of gymnastics to. It's about balance. You don't need thousands of servers to make a reliable system.
Heh those things go offline every night for 2 hour maintenance.
Also fun when those nice single points of failure crash (they do)
Source: work at a shop trying to _get out of_ greybeard mainframe to get more reliablity
It is better at handling recursive queries, and logical inference than SQL. On the flip side SQL can be better at more set style operations (for instance windowing functions are painful in datalog).
It is different tooling, essentially it comes down to do you want to extract answers from your data with varying relational algebra but holding the logic the same (SQL), or keeping the relational algebra the same but varying the logic (datalog).
Works great
From the comment right under the picture I took
> yeah, pretty typical function prolog, what's the question ?
Except we know it is not.
I am more saying to people be careful pushing any old binary blob through capstone without considering what it might produce, I get this at $DAYJOB where people disassemble VAX from things that are just data.
For example here is a "program" except it's really a meme gif off my phone. https://imgur.com/gallery/hoDKeC9
You are hilariously misinformed. I am 3.5 years and waiting on an EB2 and I am British, I know Caltech professors who took 3 years to get on EB1.
Part of the issue isn't entirely the government but also the cottage industry of legal firms. These firms (at least in my experience) can take _longer_ than some of the government steps.
[Out of band verification] using SMS is deprecated, and will no longer be allowed in future releases of this guidance
http://www.level3.com/~/media/files/brochures/en_secur_br_dd...
I found this trick, we used to play doom and rise of the triad with this and some other glue. I am surprised this trick still works so well for foxing security checkers
Realise that those of us that do use it, are fully aware that it is a hack, and that we should be doing cleaner things. However know that those cleaner things _dont exist_; and that you, Dear application developer might not quite realise some of the shadow puppetry in making your favourite library work, please lay off the bile.
As others have said, this blog post stops short, the full quote is part of a very long and ongoing process to rid ourselves of Unsafe, replacing its majors usages with new API's.
This is a process Oracle started last year after the previous sun.reflect.Reflection.getCalleeClass mess. Yes, it no one should have been using an internal class. This method did not go away; it was made only available to the JVM internals, locked out from end users. The upshot of this was that, with no sane alternative, suddenly logging became between 2x and 100x more expensive where class names become involved. The JDK team somewhat back peddled on this change, and we are stuck here in a strange limbo land.
Was it right of Oracle to do this? Absolutely, everyone who goes down the internal package route is fully aware that these are open-state secrets, sure we all know them, but we should not be talking about them. Support for these damn things requires version to version checking, hideous reflection hacks and being prepared to read a lot of JVM source code for when bugs occur.
In light of all of this, and being the general level of awesome the JDK folks are they started a very direct community outreach to remove safely Unsafe. Last year they publicly asked people on the mailing list, and privately via email to do a survey (http://mail.openjdk.java.net/pipermail/core-libs-dev/2014-Ja...) on usages of Unsafe. I know this because I got an email from Paul Sandoz asking me to comment on Unsafe abusages. Out of previous thinking from the JDK folks, as well as from the aforementioned survey, we have a bunch of JEP's for improving things regarding Unsafe.
Where things have gone slightly sideways is that we have, currently no unified working group to deal with these changes. What this document is, is a proposal to make a working group, focused on getting the right changes into the JVM. In the same ways as Project Jigsaw is for modularising the JVM (and is indirectly responsible for removing Unsafe), or the MLVM project handled making the VM better support other languages.
Unsafe is dead, long live Unsafe! I fully expect that we will achieve the right changes in during Java 9 to allow those of us that need to break the rules, to do it in a supported fashion. I am _looking_ forward to the day when I can do setMemory or getAndSetInt via a supported API, and not one where I have to know the words Unsafe.theUnsafe. The above is a storm in a teacup, its open-source democracy at work.
import pandas as pd
from sklearn.linear import SVC
df = pd.read_csv('/home/me/programming/data.csv')
y = df['label']
X = df.drop('label', axis=1)
clf = SVC()
clf.fit(X, y)
This is not to say that R is a bad language, or that R does not have equally nice API's for this stuff; but I feel that in your case its a familiarity of language thing.
I love the fact that hypothesis is a proper quickcheck and not just the fuzzing part, and that the author has a crazy stack-based-vm-language-testing thing project that might be useful.
I have been using this library with py.test for 6 months now and its been a godsend.
If I ever meet the author I would buy him beers.