I feel the pain. It is a normal thing that standards do evolve over time, though, and our software needs to cope with it.

non-interactive complexity assumption

Daniela K. Helbig teaches at the School for History and Philosophy of Science at the University of Sydney. Her research areas are at the intersection of the history and philosophy of technology, and of intellectual history. 

Any news on this? It has been over a year?

“You can’t use HTML5 or CSS3 in email.” Due to their “limited” support, the idea that using HTML5 and CSS3 in email is “impossible” remains a commonly-held notion throughout the email design industry. However, we’re calling it a complete myth.

Just because there can be issues with CSS in HTML emails doesn’t mean you should abandon efforts to use it. It all comes down to determining which codes are absolutely needed and how to style them so they can be rendered by email platforms.

But decentralized learning goes farther than that: in a decentralized, Collaborative Learning environment, each team member participates in the learning process. They can identify their learning needs, request courses, give feedback on existing courses, and create courses themselves. We call this a bottom-up approach

The use of U+212B 'Angstrom sign', which was encoded due to round-trip mapping compatibility with an East-Asian character encoding, is discouraged, and the preferred representation is U+00C5 'capital letter A with ring above', which has the same glyph.

In many computing contexts, "TTY" has become the name for any text terminal, such as an external console device, a user dialing into the system on a modem on a serial port device, a printing or graphical computer terminal on a computer's serial port or the RS-232 port on a USB-to-RS-232 converter attached to a computer's USB port, or even a terminal emulator application in the window system using a pseudoterminal device.

However, some users didn’t know that they could interact with and click on the text field. It looked like an empty box. The line affordance under the old text fields was not clear to some users. The line was confused with a divider.

The label and input were confused with body text, especially in dense compositions.

Not to be confused with tree (graph theory), a specific type of mathematical object.

Not to be confused with trie, a specific type of tree data structure. Not to be confused with tree (graph theory), a specific type of mathematical object.

The is-a relationship may also be contrasted with the instance-of relationship between objects (instances) and types (classes): see Type–token distinction.

So Substack has an editorial policy, but no accountability. And they have terms of service, but no enforcement.

Substack is taking an editorial stance, paying writers who fit that stance, and refusing to be transparent about who those people are.

I suspect you aren't seeing much discussion because those who have a reasonable process in place, and do not consider this situation to be as bad as everyone would have you believe, tend not to comment on it as much.

Any news on this one?

Granted it's a toy example using StringIO

Any update on this?

Sorry to bump this but we're also in the same situation

Now that source maps in production by default seems to be the official Rails position, can we expect some movement on this?

Closing this because it's obviously not going to get fixed and it's cluttering my open issues

An equation is any expression with an equals sign, so your example is by definition an equation. Equations appear frequently in mathematics because mathematicians love to use equal signs. A formula is a set of instructions for creating a desired result. Non-mathematical examples include such things as chemical formulas (two H and one O make H2O), or the formula for Coca-Cola (which is just a list of ingredients). You can argue that these examples are not equations, in the sense that hydrogen and oxygen are not "equal" to water, yet you can use them to make water.

You’d think :empty would be it, but it’s not. That’s for matching things like <p></p>… container elements with nothing inside them. Inputs are no-content elements already.

Dafa ànd ak moroom yi àll ba, fori aloom.

Hey, that’s is an imaginary complication of our example - please don’t do this with every condition you have in your app.

Keeping bootstrap-sass in sync with upstream changes from Bootstrap used to be an error prone and time consuming manual process. With Bootstrap 3 we have introduced a converter that automates this.

In the short term you may have the stamina to get up earlier, stay later, and out-work the demands you face. But the inverse equation of shrinking resources and increasing demands will eventually catch up to you, and at that point how you involve others sets the ceiling of your leadership impact.

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

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.

Now that v4 is released, maybe we can look again into merging this?

It is difficult to come up with content that is not extracted from a real application. Manufacturing scenarios to see if ideas have practical application turned out to be an exhasting and time consuming process.

Is there are any possibility to speedup this pull-request to be merged?

many successful projects have proven that you can develop high-quality code more rapidly (and cost effectively) this way than with the traditional pipelined approach

Did you by any chance ever finish/publish your solution for this?

this is a followup to my question here: Updating child association in ActiveModel

Time: Suppose all your data was immutable, then cache all the data indefinitely. But this isn't always to case so you have to figure out what works for the given scenario (A person's mailing address doesn't change often, but their GPS position does).

Any progress on this issue?

Sean, do you think someone can take a look at this? It's biting a lot of people and makes .or pretty much useless if you want the .or query to use a simple join, which is a pretty common use case. There are 57 likes in this issue alone.

