click the images below

It means "You're about to talk about words, but words don't matter."

This content is not compatible on this device.

Dole Mandarin Oranges in Light Syrup, All Natural Fruit, Non-GMO, 15oz CanNot available for curbside

Very often in these monorepos, packages are so incredibly specific in functionality, the question then becomes why even have a separate package at all if it’s tightly coupled? Can you use these packages independently or are they tied to specific versions of other packages in the monorepo? It’ll probably be easier to remove the mask and just work as a monolith.

"Functions Are Not Packages" - Well why not?

for whatever reasons, it hasn’t really liberated anyone from JavaScript.

antimicro is a graphical program used to map keyboard keys and mouse controls to a gamepad.

I don't understand why this isn't being considered a bigger deal by maintainrs/the community. Don't most Rails developers use SCSS? It's included by default in a new Rails app. Along with sprockets 4. I am mystified how anyone is managing to debug CSS in Rails at all these days, that this issue is being ignored makes sprockets seem like abandonware to me, or makes me wonder if nobody else is using sprockets 4, or what!

concatenation still occurs.

Reopening #162

Yes, but honestly, and no offense intended, but I don't see the harm in these type questions, nor why some people are offended when they are asked. If I owed a website, I wouldn't mind it because it just creates more pages that can be indexed. I see it as helping the website. But, I did look and didn't see a simple answer. Again, no offense is intended. I've just never understood the complaints.

So why the over-complication? What we got now is replicating a chain of && in the former version. This time, however, you will know which condition failed and what went in by using tracing. Look at the trace above - it’s impossible to not understand what was going on.

signal.to_h[:semantic]

At the request of the publisher, Tales of Monkey Island Complete Pack: Chapter 2 - The Siege of Spinner Cay is unlisted on the Steam store and will not appear in search.

In the course of the negotiations, certain promises were made by the merchants--for example, to remove the stores' humiliating racial signs

But since I feel that you are men of genuine good will and that your criticisms are sincerely set forth, I want to try to answer your statement in what I hope will be patient and reasonable terms.

But why do we return 0? Why not 1? Why not None? And while None in most cases is as bad (or even worse) than the exceptions, turns out we should heavily rely on business logic and use-cases of this function.

Why is TRB licensed under LGPL, not MIT?

compose(Add, x: x, y: 3)

Add.run(x: x, y: 3)

Why is all this interaction code better? Two reasons: One, you can reuse the FindAccount interaction in other places, like your API controller or a Resque task. And two, if you want to change how accounts are found, you only have to change one place.

Any idea @AaronLasseigne if this is mergeable?

Learn more about how we made the decision to put our guidance in the public domain

In order to support easy reuse, revision, remixing, and redistribution, the entire Hypothesis Help knowledge base by Hypothesis is dedicated to the public domain via CC CC0 1.0. While we appreciate attribution and links back to Hypothesis from anywhere these works are published, they are not required.

I don't think seeing it in Rails PRs naturally means we should do it blankly. Put it another way, what's the justification in those PRs for doing it?

ActiveModel::Form happened because the "tableless model" presented in RailsCast 219 wasn't as powerful as the "real deal" from RailsCast 193.

The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false or nil.

Read about the motivation to understand why this separation of concerns is important.

It makes me happy to see people actually think about things and not just accept a shitty API.

Naming matters for both idealogical and practical reasons.

Anyone who has ever tried to name a child knows that naming is hard. Naming things in code is harder. It’s bad enough that you have to commit to a name that someone isn’t going to like. You also have to be able to live with it.

It's difficult because it's a case-by-case basis - there is no one right answer so it falls into subjective arguments.

Cache invalidation is hard because: Everything in life we want to know, changes.Those changes are non-deterministic.

This game is not currently available in United States.

This question is locked and replying has been disabled.

The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.

We are not allowed to show you historical data for Amazon

Why the ^=? This means "starts with", because we can also have variation placements like top-start.

Why is CORS important? Currently, client-side scripts (e.g., JavaScript) are prevented from accessing much of the Web of Linked Data due to "same origin" restrictions implemented in all major Web browsers. While enabling such access is important for all data, it is especially important for Linked Open Data and related services; without this, our data simply is not open to all clients. If you have public data which doesn't use require cookie or session based authentication to see, then please consider opening it up for universal JavaScript/browser access. For CORS access to anything other than simple, non auth protected resources

The same-origin policy fights one of the most common cyber attacks out there: cross-site request forgery. In this maneuver, a malicious website attempts to take advantage of the browser’s cookie storage system.

Why? I wrote MagpieRSS out of a frustration with the limitations of existing solutions. In particular many of the existing PHP solutions seemed to: use a parser based on regular expressions, making for an inherently fragile solution only support early versions of RSS discard all the interesting information besides item title, description, and link. not build proper separation between parsing the RSS and displaying it.

On Ubuntu, Chromium is not the default browser, and the package resides in the ‘universe’ section of the archive.

