Since we're not passing any inputs to ListAccounts, it makes sense to use .run! instead of .run. If it failed, that would mean we probably messed up writing the interaction.

identity theft

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

As a workaround, I guess I'll have to disable my strict CSP in development, but I'd prefer to keep it strict in development as well so that I ran into any CSP issues sooner...

How Sprockets works

The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.

The new call API is much more consistent and takes away another thing we kept explaining to new users - an indicator for a flawed API.

multiple learned and generalized affectional responses are formed.

The frightened or ailing child clings to its mother, not its father; and this selective responsiveness in times of distress, disturbance, or danger may be used as a measure of the strength of affectional bonds. We have tested this kind of differential responsiveness by presenting to the infants in their cages, in the presence of the two mothers, various fear-producing stimuli such as the moving toy bear illustrated in Figure 13. A typical response to a fear stimulus is shown in Figure 14, and the data on differential responsiveness are presented in Figure 15. It is apparent that the cloth mother is highly preferred over the wire one, and this differential selectivity is enhanced by age and experience. In this situation, the variable of nursing appears to be of absolutely no importance: the infant consistently seeks the soft mother surrogate regardless of nursing condition.

Psychologists, at least psychologists who write textbooks, not only show no interest in the origin and development of love or affection, but they seem to be unaware of its very existence.

online curation is:

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

These two mistakes, especially the second one, plant worries in your customers mind before they’ve even had time to think of them.

Stop warning people – no contract, no obligations, cancel anytime – companies can’t resist saying this on every pricing page but by using negative words they’re just putting ideas into people’s heads.

Now if you think about it, PJAX sounds a lot like Turbolinks. They both use JS to fetch server-rendered HTML and put it into the DOM. They both do caching and manage the forward and back buttons. It's almost as if the Rails team took a technique developed elsewhere and just rebranded it.

Worked

Because the backing window is so small, all the normal stretch goals are already included

the game have no DLC because every part of it is in place and cutting it to pieces is like commiting straight felony.

cultural capital

Well, a click funnel is basically an online sales funnel, but it’s widely referred to as a click funnel due to the growing popularity of the software called “Clickfunnels”.

Although it is open-source, Snap on the other hand, only works with the Ubuntu Store. Nobody knows how to make a Snap Store and nobody can. The Snap client is designed to work with only one source, following a protocol which isn’t open, and using only one authentication system. Snapd is nothing on its own, it can only work with the Ubuntu Store.

Canonical would do well to make sure they dont complicate things for whatever the next big Linux shift is.

but really, the whole is what feels so good.

Does anyone know how to make npm use a specific fork containing a bug fix while waiting for maintainer to merge a pull request? I was just going to point my package.json to this fork, like this: "svelte-material-ui": "https://github.com/vtpatrickeddy/svelte-material-ui.git#patch-1", but that doesn't work because the repo is a monorepo. And there doesn't appear to be a way to specify a subdirectory inside it, like: "@smui/textfield": "https://github.com/vtpatrickeddy/svelte-material-ui.git/packages/textarea#patch-1",

My focus is on make the API as simpler as possible to allows easy integration without even reading the docs but keeping and expand current features.

However, this construct is not completely equivalent to if ... fi in the general case.

Because module members are usually used with a namespace, short and simple names are usually the most readable option. But those names might not make sense outside the module they’re defined in, so @forward has the option of adding an extra prefix to all the members it forwards.

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

Frontend frameworks are a positive sum game! Svelte has no monopoly on the compiler paradigm either. Just like I think React is worth learning for the mental model it imparts, where UI is a (pure) function of state, I think the frontend framework-as-compiler paradigm is worth understanding. We're going to see a lot more of it because the tradeoffs are fantastic, to where it'll be a boring talking point before we know it.

He highlights the Memex’s killer feature of associative linking and how trails of links have never been implemented in the way the Memex envisioned: It is associative indexing though, that is the essential feature of the memex, “the process of tying two items together is the important thing.” Bush describes a hypertext like mechanism at this point, but most interesting from my perspective is his emphasis on a trail as a fundamental unit — something we largely seem to have lost today. […] Documents and links we have aplenty. But where are our trails?

I don't think the heading/bearing split is as clear-cut as that.

This is the intended behavior.

"The Map is not the territory" —Alfred Korzybski