I was wondering what is the status of this issue? The PR that fixes the problem is rejected but this issue is still open, so is it going to be fixed or is it intended behaviour?

Popup - You don't need to deal with these messages right away, yet at some point you will need to take action since these won't go away until explicitly say say you don't want them around anymore.

A pop-up is a modal view that can either take form as a pop-up menu or a pop-up dialog. To my understanding, when we use the word “pop-up”, what we want to express is the pop-up motion effect on the call-out of the UI treatment.

We took a stance on an issue.

Popover is similar to tooltips; it is a pop-up box that appears when user click or hover on an element.

Also agree that <svelte:slot> is perhaps a little confusing since it replaces the slot attribute rather than the slot element, so <svelte:fragment> would make more sense

Event listener and event handler are two terms that cause confusion.

The most basic difference is the association Listener is associated with Event Source (Ex: key board) Handler is associated with an Event (Ex: keydown)

In a browser, the chrome is any visible aspect of a browser aside from the webpages themselves (e.g., toolbars, menu bar, tabs). This is not to be confused with the Google Chrome browser.

There is no rerender, when you call listen, then all scroll events will warn on chrome. See this entry from svelte: breaking the web

if the value given in value is contained in the array that is the value for the field for the form

I also like that the folksonomic approach (as in, there are no “pre-established groups”) allows for a great deal of expression, of negotiation (I imagine that #barcamp will be a common tag between events, but that’s fine, since if there is a collision, say between two separate BarCamps on the same day, they’ll just have to socially engineer a solution and probably pick a new tag, like #barcampblock) and of decay (that is, over time, as tags are used less frequently, other people can reuse them — no domain squatting!).

Obviously we shouldn't rush into anything. But changes like these are best made earlier on in a project's lifecycle, so I'm eager to hear what people think so that we can start making some progress.

When a piece of fabric is cut on the bias and sewn from the bias it has a tendency to create interesting drapes and to enhance the style of a garment. It is just so with human biases. Within an incarnated human’s life there will be a continuing and continuous experience of seeing things from a particular bias or slant, and then being able to choose to rethink and re-vision and see things from the opposite bias.

ra's "special-interest groups" in the rarified realm of epistemology, where traditionally what can count as knowledge is policed by philosophers codifying cognitive

Also, if you don't put that implementation of URLSearchParams in the global scope you're not using it as a polyfill but a ponyfill, and those are meant for your code, not for external dependencies.

However, as a developer that uses JSX, I find it too useful/concise to give up in the name of syntax purity, especially when I know that what it translates to is still very isolated and computationally pure.

In highlighting the dangers of big-up-front-design (BUFD) and waterfall development, Agilists seem to advocate no-up-front-design (NUFD) or no-up-front-requirements (NUFR) or no-up-front-architecture (NUFA).

One of the inherent dangers of any form of iterative development is confusing iteration with oscillation.

To fix our Svelte version you might think we could use beforeUpdate or afterUpdate, but these lifecycle functions are related to the DOM being updated, not to prop updates. We only want to rerun our fetching when the album prop is changed.

It could mean working closely with a platform itself to beta test new products and features. Companies like CNN, The New York Times and The Washington Post have signed on as Facebook media partners and have collectively produced hundreds of Facebook Live broadcasts, for instance. Other brands such as The Wall Street Journal, Cosmopolitan, ESPN and more have teamed up with Snapchat to produce content for Snapchat Discover, Snapchat’s media portal.

Julie Beck argues that unless we do something with what we have read within 24-hours then we often forget it.

Student evaluations of teachers are notoriously biased against women, with women routinely receiving lower scores than their male counterparts.

Second, I have a not-very-well supported theory that’s paired with the book Thinking, Fast and Slow. The behavior design implication of that book is that you need to speak to two systems of the brain. Speaking to the rational, Slow System is easy. Just lay out the facts.Speaking to the emotional Fast System is much harder, namely because it’s so hard to see or introspect on what’s going on in there. But if you accept that difficulty (and this is the part of my theory that feels like pop brain science), then you realize that you need to start looking for ways to rewire your emotional core.Then, having accepted that rewiring your emotions is part of most behavior design, I’ve started to notice things — like that most self-improvement advice is not very rational. That’s by design. A self-improvement book is mostly emotional rewiring. That is exactly why you need to read the entire book rather than cheating with a summarized version.

Does the term alternativemedia exclusively refer to politically progressive, left-wing media that aim at challenging capitalism and corporate (media)power, or does the term also include conservative, right-wing, and repressive media (Downing, 2001, p. 88)

Apologies for being "that person", but are there any updates on this topic or guidance in the meantime?

Because Svelte is a compiler, we're not bound to the peculiarities of JavaScript: we can design a component authoring experience, rather than having to fit it around the semantics of the language.

The benefit of this approach is that rather than having these defaults and fighting against them, it’s fully up to you to decide how to handle everything.

Instead, rather than trying to implement what it thinks is the best way to bundle different type of assets, it leaves that entirely up to the developer to decide.

I'll work on a preliminary PR (which I expect will need some love from maintainers, sorry!)

Note that Array.entries() returns an iterator, which is what allows it to work in the for-of loop; don't confuse this with Object.entries(), which returns an array of key-value pairs.

The feature is highly likely to be implemented, the API and implementation are the only real topics of discussion right now.

6to5 attempted to ship a quick and dirty TDZ static checking feature but had to retract it immediately afterwards due to various bugs in the algorithm.

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.

what might be learned from the case. The answer, in part, is that prudent psychiatrists and other therapists will want to be thoughtful about how they arrange follow-up care for patients whom they can no longer see.Sometimes a general suggestion that a patient seek follow-up care will be adequate. However, as the patient's condition warrants, clinicians might choose, in ascending order of time commitment, to provide the patient with the name of a particular practitioner or facility, to contact the facility to ascertain that a clinician is willing to see the patient, to help the patient make an appointment, or, with the patient's permission, to make an appointment on the patient's behalf. In some cases, it may be appropriate to ask for the patient's permission to contact his or her family to indicate a need for follow-up and to encourage the family to make sure that follow-up takes place. But of these approaches, no specific one will always be indicated, and the degree of assistance rendered the patient should be calibrated to his or her individual needs.

BenchmarkDiscussion

I’ll continue to explore the possibilities and come up with new ideas. You know I love to build my ideas.

I plan to introduce a difference! method as well.

The Paradox of Abundance: The average quality of information is getting worse and worse. But the best stuff is getting better and better. Markets of abundance are simultaneously bad for the median consumer but good for conscious consumers

there’s 3 steps to building software: Make it work Make it right Make it fast

If we can encourage people to create clean commits as they go, the example as you showed above should be far less common, because cleaning up such history as an after-math is most of the time almost impossible.

the phrase up to is used to convey the idea that some objects in the same class — while distinct — may be considered to be equivalent under some condition or transformation

"a and b are equivalent up to X" means that a and b are equivalent, if criterion X, such as rotation or permutation, is ignored

If solutions that differ only by the symmetry operations of rotation and reflection of the board are counted as one, the puzzle has 12 solutions. These are called fundamental solutions; representatives of each are shown below

in order to track the always-improving upstream project, we continuously rebase our patches on top of the upstream master

I need that model created despite being invalid, so it actually works in my favor (I have an after-signup profile creation process users through

Devise-Two-Factor only worries about the backend, leaving the details of the integration up to you. This means that you're responsible for building the UI that drives the gem. While there is an example Rails application included in the gem, it is important to remember that this gem is intentionally very open-ended, and you should build a user experience which fits your individual application.

When you simply accept that "hacker" means "malicious security cracker", you give up the ability to use the term to refer to anything else without potential confusion.

Patients with cardiac injury vs those without cardiac injury had shorter durations from symptom onset to follow-up (mean, 15.6 [range, 1-37] days vs 16.9 [range, 3-37] days; P = .001) and admission to follow-up (6.3 [range, 1-16] days vs 7.8 [range, 1-23] days; P = .039).

By choosing Matomo, you are joining an ever growing movement. You’re standing up for something that respects user-privacy, you’re fighting for a safer web and you believe your personal data should remain in your own hands, no one else’s.

The insulin then crosses the basal lamina of the B cell and a neighboring capillary and the fenestrated endothelium of the capillary to reach the bloodstream. The fenestrations are discussed in detail in Chapter 31.

Earlier this year it began asking Europeans for consent to processing their selfies for facial recognition purposes — a highly controversial technology that regulatory intervention in the region had previously blocked. Yet now, as a consequence of Facebook’s confidence in crafting manipulative consent flows, it’s essentially figured out a way to circumvent EU citizens’ fundamental rights — by socially engineering Europeans to override their own best interests.

CAPTCHAs will be dead in the next 10 years, because computers will be better at solving them than any human.

The truth is that building an innovative organization from top-down is a dynamic process.  It often involves people at all levels of the company. But, the fundamental narrative across the board with innovative organizations is the culture. The company culture has to include employees who feel connected to the organization and want to contribute value.