We're sorry, but due to Amazon not allowing us to track "Kindle Edition" products, we don't have any price data for this product.

Why Vala? Many developers want to write GNOME applications and libraries in high-level programming languages but can't or don't want to use C# or Java for various reasons, so they are stuck with C without syntax support for the GObject type system. The Vala compiler allows developers to write complex object-oriented code rapidly while maintaining a standard C API and ABI and keeping the memory requirements low.

Can this be merged please, this fixes a problem I have

May I ask what is holding this back?

These are valid comments. I think it is worth noting that svelte didn’t choose a non-javascript method for fun or because we think we should redesign the language. The additional constructs, for the most part, are there to allow svelte to more clearly work out exactly what is going on in the code in order to optimise. In short svelte needs a certain amount of information to do what it does and pure javascript is often difficult to analyse in this way. But I appreciate your concerns and comments and we try to take all feedback on board where we can. So thank you!

“Why?” you ask. This is for two reasons.

And why?

Man, for some reason, I really like this answer. I recognize it's a bit more complicated, but it seems so useful. And given that I'm no bash expert, it leads me to believe that my logic is faulty, and there's something wrong with this methodology, otherwise, I feel others would have given it more praise. So, what's the problem with this function? Is there anything I should be looking out for here?

Why the urgency? You can always fall back to a full clone.

I see this issue has 2 open PR's is this going to be finalized anytime soon?

Furthermore, how come there's a PR open since 3 months, at what seems to be the authoritative repo for Svelte?

Why is it your solution? Can you talk us through it?

ijc closed this

you grant us a non-exclusive, transferable, sub-licensable, royalty-free, and worldwide license to host, use, distribute, modify, run, copy, publicly perform or display, translate, and create derivative works of your content (consistent with your privacy and application settings).

formvalidation: path.resolve

import luhn from 'formvalidation/algorithms/luhn';

If the react cargo cult didn't have the JSX cowpath paved for them and acclimated to describing their app interface with vanilla javascript, they'd cargo cult around that. It's really about the path of least resistance and familiarity.

My proposal is that we solve this by treating a static key prop as different from one provided through spread. I think that as a second step we might want to even give separate syntax such as:

Why not just use that instead of inventing a syntax that's not part of ECMAScript?

Why not Template Literals?

I chose to use a monorepo: to reduce development friction in managing my various projects to utilize patterns across my projects

Why?

The centralization of information also worries me because it makes it easier for things to disappear.

Some of it is visual. Yes, it is true that all my posts on Twitter and Facebook look something similar to a personal blog: They are collected in reverse-chronological order, on a specific webpage, with direct web addresses to each post. But I have very little control over how it looks like; I can’t personalize it much. My page must follow a uniform look which the designers of the social network decide for me.

But the scariest outcome of the centralization of information in the age of social networks is something else: It is making us all much less powerful in relation to governments and corporations.

So what do we focus on instead, without that ability to tweak or iterate? Well, some of the messier network effects of social media, I’d argue. Sure, leaving a comment may be more “engaging” than picking a color and setting a design, but those things give us a feeling of ownership that we never really feel like we have when they’re all decided for us.

We are sharded beings; the sum total of our various aspects as contained within our biological beings as well as the myriad of technologies that we use to extend our biological abilities.

Reversing the trend toward privatization will thus require not just massive public mobilization and demand of elected officials, but also a hard turn away from efficiency as a primary value, a recognition that the building of relationships and the cultivation of care is slow and difficult and of necessity inefficient. In fact, that its value lies in its inefficiency — but making the case for such inefficiency as a necessary value requires a lot of effort, and a lot of caution.

Update, 11:22 Eastern: Weiss has posted a letter of resignation addressed to Times publisher A.G. Sulzberger on her website. In it, she denounces the Times for fostering an atmosphere of stifling conformity and accuses her now-former colleagues of bullying:

Well, in the past, because I constrained myself to only writing long posts, my blog would only show activity when I was feeling motivated to write something longer. And that motivation definitely ebbs and flows. But now, if I want to just throw up a note or post a quick picture, I can, as easily as I could post a status update to Facebook. And instead of just posting to my blog and hoping someone sees it, I can make that content visible on social networks like Twitter, which leads to engagements that, again, come back to my blog. The end result is that my blog, the space I’ve created for myself on the web, is much more dynamic and alive. And that’s pretty darn exciting!

This dynamic is playing out during the pandemic among the many people who refuse to wear masks or practice social distancing.

Why do we use bundlers again?Historically, bundlers have been used in order to support CommonJS files in the browser, by concatenating them all into a single file. Bundlers detected usages of require() and module.exports and wrap them all with a lightweight CommonJS runtime. Other benefits were allowing you to serve your app as a single file, rather than having the user download several scripts which can be more time consuming.

the error/warning output about unresolved dependencies and missing global variable names doesn't provide any more information about which dependencies are part of the problem:

