Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
quizotic
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
quizotic
10y ago
I tend to fire those who write IMHO, primarily for the humble part, but also, who else's opinion is it :-?
32.
▲
by
quizotic
10y ago
Why? I honestly don't see how it's out of scope at all (majored in mathematics, minored in physics)
33.
▲
by
quizotic
10y ago
When I rant about it, I claim his theorem says "any system that reference parts of itself is either incomplete or inconsistent," and that the universe is such a system, as we're a part of it, and refer to parts of it. So ther
34.
▲
by
quizotic
10y ago
For those who aren't riveted by the gorgeous ... sweater ... the link to the relevant TED talk is https://www.youtube.com/watch?v=Lp7E973zozc TL;DR: when tempted by procrastination count backward from 5
35.
▲
Ask HN: Coding with?overlays?
3 points
by
quizotic
10y ago
|
2 comments
36.
▲
by
quizotic
10y ago
Most of it seems pretty real-world to me. But if IIUC that std::filesystem means I don't have to write separate code for windows and linux, then it's hard not to imagine EVERYONE using that.
37.
▲
by
quizotic
10y ago
Interesting hypothetical ... even more interesting if you're implying it might not be so hypothetical
38.
▲
by
quizotic
10y ago
> the [antebellum] American south was probably the most advanced agriculture civilization ever I don't follow. Certainly the current farming system in the American mid-west is orders of magnitude more productive. But even if we'
39.
▲
by
quizotic
10y ago
Yes, we took land from indigenous peoples, and enslaved Africans. And yes we did awful things. But isn't it obvious that neither of these things created the wealth we have today? To my thinking, our current wealth derives from technolo
40.
▲
by
quizotic
10y ago
If you're an experienced C++ coder, I'd skip this article. While it's well structured, with real-world examples, it's very basic. I'm not an excellent C++ coder by any stretch of the imagination. I make lots of mist
41.
▲
by
quizotic
10y ago
Sorry, I posted the same before seeing your response.
42.
▲
by
quizotic
10y ago
I thought it was a term from Shogi, meaning "Check!", equivalent to the term in chess.
43.
▲
by
quizotic
10y ago
In the 70s, when I was all bushy-tailed, I cornered Gerry Sussman at MIT to tell him about "this new relational data model and SQL language". About two minutes into the conversation I saw him looking at me like "God, why have
44.
▲
by
quizotic
10y ago
Sigh. It's hard to know where to begin critiquing this. I guess the TL;DR would be something like: "For constrained but not atypical data models (no N:M relationships, foreign keys explicit in the schema, etc), it's possible
45.
▲
by
quizotic
10y ago
It's ironic that you see him this way ... cause he's trying to say that seeing him this way is one of the things he hates and wishes was otherwise. And by the way, it doesn't help if he goes quiet, never talking about this we
46.
▲
by
quizotic
10y ago
Interesting. I didn't have that reaction at all. I grew up in a ridiculously wealthy community, and saw the exact problems with wealth differences that he described. And I think he identifies an important truth: most of time, successfu
47.
▲
by
quizotic
10y ago
In situations where agile/story-points make sense, I suppose developers that accomplish more story-points are "better". In academia, articles that are referenced more frequently are "more important". For page rankin
48.
▲
by
quizotic
10y ago
Just so disturbing. We pride ourselves in tech on being a meritocracy. But it's not really true, even now. I'm a starchy-assed white guy, who was born in Asia and married a dark-skinned woman, so you'd think maybe I was diffe
49.
▲
by
quizotic
10y ago
should also point out that Mongo is more than a jsonb store, and postgres is, at least currently, less than a distributed, "scale-out" database. Mongo supports problems that postgres cannot currently address. period. (and I'
50.
▲
by
quizotic
10y ago
And for those who may not know, but appreciate irony, Mongo now uses ... wait for it ... a somewhat stripped down, key-value-ish, embedded ... RDBMS as its underlying data store. Yes friends, "it's a dessert topping AND a floor wa
51.
▲
by
quizotic
10y ago
> "Saving" 15 minutes of dev time because you don't know what your schema is going to look like is going to cost you orders of magnitude more time. While I agree with the spirit of this, sometimes you'll never know wh
52.
▲
by
quizotic
10y ago
I've seen Hive take minutes (OMG!) to count a table with 5 rows ... but (other) people still think it's OK, because it scales well. It's latency sucks for small data sets, but it can handle very large data sets.
53.
▲
by
quizotic
10y ago
And I've heard it said that lowering latency is harder than increasing throughput ... though whether it's more important probably depends on the context.
54.
▲
by
quizotic
10y ago
I've spent much of my career trying to optimize latency of long analytic-type queries; and I've been wrong on both sides of the issue. While it sounds stupidly tautological to say, I've come to think the important thing is be
55.
▲
by
quizotic
10y ago
Ah. Thank you for the correction!
56.
▲
by
quizotic
10y ago
As a "newer" engine, SQL Server has a couple of tricks that aren't found in most other systems, including intra-query parallelism across multiple threads. This capability requires occasional reshuffling of data between thread
57.
▲
by
quizotic
10y ago
I think you can just prepare them again, no? Of course the onus is then on poor you to know when that might make sense because of changes to the referenced tables. Though postgres is so incredibly open, you could probably do that with a tri
58.
▲
by
quizotic
10y ago
Exactly! We're so stuck in the implementation language of the 1980s: index, tablespace, partition, hash-vs-merge-vs-nestloop join .... that we lose sight of what matters. "I want these queries to be fast" ... genius.
59.
▲
by
quizotic
10y ago
> It's still quite hard to optimize queries especially if there are numerous JOINs involved Sigh. In the real world (meaning 99+% of applications) there are a few big sets of data and lots of smaller sets of reference data. The thin
60.
▲
by
quizotic
10y ago
No. Not true at all. At around a billion records, you start getting into distributed/scale-out systems, and distributed indexes are performance death whether for OLTP or analytics. Even before you cross into distributed query processin
More ›