our sensory systems on Darwin's theory were not shaped to show us the truth. They were shaped to keep you alive long enough to reproduce successfully. Period. That's all Dharm's theory actually says

Another way to say what 'Bestfrog' said, when you are trying to close a door you produce torque the torque formula is defined by T = F (the force you make) * d (the distance from the point where the door is atached to the wall, the 'pivot point') so, the further you push the door from its pivot point, the greater the torque and easier it is to close / open it (hope you understood it, otherwise just send more questions - this is my first time trying to answer something :) )

Another way to say what 'Bestfrog' said, when you are trying to close a door you produce torque the torque formula is defined by T = F (the force you make) * d (the distance from the point where the door is atached to the wall, the 'pivot point') so, the further you push the door from its pivot point, the greater the torque and easier it is to close / open it (hope you understood it, otherwise just send more questions - this is my first time trying to answer something :) )

consensus

Developers want to improve their project. If you find an issue, bring it up. If it's a valid concern, the author will probably want to have it fixed. In many cases, the author will consider it a valid issue, but simply not have the personal time or need to address it immediately. This is where open-source is great. Just fork the project and fix it

That's not enough to help you.

This start-over style of key rotation may well be one of the main reasons that PGP's web-of-trust failed [WOT]. Without a universally verifiable revocation mechanism, then any rotation (revocation and replacement) assertions either explicit or implicit are mutually independent of each other. This lack of universal cryptographic verifiability of a rotation fosters ambiguity at any point in time as to the actual valid mapping between the identifier and its controlling keypair(s). In other words, for a given identifier, any or all assertions made by some set of CAs may be potentially valid

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

he said to Harry Belafonte, he said, you know, I think we're going to win the battle of integration. He, I think that we will get that. But he said, but I worry that I'm integrating my people into a burning house. 00:17:26 And I think that's a perfect metaphor. I mean, you're trying to get people of color to have jobs or to own houses, but meanwhile, it's hard for anyone to own a house now with interest rates going up and prices so high. Jobs themselves are being destroyed. And so it's not enough to integrate into the economy as it is. We need to transform that economy.

If it's dangerous, note it in the class/method Javadocs, don't just blindly slam the door shut.

Using --ours did what I was after, just discarding the incoming cherry picked file. @Juan you're totally right about those warning messages needing to say what they did't do, not just why they didn't do it. And a bit more explanation that the ambiguity from the conflict needs to be resolved (by using --ours, etc) would be super helpful to this error message.

Don’t let the perfect be the enemy of the good. Seat belts aren’t perfect either, do you argue we shouldn’t wear them? Etc, etc. This argument only works if what you’re defending is good. As I’ve already explained, SMS-2FA is not good.

If you use a third party password manager, you might not realize that modern browsers have password management built in with a beautiful UX. Frankly, it’s harder to not use it.

If you’re a security conscious user... You don’t need SMS-2FA. You can use unique passwords, this makes you immune to credential stuffing and reduces the impact of phishing. If you use the password manager built in to modern browsers, it can effectively eliminate phishing as well.

Result of lots of searching on net is that pre-checkout hook in git is not implemented yet. The reason can be: There is no practical use. I do have a case It can be achieved by any other means. Please tell me how? Its too difficult to implement. I don't think this is a valid reason

There are also many reasons refresh tokens may expire prior to any expected lifetime of them as well.

Source Code is currently understaffed and working through our P2 bugs at the moment.

Maybe one day, JSON Schema would be able to express all the constraints in the OpenAPI spec, but I suspect some are going to be really hard.

When we do release a final version of JSON Schema, please do not use JSON Schema to guarantee an OpenAPI document is valid. It cannot do that. There are numerous constraints in the written specification that cannot be expressed in JSON Schema.

Let's not get over-excited. Actually, we're only part-way there; you can compile this code with the TypeScript compiler.... But is that enough?I bundle my TypeScript with ts-loader and webpack. If I try and use my new exciting import statement above with my build system then disappointment is in my future. webpack will be all like "import whuuuuuuuut?"You see, webpack doesn't know what we told the TypeScript compiler in the tsconfig.json.

Actually, I've decided to stop using labels for a while. A "bug" label gives the impression that someone else is going to fix the problem. We don't have enough volunteers for that (new contributors welcome!). I try to help people working on issues, though. I've spent many hours on this one.

We also know people need a good sized group and time to see the impact and value of a platform like Stack Overflow for Teams. Our previous 30 day free trial of our Basic tier wasn’t long enough. Now, Stack Overflow for Teams has a free tier for up to 50 users, forever.

What produces that text, and what do you want to use it for?

I have already tried '--ignore-failed-read', but the problem is that it doesn't only ignore failed reads on the -T files. It ignores all failed reads.

I`m getting "rsync warning: some files vanished before they could be transferred (code 24) at main.c(1518) [generator=3.0.9]" on one of my systems i`m backing up with rsync , but rsync doesn`t show WHICH files.

With all this “monetization” happening around Trailblazer, we will also make sure that all free and paid parts of the project grow adult and maintan an LTS - or long-term support - status. Those are good news to all you users out there having been scared to use gems of this project, not knowing whether or not they’re being maintained, breaking code in the future or making your developers addicted to and then cutting off the supply chain. Trailblazer 2.1 onwards is LTS, and the last 1 ½ years of collaboration have proven that.

However, since you haven't yet provided any details about how you built with Qt (Qt isn't officially supported, so you must have used a third party derivative of vim), and you haven't provided any detailed information about what error messages or malfunctions you're having with python-complete, it's not really possible to tell you how to fix the problem and get vim working with Qt.

Sure, you have a few extra newlines and semicolons, but the minifier will remove them anyway so no harm.

Another big issue is that the config wasn’t really expressive enough. From the beginning Rails needed a way to say “only compile application.css and application.js, but compile ALL images” by default. With our previous interface, we’re limited to only strings.

We could of course refactor our code to rename things any time we like, but we don’t do this enough in practice

I came up with this solution by piecing together man pages and random google result. I was surprised at how many incomplete and inaccurate answers were out there. What may have been more surprising was the complete lack of a full intact solution.

Of all the compile-to-languages, the one that strikes me as having the least merit is JSX. It's basically a ton of added complexity for the sake of what boils down to syntax. There are no real gains in terms of language semantics in JSX.

I agree that "it feels gross" is a bad reason. "not paving a bad cowpath" is a much better reason.

Moreover, React team even removed the “highlight updates” feature from dev tools because people used to obsessively haunt wasted renders with no reasoning behind it

Unfortunately people lack the the time to invest to really understand those things

It's really not enough space. I have two 16 Gbyte phones, and I'm constantly deleting and restoring apps to make space, or getting the "not enough space to update" message. My other tablet with 32 Gbytes is fine.

Account Support If you haven't received your confirmation email, you can request to resend your confirmation instructions via our confirmation page.

In the future, these attributes may expand without the API being versioned. The current attributes are:

the feature was dropped to “lack of use.”

No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.

The problem occurs when the maintainer of the package is too busy to merge my PR, so I'm just stuck with my fork.

ports many programming languages and markup languages, and functions can be added by users with plugins, typically community-built a