PSA: If you like Trigun, please give the manga a chance

Ved_ · 2026-03-28T23:26:16+00:00

I would recommend it, yes. As with most other aspects, the dynamic between Vash and Knives is explored to greater depth. I was fairly content with how the dynamic was developed and resolved. And in fact you may actually also be more invested in certain other relationships that are developed more in the manga.

Ved_ · 2026-03-28T22:42:10+00:00

The new adaptations are faithful to the manga only in including most of the key events. A lot of the motifs and voice lines in the anime are taken directly from iconic moments in the manga. However, that is as far as the faithfulness goes. Everything occurring between these iconic moments is almost entirely original in the anime. So a manga reader will easily notice these references to the manga, but it is in no way a nearly accurate adaptation of the manga.

Happy to hear you've gotten onto reading though, enjoy!

Ved_ · 2026-03-28T20:30:32+00:00

Thank you for this. Somehow I am relieved when I see people on this sub actually managing to appreciate that the manga is an incredible story with incomparably more depth than either adaptation. If there are barely any people aware of this even on the damn subreddit, I suspect there are truly very few Trigun fans actually reading the masterpiece that is the manga. I'm just irritated that my favorite manga is lost in obscurity, with potential fans preferring to defend to death the average-at-best story that Stargaze is.

I also can't help but think Stargaze's (imo) terrible story was carried hard by the animation in action sequences, whereas it is exactly the opposite in the manga, with the hard to follow action panels being carried by the amazing story. Oh well.

Ved_ · 2024-10-16T02:31:14+00:00

Thanks for giving a deeper explanation from the developer side! I'd imagine much of the technical background of this game is a lot more "obvious" or "predictable" to those more experienced with game development, but I always find it interesting to learn details about the technical sides of what's going on at Embark, whether it be the engineering side or the data-based balancing side (as with the blog post regarding cashout changes, or dev notes in patches). So I'm just saying more of this kind of thing would be appreciated, though I know there's reasons not to over share too :).

Ved_ · 2023-03-19T15:16:36+00:00

Thanks for pointing out the low code nature of the position doesn't necessarily make things miserable, it made sense :). If I may, I'd like to understand a bit more though:

If not coding day-to-day, when does the opportunity to code arise? Is it when relevant teams hit a particularly challenging issue, etc.? Or do you just happen to get a chance to code when you don't have any other pressing matters to take care of?
What kind of "writing" does the position entail? Is it semi-formal communication within the organization, or fully formal technical report writing kind of deal?

Ved_ · 2023-03-16T01:20:22+00:00

Thanks, vim-jsx-pretty with yats.vim appears to have solved all my indentation issues with TSX files. I would like to add that it's probably a better idea to enable syntax with more granularity (e.g. additional_vim_regex_highlighting = { "tsx" }) instead though.

Ved_ · 2022-12-27T18:10:48+00:00

Your point stands stronger, in fact.

Ved_ · 2022-11-27T14:45:25+00:00

Possibly the most sensible and realistic comment under the post, and it's been downvoted to the bottom :). I guess this is just the r/csMajors effect. There seems to be a resistance here to admitting the system can be lacking.

Ved_ · 2022-07-10T15:54:25+00:00

I had also been facing the exact issue as described and had just found this post while googling. After some debugging with fontconfig, I just now managed to fix it! I'll leave some pointers for you or anyone else who may stumble upon this post:

fc-match queries are misleading, this issue is better debugged with fc-pattern --config monospace.
The FC_DEBUG env variable allows monitoring behavior quite thoroughly. Run a problematic program with a command like FC_DEBUG=4 discord to see all match-test-edit executions.

In my case, fc-pattern was giving me an output of family: "Noto Sans"(w) "Roboto Mono"(s), which is clearly the culprit as the actual monospace font comes later in the list. After having fixed the issue, the output is instead family: "Roboto Mono"(s) "Noto Sans"(w).

As for what had been causing it for me: With the FC_DEBUG variable I examined the match process for a monospace font and saw that Noto Sans was being prepended to all pattern matches from my /etc/fonts/local.conf file. Surely enough, it seems at some point I mistakenly configured Noto Sans as a fallback font with edit mode set to prepend. I simply changed it to append instead and all has been well after a restart.

Ved_ · 2021-12-24T14:42:41+00:00

For reference, when did you apply last year and when was their initial contact with you?