Alfred Korzybski remarked that "the map is not the territory" and that "the word is not the thing", encapsulating his view that an abstraction derived from something, or a reaction to it, is not the thing itself.

"The menu is not the meal."

A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.

npm install npm run dev

I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.

If there was a place I thought reactivity would be weak, I embraced it and I worked on it until I was happy with the results.

I started Solid years ago before I thought anyone would be interested in using it. I only started promoting it because it had already achieved the goals I had set out for it.

both copied much of their API from Redux Form, so, despite working very differently under the hood, there is a lot of overlap in their APIs.

There’s an entire category of products commonly known as Platform as a Service (PaaS) that endeavors to make this possible. But, so far, these services have largely fallen short of what developers need. Many of our customers have come to DigitalOcean after their PaaS became too expensive, or after hitting various limitations.

I don't read comments as I think they are dangerous

If you’ve used Flow before, the syntax is fairly similar. One difference is that we’ve added a few restrictions to avoid code that might appear ambiguous.

But because it is espoused by so many leading members of the JavaScript community, scrutiny is all too rarely applied.

It’s written by Sindre Sorhus, whose npm profile is enough to make all but the most prolific developer feel wholly inadequate, and so carries with it a degree of authority.

For context, the previous API had a lazy promise. Currently I’m thinking we could just return a closure like in the React API

This is the same as useEffect in React, incidentally — the function must be synchronous in order to avoid race conditions.

The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.

Does it look like a decorator plugin in Ractive, right

The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)

Make sure students can reach out to you privately to let you know if anything about the experience was uncomfortable for them.

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 huge part of the value on an RFC is defining the problem clearly, collecting use cases, showing how others have solved a problem, etc.

An RFC can provide tremendous value without the design described in it being accepted.

For a non-monorepo package you can simply point directly to the Github repo. This case is similar, but you want to scope it just to a single package within the repo. For those that make monorepos they don't necessarily need this feature. It's for those that use projects that use monorepos. Telling them to not organize their projects into monorepos doesn't help people who make use of these projects.

If npm installs a git repo, it assumes that the git repo is the package. I don't really know how we could specify a sub-path easily, since all parts of the git url are already used for other things.

This is more a rhetoric question as this seems to be quite hard ;-) There is a long discussion about installing a subfolder of a repository and monorepos in general at the NPM Github issues (yarn misses this feature, too). The thing is that this makes it quite hard to report issues of your project as one can't test the current master easily. Do you recommend a way how to use the latest Github version?

As a web designer, I hate that "log in" creates a visual space between the words. If you line up "Log In Register" - is that three links or two? This creates a Gestalt problem, meaning you have to really fiddle with spacing to get the word groupings right, without using pipe characters.

There is an observable widespread tendency to give an awk answer to almost everything, but that should not be inferred as a rule to be followed, and if there's (say) a Python answer that involves less programming then surely that is quite on point as an answer for a readership of users.

Article 7(3) of the GDPR prescribes that the controller must ensure that consent can be withdrawn bythe data subject as easy as giving consent and at any given time. The GDPR does not say that givingand withdrawing consent must always be done through the same action.

consent is obtained through use of a service-specific user interface (for example, via a website, an app,a log-on account, the interface of an IoT device or by e-mail), there is no doubt a data subject must beable to withdraw consent via the same electronic interface, as switching to another interface for thesole reason of withdrawing consentwould require undue effort.

The controller informs customers that they havethe possibility to withdraw consent. To do this, they could contact a call centre on business daysbetween 8am and 5pm, free of charge. The controller in this example doesnotcomply with article 7(3)of the GDPR. Withdrawing consent in this case requires a telephone call during business hours, this ismore burdensome than the one mouse-click needed for giving consent through the online ticketvendor, which is open 24/7.

This follows the original vision of the Web as a space for collaboration and not just a one-way publishing medium.

Creating and calling a default proc is a waste of time, and Cramming everything into one line using tortured constructs doesn't make the code more efficient--it just makes the code harder to understand.

By honoring the mammae as sign and symbol of the highest class ofanimals, Linnaeus assigned a new value to the female, especially women’s unique rolein reproduction

on a stage two feet high, along which she was led by her keeper, and exhibited like awild beast; being obliged to walk, stand, or sit as he ordered her.”6

reast shapes amonghumans

functions-as-a-service (FaaS)

Because we would eventually rebalance our test suite across many nodes, we would quickly hit a bottleneck. Our test suite would only be as fast as our slowest test file.

