I don't like it, but if they're part of the project files, then they belong in version control. I do worry about the challenges of combining the difficult-to-merge nature of binaries with the distributed workflows that Git encourages. While data doesn't get lost, the inability to merge them may mean that someone needs to spend extra time re-performing their changes if they "lose" the push/merge race.

Game engines have been doing a better job of transitioning away from large monolithic binaries by either serializing them in somewhat mergeable text files or at least splitting them into large numbers of smaller binaries to reduce file contention.

Git LFS does offer the ability to off-load them from the repository, reduce download and checkout times as well as the ability to lock files (which does introduce centralization...), but it doesn't seem to be as ubiquitous and can be more expensive to use, depending on the team's options for Git repo providers.

Note: I assume you mean binaries as in "non-text files", not build artifacts, which definitely don't belong in version control at all.

It's exactly that: the trickiness around debugging is the main thing that feels like it's got some barriers compared to a turnkey solution in an IDE. I heard VS Code and Godot was available until I realized that the LSP and debugger for Godot 4.x was unusable for months until the recent refactor.

Don't get me wrong though, I am totally using VS Code for my Rust projects. It just isn't a turnkey solution that I'd recommend to someone if they just want to hit "New project" and do the whole write-compile-debug loop without needing to understand anything. (I had also used it a while back prior to rust-analyzer being the main go-to extension, I think...)

VS Code is a great text editor for me. I write Markdown documents, manipulate bulk strings, and diff files with it. Aside from small scratch projects, its consistency and reliability as an IDE is varied for me. It's far from "just works", at least for the types of things I do (C, C++, C#, Rust) and isn't really on my list of editors I'd recommend for those workloads.

You can make it work, but it's going to require extensive time spent figuring out what extensions to use (and their quirks), ensure that you have a working setup to the language server, and learn how each environment wants you to setup its tasks and launch configurations, if applicable. Unlike larger IDEs like VS or Rider, it doesn't have a consistent "new project" process either, so you're on your own for that.

I keep different identities for different purposes. This identity is pretty public and active on social media, but mostly in the developer and anime sphere. This is partially born out of a desire to find other people to connect with on those topics, which makes it a worthy trade-off in my view. I also don't mind sharing what I've posted since most won't bother to look closely, and even if they do, there's not too much to find other than my interests and past projects.

Other identities serve other interests or are much more personal, so those things aren't as closely in the public eye. My more divisive or controversial takes are really only shared with trusted friends and generally not in writing though, so I might not fit the question you're posting very well, haha

I've only used code snippets in VS Code which can store them in user settings for synchronization. They can also e stored in project settings, which can be optionally synchronized via source control.

I tend not to need them in larger projects where a lot of codegen is available or macros, so I haven't thought about a solution for things like VS or manual syncing.

Generally, I wait for gameplay footage from official and unofficial sources before committing to buying a game. I have a number of accounts I follow on other social media platforms that keep me updated on new games I might be interested, but none of them are reviewers outside of a quick 30-second blurb on socials or their Steam Curator account.

If I'm leaning buy but still hesitant, I'll generally pick it up and play for a bit to see if I'll keep it.

I don't find that my tastes align very closely with any reviewer, so I generally steer clear of them. If there's any kind of massive community criticism, there's bound to be plenty of people shouting about it online which makes it easy to take into consideration (whether to ignore it or not).

Yeah, the improved contrast and color accuracy is the main reason why I even considered swapping out the screen. The simulated color vibrancy mod (which is coming "soon" to stock SteamOS 3.5 anyway) ended up being good enough for me though as long as I just want pretty colors.

If I really care about the visual experience, I'm doing it on my desktop w/ a proper monitor anyway, not on the dinky little 7" screen.

That said, if I ever broke the screen though, I might do it since I'd have to replace it anyway.

An extension called Indie Wiki Buddy can also help with this by helping direct you to known alternatives to fandom for specific franchises or falling back to Breezewiki-based instances that rehost Fandom content without all of the Fandom bloat. It also provides this filtering and hinting to search results too, so you don't have to change your workflow too much to use it.

I think my preference would be to have the game offer to reduce the difficulty temporarily after failing or offer other forms of support to make the boss encounter easier. If I selected Hard then I probably want the challenge of Hard, but if this difficulty spike is too much, then smoothing it out could be acceptable.

This is also ideally in addition to a way to adjust the difficulty mid-game as needed, of course.