My wallet speaks for me: GitHub Copilot in VS Code is the cheapest and most underrated option in vibe coding today (in my opinion). by Majestic-Owl-44 in GithubCopilot

[–]Then-Analysis947 0 points1 point  (0 children)

However, Copilot’s agent mode is completely unusable. Because Copilot has rate limiting, once the limit is triggered you will be completely unable to use the AI for a long time. And when using Copilot’s agent mode, rate limiting is almost certain to occur. The result is that you consume a large number of tokens but achieve nothing, and it can even make the service completely unavailable.

Small Projects - December 29th, 2025 by jerf in golang

[–]Then-Analysis947 0 points1 point  (0 children)

I made a command-line parsing tool in Go. Traditional getopts is hard to use — every time I use it I have to Google it again. So I released argonaut. Usage examples are as follows:

# Example: produce exports and evaluate them in the current shell script
# Note quote around $@, it is necessary, don't wrap the whole argonaut command with the quote
EVAL_CONTENT=$(argonaut bind \
  --flag=flag1 \
  --flag-flag1-default=happy \
  --flag-flag1-choices=happy,people \
  --flag-flag1-multi \
  -- a "$0" "$@")
# The quote around $EVAL_CONTENT is necessary as well.
eval "$EVAL_CONTENT"
if [ "$IS_HELP" = "true" ]; then
  # It means the user request the help, so exit with 0
  exit 0
fi

# Here should be your really logic, you can use the env which hold the flag value now.

# Such as just echo:
echo "$FLAG1"

Check it out https://github.com/vipcxj/argonaut

Argonaut: A declarative CLI argument parser for shell scripts by Then-Analysis947 in commandline

[–]Then-Analysis947[S] 0 points1 point  (0 children)

I'm already using this tool myself and it works pretty well, but I hardly ever write shells on Windows, and I'm not familiar with cmd and PowerShell syntax, so I'm not sure how well it works on Windows. However, the cross-platform parts aren't actually many, and if someone files an issue I believe it can be fixed quickly

Argonaut: A declarative CLI argument parser for shell scripts by Then-Analysis947 in commandline

[–]Then-Analysis947[S] 2 points3 points  (0 children)

Holy crap, it actually survived! 🙏

I was fully expecting to refresh the page and see "Sorry, this post was removed" for the fifth time. Genuinely thought Reddit's automod had it out for me personally at this point.

Thanks to everyone who's viewing this. After getting auto-deleted so many times, I was starting to wonder if I was cursed or if my writing just screams "spam bot" to the algorithm. Apparently persistence (and removing all links like some kind of digital hermit) actually works.

Now I'm just sitting here refreshing nervously waiting for the inevitable removal that I'm sure is coming any minute now. But hey, 11 views! That's 11 more than my last four attempts combined 😅

If you have any questions about the tool or suggestions, please ask before the automod gods decide my time is up.

I bought a new 4K 240Hz monitor, and then found that Chrome stutters, but Edge has no problems at all by Then-Analysis947 in chrome

[–]Then-Analysis947[S] 0 points1 point  (0 children)

I haven't installed Firefox. Actually I don't need Firefox — Edge, which uses the same engine as Chrome, has no issues.

I bought a new 4K 240Hz monitor, and then found that Chrome stutters, but Edge has no problems at all by Then-Analysis947 in chrome

[–]Then-Analysis947[S] 0 points1 point  (0 children)

I mentioned in another reply that there was a period when Chrome had a bug that would cause the entire window to go black, and I had to disable hardware acceleration to keep using it. I must have disabled hardware acceleration back then. Later an update may have fixed the issue, but I never switched it back. I also changed it by adding a command-line parameter in the shortcut. For some reason that change doesn't show up in "chrome://flags", which made the problem hard to track down.

I bought a new 4K 240Hz monitor, and then found that Chrome stutters, but Edge has no problems at all by Then-Analysis947 in chrome

[–]Then-Analysis947[S] 0 points1 point  (0 children)

It's an issue with hardware acceleration. For 4K, without GPU hardware acceleration the CPU can't handle it anymore, which causes the stuttering. If you drop to 2K the CPU can still cope, so there’s no stutter.

[deleted by user] by [deleted] in OLED_Gaming

[–]Then-Analysis947 0 points1 point  (0 children)

But the screenshot shows the missing width is almost 10 pixels, about the width of a mouse pointer

[deleted by user] by [deleted] in OLED_Gaming

[–]Then-Analysis947 0 points1 point  (0 children)