Have adopted CI best practices and are defining their CI/CD pipelines as code

The administration and its allies fear that the more people gravitate toward the successful, free-market self-insurance approach, the worse their government-engineered health “reform” will look. We’re already seeing the beginning of this trend.

Authors of third-party tools should prefix each label key with the reverse DNS notation of a domain they own, such as com.example.some-label.

By putting our data in the corporate cloud, we are that kid. We are giving corporations and governments a way to see where we are looking towards, and they can predict our future and decide whether and how to intervene or subvert.

From a game theoretic standpoint, we’ve already lost. Too many of our civil society adversaries have too much of our data, and we have so little of theirs.

To be fully compliant with GDPR, you would also need to enable Show Reject All Button setting.

The element dem in epidemic, endemic, and pandemic comes from the ancient Greek word demos, which meant people or district:

Taxonomy, in a broad sense the science of classification, but more strictly the classification of living and extinct organisms—i.e., biological classification.

However, since problems are only addressed when they arise, maintenance is reactive rather than proactive. Small problems left unaddressed can balloon into major failures due to focus on cost.

Google charges a lot for their translation tool. It is fairly difficult to build something similar without running up against their free API limits or having the user create an API key.

That’s because the Google Translate extension uses some internal Google-only APIs (Mozilla also does the same thing).

Add-ons must function only as described, and should provide an appealing user experience. Based on the description of the add-on, a user must be able to understand and use the add-on’s features without requiring expert knowledge.

Apparently Firefox does have translation built-in, it's just not enabled due to lack of usage agreement / API keys. https://hg.mozilla.org/mozilla-central/rev/a3eb8e502006

The notices were meant as a jumping-off point where people could begin the journey of understanding how each of their applications and the websites they visit use their data. But, they have probably had the opposite effect

Despite their awarded diplomas in the art of writing, you'd be surprised at how many editors and journalists in the United States make English mistakes. For instance, "an" is still often coupled with words that begin with an "H" sound, even though this is improper. I'd advise against treating material from news sources as if it were error-free or even a higher authority on grammar.

Potential for political focus on building new features over technical improvements (such as refactoring)

You see entropy is information leaking. When it comes to passwords (and secure systems in general) you want to leak as little information as possible. Otherwise an attacker has information they can use to their advantage.

Download the billions of breached passwords and blacklist them all. Attackers have a copy; so should you.

This isn’t the first time Kerckhoffs’ Principle has come up. I specifically discussed it when talking about creating good, strong Master Passwords, when I said that we should use a system for coming up with Master Passwords that doesn’t lose its strength if the attacker knows the system that we used

Kerckhoffs’ Principle states that you should assume that your adversary knows as much about the system you use as you do. This is why – despite what I may have said on April Fools Day last year – security experts are skeptical of security systems that hide the details of how they operate. They are particularly skeptical of systems that derive their security from keeping the details of how they work secret. I could go on at great length about why openness about the system improves security. Indeed, my first draft of this article did go on at great length.

"the enemy knows the system"

"one ought to design systems under the assumption that the enemy will immediately gain full familiarity with them"

Although we don’t anticipate publishing source code for manipulating 1Password keychains, others, unaffiliated with AgileBits, have done so.

“The source code for Falcon is so good, I almost prefer it to documentation. It basically can’t be wrong.”

This is a great time to individualize instruction and have students work at different paces. You don’t want 100-120 papers coming at you all at one time. Spread it out, and it will keep you from getting short-tempered with your students.

That outcome, in fact, is why the General Data Protection Regulation has been introduced. GDPR is being billed by the EU as the biggest shake-up of data privacy regulations since the birth of the web, saying it sets new standards in the wake of the recent Facebook data harvesting scandal.

Rojas-Lozano claimed that the second part of Google’s two-part CAPTCHA feature, which requires users to transcribe and type into a box a distorted image of words, letters or numbers before entering its site, is also used to transcribe words that a computer cannot read to assist with Google’s book digitization service. By not disclosing that, she argued, Google was getting free labor from its users.

I refuse to work for Google and specially not if I am not getting a salary !!!

challenges/unpaid work assignments for Google

Since Rails doesn't restrict the symbols that you use to set I18n.locale, you can leverage this system to display different content depending on anything you like. For example, suppose you have some "expert" users that should see different pages from "normal" users.