It's one of the best written games I've played.

Even ignoring the actually rare setting and well done world building, Aloy's growth from kid out of her depth into the Savior of the planet, and how she reacts to primitive tribal cultures with beliefs she knows are outright laughable are really well done and really well executed. I'm more of a "play games for the mechanics" person and that's what originally got and kept me hooked, but the writing works well.

I get them. I don't always answer.

I tend not to get along well with the kind of people who think I have to drop everything to respond to them, so it's fine.

If they hadn't made it impossible to use a functional app to browse their site, I probably wouldn't care.

But the fact that they blocked 100 apps that would, if you merged the absolute worst of all of them, still blow the actual Reddit app out of the water? Nope. Fuck 'em.

Everything has a huge opportunity cost. You're giving up alternatives for every choice you make. Lowering variance of high impact attacks has value if you choose to play that way. Missing can turn a battle.

It doesn't have to be useful to every choice of every build to have its existence justified. There are plenty of choices of spells, equipment, etc that I can look at and tell you "I'll play 20 different times 20 different ways and never be tempted to use that once". That's perfectly fine.

Does true strike not apply to spell slots or per battle/rest attacks? Because an advantage on some of those limited use attacks makes perfect sense to give up an action for.

Maybe if Microsoft(/Facebook/Elon) stopped doing actively fucking evil shit every opportunity they got it wouldn't dominate the discussion?

On top of that, there's the fact that the system is so reliant on its unique GamePad controller – many games actively require you to use it rather than other controllers, and you can't even change your system settings without it.

Holy fucking shit nintendo.

I liked cloud of daggers. Moving it is good, because it's absolutely possible to basically burn it and not have it be that useful past a turn or two, but just taking away positions for enemies to be has value.

Maybe not compared to something higher level like Hunger of Hadar I used a lot with my warlock later game, which covers more ground and affects movement as well, but making it harder for a caster/archer to sit behind a doorway and harass you is useful the way I played.

I was absolutely terrible at that. I had really bad homework grades and completion rates exactly because of shit like that.

"You gave me a 500 word question. I can't make 1500 words out of it. If I'm going to fail anyways fuck turning it in." (No, no part of that approach was intelligent, but I just couldn't fill space with obvious trash. My brain would shut down.)

Yeah, I get shit occasionally in random places for using bigger words when they actually would take multiple sentences to replace.

But there are a fucking lot of people who use big (or obscure) words purely as a kind of signaling that they're smart, rather than for communication. And it's usually really obvious to people who have better vocabularies (or better understanding of the jargon in a specific field) that they don't know what they're doing.

If after looking up a word, the rationale for the word choice doesn't become understandable on at least some level, it's probably nonsense. (There are some super smart people who just don't know how to communicate though and think the word's as simple to everyone else as to them.)

I wonder if PS3 is recent enough that better practices around source code were there. You'd have a lot better chance of making first party games (the ones that leveraged the hardware the best for the most part, and the ones you have less licensing issues with) run well if you could recompile them instead of trying to translate code heavily optimized for that architecture.

That was how the put them in buckets.

But I think it's at least as likely as not that whoever wrote that rule chose those buckets to be "unclean" because people got more sick more often. "I got sick once after eating it" is still one of the biggest reasons some people don't like seafood. Your brain is very good at turning single bad events into "don't touch this" if there isn't a body of safe interactions to fall back to.

Cloudflare's (pretty good IMO) response was pretty indicative of how bad this was. It sounded a lot to me (without that low level of familiarity of exactly everything they offer) like they specifically built some new tooling just to handle this issue at scale. They definitely said that changing links on pages (without an opt in for free users, who generally are less advanced/serious) is not something that they want to do, which is good, but I do think this specific scenario justified defaulting to enabled for customers who aren't paying for the service.

Was that not kind of known at the time? Common knowledge isn't the right phrase, because AMD and especially AMD's financial situation are pretty unknown to most people, but I definitely had a level of understanding that AMD was in rough shape financially and that Sony's big commitment to guaranteed volume was a pretty big deal for them.

Such source code isn't possible with the general audience service they offer, even if being open source were a requirement for credibility in any way.

You're comparing them to a company with a long history of actively hostile behavior despite the fact that there's never been a single hint of anything resembling hostile behavior from them, they operate from a country with meaningful privacy protections and only surrender data when compelled by their own courts (who only do so in circumstances that actually warrant it), and haven't actually given up information that's useful when required to because they don't have it.

I'll tell you what. When proton ships a product that takes a screenshot of my desktop every 5 seconds and stores it in an unsecured DB any user on my computer can access, we'll call them even.

Certain loans and contracts can prevent you from being able to sell something without the lien being lifted.

For example, if you have a mortgage on a house, or in some cases if you're paying a contractor to do renovations, you can't just sell the house out from underneath them and run with the cash. Someone "buying" shit with a lien on it could outright lose it in some circumstances (though it would be pretty hard to get there for land because the process is so protracted).

Not for the battery itself.

They are allowed to void your warranty, if, for example, they can show it's delivering out of spec voltage and that damaged the SoC.

To be fair, I absolutely respect keeping the development focused. Feature creep keeps projects from getting core shit done properly.

No, it isn't even a little hard. It's super simple pre-parsing of the input that can trivially be done client side before the query even touches their server. Advanced users who use those tools are perfectly capable of taking the extra step to indicate to the engine that they're doing a real search, and the worst case is still far less intensive per search than any of the LLM nonsense they added to every search and is almost never useful in any way.

They choose not to. It's exactly that simple.