Why do I need a global variable? Is the global requirement from ES6 modules (I'd have thought modules would be in a functional scope) or rollup?

The Why

Lorem Ipsum

DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.

When the message say function was called outside component initialization first will look at my code and last at my configuration.

We could at least try to offer better error message for this, before it becomes our next NullPointerException, Segmentation Fault or Kernel Panic

It would be tiresome - and bloated - to include a class pass-through for every component or assigning custom properties (from the RFC linked) for all potential properties on every component, just in case it's gonna be used in layouts that requires it. Wrapping them in a wrapper div is certainly an option, but potentially creates 100s or 1000s (long lists, several lists etc.) of new elements in the DOM slowing down low-end devices.

This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.

Your tooltip component will have to wrap your image with a span tag or something, it can’t just add events to its children. And if you are adding multiple actions to it you will have to wrap it multiple times.

<Concern1> <Concern2> </Concern2> </Concern1>

vs.

<img use:concern1 use:concern2>

You can imagine the ensuing combinatorial explosion if we needed to add borders or box shadows or filters or what-have-you.

If this was tied into Svelte's flow with hooks this would not be necessary since it would know when it was being removed from the DOM.

You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)

This is where hooks/behaviors are a good idea. They clean up your component code a lot. Also, it helps a ton since you don't get create/destroy events for elements that are inside {{#if}} and {{#each}}. That could become very burdensome to try and add/remove functionality with elements as they are added/removed within a component.

Drag and drop might be done better with hooks than components.

Nic Fildes in London and Javier Espinoza in Brussels April 8 2020 Jump to comments section Print this page Be the first to know about every new Coronavirus story Get instant email alerts When the World Health Organization launched a 2007 initiative to eliminate malaria on Zanzibar, it turned to an unusual source to track the spread of the disease between the island and mainland Africa: mobile phones sold by Tanzania’s telecoms groups including Vodafone, the UK mobile operator.Working together with researchers at Southampton university, Vodafone began compiling sets of location data from mobile phones in the areas where cases of the disease had been recorded. Mapping how populations move between locations has proved invaluable in tracking and responding to epidemics. The Zanzibar project has been replicated by academics across the continent to monitor other deadly diseases, including Ebola in west Africa.“Diseases don’t respect national borders,” says Andy Tatem, an epidemiologist at Southampton who has worked with Vodafone in Africa. “Understanding how diseases and pathogens flow through populations using mobile phone data is vital.”

the best way to track the spread of the pandemic is to use heatmaps built on data of multiple phones which, if overlaid with medical data, can predict how the virus will spread and determine whether government measures are working.

Why TypeScript?

Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.

A well-formatted and descriptive commit message is very helpful to others for understanding why the change was made, so please take the time to write it.

We stopped using SSH keys, Vít Kotačka answers helped us understand why it was failing before.

Introducing React-Static! How it works and why we built it!

This task disables two-factor authentication (2FA) for all users that have it enabled. This can be useful if GitLab’s config/secrets.yml file has been lost and users are unable to log in, for example.

isConsentGiven()

storeConsent()

Members currently electing to withdraw from the default royalty free license and instead offer Reasonable and Non-Discriminatory (RAND) terms are:

Though not always legally required, a Terms & Conditions (T&C) document (also known as a Terms of Service, End-user license agreement or a Terms of Use agreement) is often necessary for the sake of practicality and safety. It allows you to regulate the contractual relationship between you and your users and is therefore essential for, among other things, setting the terms of use and protecting you from potential liabilities.

I appreciate the vigilance, but it would be even better to actually publish a technical reasoning for why do you folks believe Firefox is above the device owner, and the root user, and why there should be no possibility through any means and configuration protections to enable users to run their own code in the release version of Firefox.

The idea behind the app is to allow people to rent something that they would only use once or very rarely. Rather than buying that expensive drill that you will only use for 15 mins, why not rent it from your neighbor?

Why

def self.broadcast(logger) # :nodoc:

For some unknown and unfortunate reason, this method is undocumented but you can refer to the source code or blog posts to learn how it works or see examples.

My extended dance remix version of why is at

Because it's easier for Indiana Jones to recover the Sankara Stones than for someone with an idea for an App to find a decent App developer.  And because we wanted to finally have a place to send friends and clients who constantly ask for our help in finding developers. Yeah, we know there are more than 140,000 iPhone applications out there already, so not everyone is struggling to find a developer. But believe us, the demand outweights the supply. Hence, this site.

development is hard because you have to preserve the ability to quickly improve the product in the future

The :shallow_prefix option adds the specified parameter to the named route helpers:

Confusingly, all the distributions I use (Ubuntu, RHEL and Cygwin) had some type of check (testing $- or $PS1) to ensure the current shell is interactive. I don’t like cargo cult programming so I set about understanding the purpose of this code in my .bashrc.

No, clumsily working around the root account in situations where it is absolutely appropriate to use it is not for good reasons. This is just another form of cargo cult programming - you don't really understand the concept behind sudo vs root, you just blindly apply the belief "root is bad, sudo is good" because you've read that somewhere.