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.

we know from Lab studies that children understand the meaning of stuff at first or second or third site you

here are seven classes of fats in our diet seven and some of them will save your life and some of them will kill you

It was enclosed in scare quotes, a sort of acknowledgment that the author knew it was non-standard, but was too apt for the purpose to resist. I remember reading it and trying to think of the “real” word that would be employed there, but could not find a satisfactory alternative. Since then, I’ve found myself unable to resist using the word when appropriate, due to its utility!

Who says it's not a word? Not a word, simply because lexicographers have not recognized it? When a lexicographer recognizes it, it has already been in use! Even Mr. Fiske says it is a word, although he obviously disprefers it.

on reasonable uses of "disprefer" — it's probably true that its meaning is not immediately apparent, and using it when addressing general audiences probably avoided (dispreferred?), but of course, it depends on the context I think. It is a term that has an obvious jargon aspect, but that doesn't seem to me to make it uniformly verboten. Other, DNA would never have entered the popular lexicon, or quantum… I'm sure those parallels are inapt in several ways, but my point, which I think still stands, is that while clarity to the broadest audience possible is often a laudable goal, this also doesn't mean it should be the only or always the chief goal. It seems to me technical words get disseminated and incorporated popularly through their use outside of strictly technical fora, and while several people said they did a double take or didn't immediately understand the word (or misunderstood its meaning), it's also true that this can happen with perfectly reasonable, standard vernacular constructions, especially reasonable standard constructions that are expressing a counter-intuitive (even if true) claim. Just sayin' — "can people understand this without giving it but a moment's thought" is a high (or ultra-low) car to hold all non-technical communication to. (That said, I also have a love for arcane words, shades of meaning, and being able to express certain moods/valences/concepts precisely. THAT said, I'm no linguist, and probably won't be using this word commonly for all my talk.)

The main problem with disprefer is that it violates de Buitléir's rule: If *I* use a word you're not familiar with, your education or experience is lacking. If *you* use a word I'm not familiar with, you're being a show-off or making up words.

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.

enough versus feasible dilemma

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.

But how much readability are enough?

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.

I thought something like git rev-parse --abbrev-ref origin/HEAD would work, but that just seems to show what the default branch was of the repo it was cloned from, at the time of cloning, provided that the remote we cloned from was named origin.

Let us briefly discuss three specific examples of concepts that seem particularly promising for theprospect of ‘good enough world’ and could become synergistically interrelated: (a) the social policy ofunconditional basic income, (b) the development of blockchains and (c) the idea of the offer networks

A Good Enough World

the Internet can potentially becomea backbone to a ‘global commons,’ an immense free space of information, products and services towhich everyone can contribute to and from which everyone can profit [51, 52 ].

The human takeover needs to be nonviolent and genuinely creative. It can augment the entirehuman social system not by resolving the gridlock of all the colliding identities and trajectoriesmentioned in Section 2 but by adding a lifeline for humans to hold on to whenever they considermaking a decision that challenges and disrupts; whenever they allow a new thought to take shape;whenever they genuinely feel the genuine need to say ‘no,’ or ‘yes,’ but today must say otherwise.

The ‘ideal’ is nothing other thana representation of social conditioning and the installation of a personware module into the newbornhuman that tries to accord what is with what the social system projects. We acknowledge of course thatsome mediation is always needed. The baby sees the world and the social world in particular throughthe eyes of the parent and only afterwards autonomously. This mediation is crucial to the cognitivedevelopment of the person and cannot happen without a personware. But the personware can beconstructed such that it empowers the individual and does not subjugate it to the social demands.

As for publishing this as an actual gem on rubygems.org...I have enough open source I'm involved in all ready (or too much, as my wife would probably say) and I'm not really interested in maintaining another gem.

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.

"Put as much information about the problem itself into the email". This is where you show your ability to know what is important and relevant and establish your technical level. Don't be brief, don't imply, and break it down Barney style so the person receiving it knows to escalate your ticket.

