wbercx
Joined 13 years ago
Joined 13 years ago
I find myself having to STRAIGHT_JOIN more often than I would like because it simply won’t generate sensible execution plans sometimes.
What drives this sentiment?
Our bottleneck was that we have so much data, making it all observable up front led to slow initial load times and high memory usage. We now make things observable on demand which has eliminated a lot of that.
https://docs.microsoft.com/en-us/windows/wsl/wsl-config#boot...
There's a few more on that page. I would not be surprised if more appeared over time.
With that said my details do not appear to have leaked.
Chrome decided to add autocomplete to some of our fields with contextually irrelevant options. As far as I know there isn't anything I can reliably do about it.
Already lost interest.
In React and like-minded projects, I look at a stack trace and see that it starts at some kind of batch renderer. I can't tell "why", "how" or sometimes even "what" broke. The input part of it is completely lost.
I work on a Backbone application where stack traces are much more obvious. They usually tell you the whole story. I find that juniors who were mostly exposed to React have a tendency to completely ignore stack traces, and am now wondering if they are just conditioned to them being unhelpful.
I’ve noticed that many light themes use relatively bright colours for text, and I’m finding them increasingly difficult to read.
The orange used in the explorer view is just bright enough to become slightly blurry to me, causing me to squint.
I may not have that issue if you use the same orange found in the syntax highlighting, which seems slightly darker to me.