Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nickbauman
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
nickbauman
6y ago
Yes. But the Mongols (Golden Horde) reached Germany eventually in the late 14th century, but that was their apotheosis; they never came back after that. https://en.wikipedia.org/wiki/Mongol_invasion_of_Europe#Agai...
62.
▲
by
nickbauman
6y ago
I think the problem with XML is that people tried to make it into something as comprehensive as CORBA (this is SOAP) so that all the decisions about the communication was done in-band. JSON requires everyone to make out-of-band decisions ab
63.
▲
by
nickbauman
6y ago
Thank you for writing it. Not enough of this sort of thinking on HN. Too much emphasis on the incrementalism of "pioneering the obvious". Not enough on the 10,000 foot view of the problem.
64.
▲
by
nickbauman
6y ago
Goodness, the number of folks who divide the world into "solved problems" and "problems to be solved" missed the entire point of the article. This article was not about "what we can do to the world for our own needs
65.
▲
by
nickbauman
6y ago
Replying to myself (facepalm): just to make sure people know what I think. I've been doing TDD since 2002. I'm of the "You will take this out of my cold, dead hands" variety on the usefulness of TDD. That doesn't me
66.
▲
by
nickbauman
6y ago
Let's keep in mind this Fowler post has no science in it. It's just some "lauded practitioners'" view of TDD. Our industry is driven by this kind of discourse. There's very little good scientific research to an
67.
▲
by
nickbauman
6y ago
JS and their ilk replace the market-makers, you're saying.
68.
▲
by
nickbauman
6y ago
I thought that was clear: prior to HFT, the seller would have made the deal with the buyer without the intermediary HFT because if the latency. HFT exists because of speed. Very hard to say "High Frequency Trading" without saying
69.
▲
by
nickbauman
6y ago
Right, gotcha: the market needs intermediaries to function properly.
70.
▲
by
nickbauman
6y ago
Thanks, that's what I thought.
71.
▲
by
nickbauman
6y ago
So that's the missing part you say? The Internet has been the biggest catalyst of disintermediation in history. But this is not disintermediatable without HFT?
72.
▲
by
nickbauman
6y ago
Yes. So seller A wants to sell for $1.00 and buyer B is willing to buy at $1.06, an algorithm will calculate the presence of this potential (or actually have knowledge from other systems that this a certainty) and purchase seller A's s
73.
▲
by
nickbauman
6y ago
When we say "algorithmic trading" is this synonymous to "high frequency trading"?
74.
▲
by
nickbauman
6y ago
I read that too. Loved it. An unexpected gem!
75.
▲
by
nickbauman
6y ago
Kapton is also inside many nuke plants in the US, too. What could possibly go wrong?
76.
▲
by
nickbauman
6y ago
I live in downtown Minneapolis and it's the first time I no longer really need a car since my childhood in Germany. And I love it.
77.
▲
by
nickbauman
6y ago
Right a startup looking for funding (by its very nature) means you're creating a situation where your company will be in the process of going out of business the moment you get your capital. Your job is to prevent that eventuality. S
78.
▲
by
nickbauman
6y ago
That is nice
79.
▲
by
nickbauman
6y ago
The point is Hickey brings up important points about language design as its experienced by devs actually using the language. Hardly anyone discusses this. Furthermore, you seem to be making my argument for me when you claim that Clojure d
80.
▲
by
nickbauman
6y ago
Writing your own type system in a Lisp is an afternoon task, but nobody does that because...
81.
▲
by
nickbauman
6y ago
That's a good link there. I think the answer to a smaller Rust is Go, however. The comparative compiler speed alone is worth the price of entry. Don't @ me ;)
82.
▲
by
nickbauman
6y ago
Not if I loosened the requirement. Stricter adherents shouldn't have to change anything. This is poor language ergonomics.
83.
▲
by
nickbauman
6y ago
Yeah that's not good design. Lowering a requirement should not make callers complying to a stricter one have to change anything. But, ohhh.. right only the type changed. so everybody stop what you're doing and start over.
84.
▲
by
nickbauman
6y ago
Poor ergonomics: I loosened a requirement. Nobody should have to change their code. Kotlin does this right.
85.
▲
by
nickbauman
6y ago
Most Optional implementations are kinda terrible, though. They cost more than they save. If I have a function with a param and I release it with it required, but later I change it to be optional (loosening a requirement) does rust require e
86.
▲
by
nickbauman
6y ago
Never had a problem with the closure compiler vis-a-vis ClojureScript, is this really a thing?
87.
▲
by
nickbauman
6y ago
Yeah the borrow checker is an interesting solution to a problem I don't have with a managed language. It's the main "safety" feature people coming to rust are introduced. I'm in agreement about Rust here with a lot:
88.
▲
by
nickbauman
6y ago
Types provide only the simplest most trivial kinds of correctness, though. And people routinely make mistakes with types.
89.
▲
by
nickbauman
6y ago
Clojure has been there as a fullstack language for a lot longer. It also fulfills the story that Elm was trying to do for much longer. And Reagent is a much needed improvement on React. The borrow-checker in Rust is kind of silly tool to us
90.
▲
by
nickbauman
6y ago
Please check out the term "Overton Window"
More ›