Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jallmann
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
181.
▲
by
jallmann
11y ago
Pretty great article. It really blows my mind how different the food we eat today is, as compared to 500, 100 or even 50 years ago. For a long time, salt was precious and highly sought after. Sugar, at least the granulated form, has been
182.
▲
by
jallmann
11y ago
Excellent article, very clever optimizations given the tradeoffs. From the article: > We were talking about students' tendency to let the compiler substitute for thinking This is actually why I use OCaml. Not going to comment on whe
183.
▲
by
jallmann
11y ago
I used Bencode to encode messages for a presence and messaging system. Easy to write parsers for, binary safe, worked well overall. Probably the only real issue was that the sizes of lists and dictionaries aren't known in advance. This
184.
▲
by
jallmann
11y ago
> Any insights on why companies doing ship breaking wouldn't invest at least some of the returns into their own facilities? > people don't figure out ways to do it better/more efficiently/safer? From the article,
185.
▲
by
jallmann
11y ago
I have a few iTouches here for testing, kept at various iOS versions. Much cheaper than buying iPhones. Will probably pick up a new 6G soon, since the 5Gs are getting a bit long in the tooth, and no telling what iOS 9 will do to it. I'
186.
▲
by
jallmann
11y ago
> I wouldn't be interested in readinh an article called "I how I almost saved the Internet" The old title was "how I nearly almost saved the Internet starring afl-fuzz and dnsmasq " That title gives enough detai
187.
▲
by
jallmann
11y ago
The written guidelines might not have changed, but the enforcement policies certainly have. So instead of complaining about linkbait in titles, people complain about changing the title. Always going to be something to complain about... Anyw
188.
▲
by
jallmann
11y ago
IMO the newer title enforcement policies are worse than the old ones. The old ones might have been unreasonably rigid, but at least they were consistent. Right now the policy is "Keep the original title... unless we feel like it."
189.
▲
by
jallmann
11y ago
The public key operations during setup are clearly useful for authentication against a possibly untrusted peer. What mechanism is used for key distribution? Revocation? Is the main advantage over TLS in its use of a limited set of cryptogra
190.
▲
by
jallmann
11y ago
> If my country would do this - and it is very well possible they do Probably any country that can devote resources to industrial espionage does it. > I'd be very much ashamed of this "Playing nice" puts you at an disad
191.
▲
by
jallmann
11y ago
Pseudodoxia Epidemica is dense, strange and delightful. Probably my favorite chapter is on the Amphisbaena [1] (a serpent with a head on both ends), which Browne dismisses as basically being too weird to exist. Then he can't help but
192.
▲
by
jallmann
11y ago
> benefits are: practice, because we are going to want to run networks in space sooner or later anyway As I've said earlier, learning how to manage a fleet of probes is a non-issue until we actually have a legitimate need for a lar
193.
▲
by
jallmann
11y ago
Again: what would be the benefit of collecting hundreds of mediocre (and probably predictable after the first few samples) data points, without being able to do the kind of science you really want to do? If we had a few things we knew we
194.
▲
by
jallmann
11y ago
(IANA Astronomer) Each probe has a mission, and each instrument has an hypothesis it is designed to test -- that's the scientific method. Given the large fixed costs of space exploration, it's probably a better tradeoff for now to
195.
▲
by
jallmann
11y ago
Software implementations of a new codec are generally available earlier, but the first implementations shipping to consumers (in STBs, phones, etc) are all going to be in hardware, because the computational cost of a new codec is typically
196.
▲
by
jallmann
11y ago
> Which are two of the most critical properties of a codec. If your target is mobile or embedded, yes. Fortunately, that's not the only use case. Software codecs are a lot more interesting from the standpoint of not being fixed func
197.
▲
by
jallmann
11y ago
The only reason to implement a codec in hardware is speed or power consumption. Software codecs are much more flexible with the parameters you can tweak, and more tolerant of variances in the input such as buffer under/overflows, etc.
198.
▲
by
jallmann
11y ago
Very interesting! Didn't realize OMake was so large, although Windows portability seems like a strong point for the project. Would be interesting if the follow-up post goes more into depth comparing performance to other build systems,
199.
▲
by
jallmann
11y ago
> This is why the mission of securing America's networks needs to be removed from the NSA. And who should be responsible for this mission? Are you saying that the offensive and defensive cyber capabilities should be split between di
200.
▲
by
jallmann
11y ago
That's not what OP was asking. WebRTC is a standard in the same way HTTP is a standard: it defines the API surface and transport for a particular set of features within the browser. Signaling is intentionally missing from the WebRTC sp
201.
▲
by
jallmann
11y ago
WebRTC services are still, for the most part, isolated silos. There is no effort made to federate or interoperate between services. For that, you want something like SIP or XMPP/Jingle.
202.
▲
by
jallmann
11y ago
> I think it's worth refining that statement That's not a refinement; it's an ill-posed generalization based on misinformation and speculation. Please don't do that. The responses to this article have been on-topic an
203.
▲
by
jallmann
11y ago
> I can't help but come to the conclusion that any 'marginally legal if that' activity that it administered by the government will suffer from a kind of Peter Principle, where it continues being expanded until a major mist
204.
▲
by
jallmann
11y ago
> I also saw oCaml for iOS but it didn't seem to be up to date There is work underway to improve cross-compilation support [1][2]. Once that lands in a release, there shouldn't be any reason to maintain forks of the compiler fo
205.
▲
by
jallmann
11y ago
While I generally agree with your statements, it is important to note that in this case, the article's author has been arguing that any "fundamental asymmetries" between students and faculty are largely illusory, and such hai
206.
▲
by
jallmann
11y ago
>What will it take to bring this kind of technology to Southern California? San Diego county is already getting a desalination plant in Carlsbad, although it's projected to cost more, for much less water: $530 million for ~18 billio
207.
▲
by
jallmann
11y ago
That's the one for Standard ML, yes. There are others for SML, some using proof assistants [1]. Other (S)ML extensions have formal semantics as well, and OCaml itself is partially specified [2]. [1] https://github.com/C
208.
▲
by
jallmann
11y ago
Sure, for a subset of the language. But the point is, a hand-wavy complaint about PL semantics (which can be precisely defined) doesn't make sense when comparing languages in this context.
209.
▲
by
jallmann
11y ago
ML actually has a formally specified semantics. Haskell does not.
210.
▲
by
jallmann
11y ago
> Checked exceptions don't work very well with generic higher order functions Can you elaborate? The only problem I can see is if the language forces the exception to be handled by the caller. That doesn't have to be the case:
More ›