Not on Oled issue but I've noticed that vscode fonts appear much sharper than visual studio fonts. It's subtle, but just enough to make me dislike looking at code in visual studio.
This is such a common annoyance on the modern internet. I've recently been playing Minecraft with my kids, with a few mods, and I've been irritated to discover that - unlike when I'd mess around with mods a decade ago - lots of the "documentation" for mods now exists only in video form.
Anyway, I built / slopped out this little wrapper for yt-dlp that I call tuber[1], and it has a feature for grabbing a video's subtitles and summarizing them with Claude, if you've got the CLI. I've found it really handy for those annoying cases where some video seems to promise info I want but I don't want to sit through ten minutes of bullshit.
Some of the comments in these links are hilariously elitist. They are actively embracing a hostile environment, especially towards newcomers, but how do they expect to grow and maintain a community when they are scaring users away?
Thing is, if that's how you are greeted at stackoverflow, then you'll go elsewhere where you're not treated like an idiot. Stackoverflow's decline was inevitable, even without LLMs.
> I disagree with most comments that the brusque moderation is the cause of SO's problems
The moderation was precisely the reason I stopped using stackoverflow and started looking for answers and asking questions elsewhere. It was nearly impossible to ask anything without someone replying "Why would you even want to do that, do <something completely different that does not solve my problem> instead!". Or someone claiming it's a duplicate and you should use that ancient answer from another question that 1) barely fits and doesnt solve my problem and 2) is so outdated, it's no longer useful.
Whenever I had to ask something, I had to add a justification as to why I have to do it that way and why previous posts do not solve the issue, and that took more space than the question itself.
That's not moderation. That's a lack of moderation. Comments like this weren't posted by mods but by people looking for stuff to answer. A mod would definitely delete such a comment if they were notified about it. But not enough users flagged stuff and preferred to complain about being hurt instead. There's also a problem that not enough mods were present at all times to handle the volume of comments posted.
I will miss it but you are right about moderation. I don't know what the issue is on some platforms, reddit and SO come to mind. Moderators on many other platforms or forums seem to be alright and keep a clear head, even when they have to deal with a lot of vitriol and they get little thanks for their work.
There are probably negative examples as well but some platforms seem to be especially vulnerable. If I had to run reddit or SO, I would limit moderation to one subreddit/subdomain. No idea if that would help, but the problem isn't exactly invisible.
The high memory usage is due to the optimization. Responsiveness, robustness and performance was improved by making each tab independent processes. And that's good. Nobody needs 80 tabs, that's what bookmarks are for.
"using namespace std;" goes a long way to make C++ more readable and I don't really care about the potential issues. But yeah, due to a lack of a nice module system, this will quickly cause problems with headers that unload everything into the global namespace, like the windows API.
I wish we had something like Javascript's "import {vector, string, unordered_map} from std;". One separate using statement per item is a bit cumbersome.
Last time I tried, modules were a spuriously supported mess. I'll give them another try once they have ironclad support in cmake, gcc, clang and Visual Studio.
Terrible for atomic functions where you are often only interested in atomically writing something, but not interested in the return value they also provide.
I'm not a fan of nodiscard because it's applied way too freely, even if the return value is not relevant. E.g. WebGPU/WGSL initially made atomics nodiscard simply because they return a value, but half the algorithms that use atomics only do so for the atomic write, without needing the return value. But due to nodiscard you had to make a useless assignment to an unused variable.
Disagree. This is the default in Objective-C & Swift, and it’s great. You have to explicitly annotate when discards are allowed. It’s probably my all time favorite compiler warning in terms of accidental-bugs-caught-early, because asking the deeper question about why a function returns useless noise invites deep introspection.
Only when it comes to graphics/art. When it comes to LLMs for code, many people do some amazing mental gymnastics to make it seem like the two are totally different, and one is good while the other is bad.
reply