Look for certain questions that have been asked every time, and put those answers into the initial email you send about the new problem. Try to add things that make the potential problem sound local. The more information you give them that you know they will be asking for in their script, the faster you will get someone who can help you. And they will thank you for it.

If you email helpdesk (us specifically), if you use appropriate technical detail you will probably get someone who knows what they're doing, and will greatly appreciate it. If you call, you will get me only. I will ask you lots of questions, with awkward pauses in between while I write my notes, and at the end of it I probably won't be able to help you. Technical detail is still welcome, but there are some questions I will ask you anyway even if they sound useless to you

Put as much information about the problem itself into the email, within reason. No need to write a paragraph, that takes time away from you and from us. Bullet points are perfect (preferred).

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.

Also, the img is liquid/fluid, the height of the div/img are unknown, and the width is set to 800px and max-width to 80%.

# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end

find_field finds by id, name or placeholder text - so find_field('Prefix') should find the element with matching placeholder text rather than needing xpath.

but I like that Svelte comes with a good CSS story out the box.

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.

I don't use remote editing much so vim-dirvish is powerful enough to manage my workflow (It's actually faster than netrw ~ the author claims 2x, I feel it's faster than that - it's really instantaneous ⚡) very useful on large codebase/repositories

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

Yes, it's true that it returns a single file, but with the more robust caching in 4.0 it works well enough in my experience.

With these JavaScript techniques, the display of server validation errors could be a lot simpler if you expect most of your users to have JS enabled. For example, Rails still encourages you to dump all validation errors at the top of a form, which is lulzy in this age of touchy UX. But you could do that minimal thing with server errors, then rely on HTML5 validation to provide a good user experience for the vast majority of your users.

Please note that the I/O DSL is only providing the most-used requirements. Feel free to use the low-level taskWrap API to build your own variable mapping with different scoping techniques.

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.

In both filters, you’re able to rename and coerce variables. This gives you a bit more control than the simpler DSL.

For this one we'll define a helper method to handle raising the correct errors. We have to do this because calling .run! would raise an ActiveInteraction::InvalidInteractionError instead of an ActiveRecord::RecordNotFound. That means Rails would render a 500 instead of a 404.

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

If components gain the slot attribute, then it would be possible to implement the proposed behavior of <svelte:fragment /> by creating a component that has a default slot with out any wrappers. However, I think it's still a good idea to add <svelte:fragment /> so everyone who encounters this common use case doesn't have to come up with their own slightly different solutions.

@monkeythedev can your work be used already? I would suggest not yet, i'm still doing core changes every day

The main reason to use these lower-level components is if you need to customize your form input in some way that isn't supported using TextField.

Internal Sass features have also moved into the module system, so we have complete control over the global namespace.

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.

withindex.js, we have a single source of truth, giving fine grained control on what we expose to the outside world.

The reason that this solves our problem is: we now have full control over the module loading order. Whatever the import order in internal.js is, will be our module loading order.

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.

Virtual DOM is valuable because it allows you to build apps without thinking about state transitions, with performance that is generally good enough

But the vast majority of things that our apps are doing are just conditional and list rendering.

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

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

"AOO is not, and isn't designed to be, the 'super coolest open source office suite with all the latest bells and whistles,'" Jagielski continued. "Our research shows that a 'basic,' functional office suite, which is streamlined with a 'simple' and uncluttered, uncomplicated UI, serves an incredible under-represented community.

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.

Integration specs are relied upon to ensure the application functions, but does not ensure pixel-level stylistic perfection.

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:

Describe the problem fully Link to a test case showing the problem.

Without this information, very likely your question will not be answered, frustrating both yourself and anyone else who does want to help, because they are unable to do so

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

A well-de- veloped color, then, appears to partake of the "body" metaphor more than of the "painting" metaphor, for it is an integrated, unitary, natural- seeming part of the argument that persuades by its appearance of truth (lnst. 11.1.58-59), while a speech whose co/ores are discernibly "added-on" and not integrated fails to persuade