Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lvh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
53 ms
·
541.
▲
by
lvh
7y ago
The 13.8Gy claim is made by estimating, calculating and then confirming by experiment how quickly wear and tear works (the primary mechanism is nanograting, and the primary contributing physical quantity is temperature). It then specificall
542.
▲
by
lvh
7y ago
5D has been a term of art for years, and was not made up by this article. https://en.wikipedia.org/wiki/5D_optical_data_storage
543.
▲
by
lvh
7y ago
What is the difference between dimensionality and degrees of freedom? The standard definition of degrees of freedom is "number of variables that make up the state of the system" and the definition of the dimensionality of the stat
544.
▲
by
lvh
7y ago
Yes, 13.8Gy is the approximate age of the universe and yes the researchers used that number. But it's not like they made this up and conveniently landed there: they computed a range of options and worked back from that specific number
545.
▲
by
lvh
7y ago
Yes, 13.8Gy is the approximate age of the universe and yes the researchers used that number. But it's not like they made this up and conveniently landed there! Turns out the biggest decay factor is nanograting and the biggest contribu
546.
▲
by
lvh
7y ago
I agree that’s probably what’s going on, but “the university is making stuff up to look busy” and “no sane engineer would say this” and "clearly they made this up, 13.8Gy is mighty convenient" isn’t exactly a charitable read.
547.
▲
by
lvh
7y ago
It’s perfectly reasonable to say you’ve increased dimensionality when you find a new physical property to store things with. If a CHS-addressed HD tomorrow starts using opacity or depth as a way to store 2 bits in each, obviously the dimens
548.
▲
by
lvh
7y ago
And yet, in machine learning we regularly talk about dimensions 100 and above! Just because they eventually map to three special dimensions doesn’t mean it’s not useful to talk about the different degrees of freedom you’ve managed to use fo
549.
▲
by
lvh
7y ago
The university in question is Southampton. Hardly a Christian fundamentalist stronghold. Meanwhile, there is a tradition of using the Bible for new printing media, including one of the first printed works, the Gutenberg bible.
550.
▲
by
lvh
7y ago
The treasury is not out “a few million”.
551.
▲
by
lvh
7y ago
Nothing: but that doesn’t tax all billionaires equally. The point is that you want George Soros and Grover Norquist to pay.
552.
▲
by
lvh
7y ago
Small numbers with many representations are much more common than the full width ones.
553.
▲
by
lvh
7y ago
Yep, but back then I think it was just commercial -- I believe everything got upstreamed. (The nice thing about Veertu using HVF was that it could ship a virtualization product in the App Store.)
554.
▲
by
lvh
7y ago
VMWare Fusion and ESXi support paravirtualized IO, but virtio is a specific KVM technology. Xen paravirtualized IO is similarly the same idea but not compatible.
555.
▲
by
lvh
7y ago
Real CSPRNG designs are a bit more complex, having at least a state (like a hash function) but also an output mechanism to let it generate more bits. One way to do that is to “compress” all your input entropy into a single state, and then u
556.
▲
by
lvh
7y ago
That also identifies the typeface, since there’s only one typeface the National Parks use that is carved using a router bit. (Even then, you’d still need to have the stroke data, which seems like the hard part?)
557.
▲
by
lvh
7y ago
FWIW, that's been our experience as well (both at a largeish publicly traded company and now at a small private consultancy). Go get work sample tests :) (It's fine if your work sample test really just focuses on one language! But
558.
▲
by
lvh
7y ago
If we're going to talk about empirical effects, we first need to agree on what quality means. Parts of the thread, including your comment, lead me to believe we sometimes mean an abstract, desirable but ineffable property--but then we&
559.
▲
by
lvh
7y ago
Also, to get there, you're already accepting the assertion that the move isn't a management decision :-)
560.
▲
by
lvh
7y ago
FWIW, I have a very different read on this, based on both my experience with Clojure and some of the leading Storm-using orgs (and the Apache process). Firstly: Clojure isn't actually a problem. We hired people who are highly junior (o
561.
▲
by
lvh
7y ago
If that is true, would there be evidence that Amazon did not push the "customer obsession" until it became an antitrust target?
562.
▲
by
lvh
7y ago
The newest JVM out of Oracle, GraalVM, has its polyglossy as its central feature. And Clojure has always been a lot closer to Java (in terms of quality of interop) than even e.g. Scala, let alone something like Jython. (Notable exception JR
563.
▲
by
lvh
7y ago
If you can have the foresight to know how your project will be used many years down the line, sure, make technical decisions based on that :-) (Personally, I think the change is rather evidence of the primary drivers behind Storm developmen
564.
▲
by
lvh
7y ago
Because the previous title was editorialized? Furthermore, perhaps the conversation is about the old title because it was, and now the conversation can go be about Storm itself :)
565.
▲
by
lvh
7y ago
I'm not super interested in debating 'zimmerfrei but for everyone else: no, I don't think you should use a library that randomly slaps copyright headers of the fork author on source files [0] and introduces C implementations
566.
▲
by
lvh
7y ago
Still the same answer unfortunately: depends on the use case. Sometimes you just want signing, sometimes it's OK to share a key, sometimes...
567.
▲
by
lvh
7y ago
Same points I made before: if more than one library has a flaw, it’s a design flaw and not a one-off implementation flaw, and if you’re trusting the header before you validate (which is necessary!), then it is not meaningfully protecting an
568.
▲
by
lvh
7y ago
You mean massive in general not relative to the encrypt+sign-JWT combo detailed in the blog post? Any kind of encryption is going to make the ctext be effectively random bits, and is going to add a MAC tag that's some number of bits wi
569.
▲
by
lvh
7y ago
What? You mean protected by the _MAC_? The header is never encrypted: the header is how you even figure out what to do with the rest of the message at all. That is why it definitionally can not be protected by it (that's the definition
570.
▲
by
lvh
7y ago
I mean, part of the answer is "don't do that" but if you have to, secretbox or PASETO. Part of the problem is that "stateless token" can mean a lot of things depending on context; for internal use you generally want
More ›