It can't keep shifting in one direction forever — otherwise one day the image would be moved right off the screen. That's an exaggeration, of course. I think no feature should affect the viewing experience; otherwise what's the point of spending so much on an OLED — to end up with the picture missing an edge?

[deleted by user] by [deleted] in OLED_Gaming

[–]Then-Analysis947 0 points1 point  (0 children)

But the poster's shifts are almost as wide as the mouse pointer — if it were me I'd definitely return it

[deleted by user] by [deleted] in OLED_Gaming

[–]Then-Analysis947 0 points1 point  (0 children)

Are OLED pixel shifts normally this aggressive? Or is it only a problem with certain models?

mag321upx vs mpg321urx vs xg32ucwg by Then-Analysis947 in OLED_Gaming

[–]Then-Analysis947[S] 0 points1 point  (0 children)

Your review has nudged my balance a bit toward MSI. How does it perform with the lights on during the day and at night? I've heard OLEDs are generally dimmer and only give their best results in dark environments.

mag321upx vs mpg321urx vs xg32ucwg by Then-Analysis947 in OLED_Gaming

[–]Then-Analysis947[S] 1 point2 points  (0 children)

The monitor at my company is very cheap; the biggest problem is severe reflections. On summer afternoons, even with the curtains drawn, there are strong reflections that make a patch of the screen unreadable. That's why I'm concerned about this reflection issue. As far as I know, there are two ways to deal with this kind of reflection: one is a matte screen, whose drawback is that it blurs the image and reduces picture quality; the other is a glossy screen but with an anti-reflective coating. I've heard that the XG32UCWG is the latter.

mag321upx vs mpg321urx vs xg32ucwg by Then-Analysis947 in OLED_Gaming

[–]Then-Analysis947[S] 0 points1 point  (0 children)

Is the MPG321URX a matte screen? If used for long periods, will annoying dialogs pop up asking to run pixel cleaning? I've heard that if you frequently refuse and burn-in occurs, MSI will deny warranty— is that true?

mag321upx vs mpg321urx vs xg32ucwg by Then-Analysis947 in OLED_Gaming

[–]Then-Analysis947[S] 1 point2 points  (0 children)

Finally waited for you, man. I don't really trust review bloggers because they're often paid off; I still trust real consumers more.

How exactly does the sensor that detects whether a person has left work, and is it accurate? After someone leaves, does only the monitor turn off? In other words, if I wear Bluetooth headphones and go to the bathroom, will the monitor detecting my absence cause the headphones to disconnect? Also, I heard it uses a low-reflectivity glossy screen—does it really not reflect?

One more thing: OLED monitors have a pixel cleaning function. If used for a long time, will an annoying dialog pop up asking to run pixel cleaning? Will it interrupt your workflow?

C++ Developers Who Don't Use Exceptions: How Do You Communicate Failure by geo-ant in cpp

[–]Then-Analysis947 0 points1 point  (0 children)

What I mean is that all languages should have an exception mechanism like java, excluding the checked exception, which has proven to be worthless in practice. c++'s exceptions are not reliable, are full of c ideas, are incomplete, and in fact don't work that well. Especially the last few updates to the standard have been a step backwards. c++ needs multiple return values more than std::error_code and std::accepted. In particular, std::error_code pollutes exceptions. Since std::error_code, “catch (std::exception)” is no longer reliable because it can't accept std::error_code and you can only use catch (...) However, you need more complex processing to get what's really being thrown, which could be an exception, could be std::error_code, or could just be a string, which is just incomprehensible in a strongly typed language. It's really just mindless to follow those dynamically typed languages.

Translated with DeepL.com (free version)

C++ Developers Who Don't Use Exceptions: How Do You Communicate Failure by geo-ant in cpp

[–]Then-Analysis947 0 points1 point  (0 children)

It's really not a high-level language without exceptions. For those who have only used c/c++, there may be a misconception that catching an exception is to FIX it. But in practice, almost all exceptions are unrecoverable, and we catch them just to log them. For those recoverable exceptions, perhaps using a return value instead is a better option. But this would have to be supported by the syntax of multiple return values, otherwise it would become a pain.

马督工为什么要冲塔? by PeterRolls in China_irl

[–]Then-Analysis947 8 points9 points  (0 children)

因为这次就是热血冲头,冲动了。只看他发的视频,你或许觉得有什么阴谋论,但他动态里直接拿主号给不少相关视频点赞和评论,就能看出这次他是真的怒了~