401 karma · joined June 2, 2011
So therefore, the universe is either full of magic (in a system with inconsistency, anything can happen), or mystery (there are true things that we can never prove).
My belief is that the quest to find a unified physics that describes everything is provably impossible due to Godel's theorem.
And on the rare occasions when I look for evidence of God, the fact that one of the things we can know for sure - is that we can't know everything - provides about as much comfort as I need.
https://www.youtube.com/watch?v=Lp7E973zozc
TL;DR: when tempted by procrastination count backward from 5
I don't follow. Certainly the current farming system in the American mid-west is orders of magnitude more productive. But even if we're focussed on pre-industrial history, are you sure that the ancient South American agri-economies weren't better? And for productive land use, what about Japan and south-east Asia, where every square inch ran like clockwork.
But isn't it obvious that neither of these things created the wealth we have today? To my thinking, our current wealth derives from technological innovation, process engineering, psychological insight, most of which would not have been possible without welcoming people from other lands, and being willing to work with those who are different than we are.
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 mistakes. But not these. The article is fairly thorough and long, so if you're experienced you'll invest non-trivial time for little or no reward.
Or maybe it was the look you have when you are SURE that someone is telling you an elaborate joke and suddenly realize that no punch line is coming.
LINQ: I'm looking at YOU :-/
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 to have a more concise syntax than SQL, with less impedance mismatch."
But even that underwhelming statement is generous.
In the 1980s, the object database claim to fame was less impedance mismatch, and ODI's "coding by deletion", but at least ODBs coupled that with claims to superior performance for network data models.
Maybe it's just the grandiose title "LINQ beats SQL" that's so annoying. Simpler syntax would certainly be welcome for the relatively rare cases of humans generating SQL (I think most SQL is machine generated these days)... but only with a host of etceteris parabis conditions, prominently including performance.
And by the way, it doesn't help if he goes quiet, never talking about this wealth or experience. Then he's just seen as aloof an heartless.
It's just true. Becoming wealthy changes things for most people. Maybe not Warren Buffet.
In academia, articles that are referenced more frequently are "more important". For page ranking, pages that are referenced more frequently, are more important. I wonder if there's an equivalent with infrastructure programming? If a developer builds a subsystem that is used frequently, does that indicate the developer has provided substantive value?
But articles like this help. Keep pounding in the message, and eventually people will change ... or die off.
While I agree with the spirit of this, sometimes you'll never know what your schema is, because it's not under your control to begin with. That's why there are triple-stores and "document" databases and key-value stores now, and why there were deductive databases 30 years ago.
The world is wide, and there's room for more than one tool in the chest.
* I might think I know what's important/critical-path and be wrong (it's happened)
* Users might be willing to live with slowness in some areas I didn't expect and demand performance in others
* More performant solutions might come to light later
* Particularly before product-market fit, features and their optimizations might be discarded
* New development might change the critical path
OTOH, I've found it's often beneficial to organize data and processing in a way that can take advantage of parallelism like multi-threading and vectorization. Often that's the kind of thing that's harder to do later.
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 thing that matters for performance is reducing that cardinality of the big stuff as quickly as possible. Which is a huge constraint on the search space.
Sure, in some theoretical sense, join ordering needs an A* algorithm or simulated annealing or some other esoteric approach to search. But in practical sense, it is almost a non-issue.
And here's the thing. Those systems with advanced search and costing for join ordering STILL make incredibly stupid decisions more than 3% of the time. And a bad decision can take hours to days and dominate all the good decisions.
DeWitt made incredible contributions to database architectures. He's a great guy and I'm a huge fan. But that was 30 years ago. Where are today's DeWitts?
What about different compression schemes for different sets of "column" values - with the idea that you execute against the compressed values, rarely ever decompressing. Even column store systems that allow you to specify a compression scheme aren't adaptive. Why the hell not? This is almost 2020.
Regarding your point about reads and writes on the same store, you might take a look at the new "HTAP" systems (hybrid transactional and analytic). The VectorWise guy has a "new" (probably old by now) project called HyPer