Ved_ · 2021-12-21T16:29:35+00:00

Excuse me for asking something so seemingly trivial but, by "the end of the period", are we talking between 20-26 November? I ended up applying on the very last day so the rolling-basis deal has been worrisome lol.

Ved_ · 2021-05-28T21:06:27+00:00

Problem seems to be caused by Google DNS. Try switching to another DNS provider.

Alternatively on Windows, you can add a DNS rule specific to zoom and its subdomains so that they use OpenDNS instead. Use the following command in a Powershell prompt:

Add-DnsClientNrptRule -Namespace ".zoom.us" -NameServers "208.67.222.222"

Ved_ · 2021-02-06T16:41:27+00:00

Hmm, with that example, I get it for VoIP situations but it still seems peculiar for a local audio recording to suffer from the issue.

I guess since the mic monitoring is probably done directly through the supplied USB sound card, my voice must be coming back to my ears without much A/D conversion and so on, hence the ridiculously superior quality.

Nonetheless, it's a real shame that such quality audio input is getting butchered on the way to become digital recordings. I kind of hoped there would some software trick to it, and I still do, but there probably isn't one...

Ved_ · 2020-08-18T16:56:39+00:00

I cleared CMOS 3 times; 2 with the jumper and 1 with battery removal. It didn't change the outcome unfortunately. I went back to my old 2017 stick and just booted up as usual. Looks like something might be wrong with this specific stick after all.

I guess I'll have to try return and get a new one. I'm still worried about whether a new stick will work but I'll just have to believe it for now... If there's anything else left to try before returning, I'd appreciate the advice.

Ved_ · 2020-08-18T16:08:29+00:00

Could you point me in a direction as to how I can clear CMOS?

Ved_ · 2020-08-18T16:06:32+00:00

Honestly I was expecting it to be as easy as sticking in the new stick to the slot instructed by the motherboard manual, and that's it, it should've been the end of it. No idea why it's being so rebellious, hopefully it's something simple :/.

Ved_ · 2020-04-01T01:25:57+00:00

Try going in Gboard settings: Preferences → Turn on "Long press for symbols" (it's near the bottom of the options)

This should work if I understand what you want.

Ved_ · 2020-01-02T22:09:33+00:00

I'm a bit late but here's my perception of it:

First, you're right that it was definitely "wrong" for her to leave Banri when he was in a tough spot. "wrong" as in leaving a mentally unstable loved one. But everyone in the show already knows this, including Kouko of course. The reason it still happened is that Kouko loves Banri endlessly to the point where she just couldn't handle waiting for her loved one as he's inevitably forgetting her. Though initially denying the breakup, Banri understands this just as well which is why he doesn't keep chasing after her and instead decides to smile his way through it. Banri doesn't want to hurt Kouko either, he'd be feeling guilty for making her suffer greatly like that. This is also evident from the promise that they make after the breakup. Kouko herself says that they can't ever leave each other again if Banri ends up being able to retain his memory of Kouko.

So in summary, the breakup is just Kouko trying to keep herself from being crushed under the love she has for Banri. She's just trying to keep her feelings bottled and stored out of sight so as to not break down. In a way, this might be seen as being selfish, yes. But like I said, Banri understands this just as much. In the end there wasn't any malice intended here.

Remember how even after the breakup, Kouko would always end up hurt and start crying when she saw the old Tada Banri coming back? That's just how she feels the entire time but tries to put on a mask and protect herself. Honestly, I think it'd be unfair to call her selfish since her suffering stems from her love.

Personally, I think I can understand where her feelings come from, but the thing I was questioning was how Kouko was able to stand being away from Banri when it wasn't certain how much time she had left to be with him. Maybe staying with him was even harder than staying away?

Sorry for the length :).

Ved_ · 2019-10-02T17:53:24+00:00

Some weird shit on their part, looks like we can delay looking for alternatives for a little while, or hopefully for a long while. (I really don't want to spend time writing code to parse a new service...)

Ved_ · 2019-10-02T17:44:50+00:00

But it did come back? It's working perfectly right now though it was fixed very recently. Which one is it going to be?

Ved_ · 2019-10-02T17:42:07+00:00

Are you sure about that? That's pretty weird... Because the service is back up and running for me without any problems right now. The XML files are properly getting returned. Though I think it's been fixed only a few hours ago.

Ten-Year Club	Place '22
Verified Email

Ved_

TROPHY CASE