5,648 Matching Annotations
  1. Dec 2020
    1. Is motivated partisan cognition bipartisan?The extent to which each side exhibits motivated partisan (or biased) cognition is a focus of ongoing debate. Some scholars argue for symmetry (SM). For example, a recent meta-analysis demonstrates equivalent levels of motivated partisan cognition across 51 experiments investigating the tenden cy to evaluate otherwise identical in-formation more favorably when it supports versus challenges one’s political beliefs or allegiances (14). In an illu strative experiment, liberals and conservatives viewed a film clip of a political demonstration in which protestors clashed with police. Despite view-ing the identical clip, liberals rated the protesters as more violent when they believed it was an anti-abortion protest (a conservative cause) rather than a gay-rights protest (a liberal cause), whereas conservatives exhibited the opposite pattern (SM). Other scholars argue for asymmetry. For example, some evidence suggests that, relative to Democrats, Republicans have a higher need for order and greater trust in their gut-level intuitions. Such tendencies appear to motivate them to favor explana-tions that are straightforward and intuitive rather than complex and abstract, even when the latter types of explanation might be more accurate (15) (SM). Such findings are representative of the existing evidence, but conclusions remain tentative.

      This is classic material to add to that which i dug up in 2016 about non-attachment to views.

    1. The only solution that I can see is to ensure that each user gets their own set of stores for each server-rendered page. We can achieve this with the context API, and expose the stores like so: <script> import { stores } from '@sapper/app'; const { page, preloading, session } = stores(); </script> Calling stores() outside component initialisation would be an error.

      Good solution.

    1. This is an opportunity to fix a bug: if you're on a page that redirects to a login page if there's no user object, or otherwise preloads data specific to that user, then logging out won't automatically update the page — you could easily end up with a page like HOME ABOUT LOG IN ----------------------------------------------------------------------------------------- Secret, user-specific data that shouldn't be visible alongside a 'log in' button:
    1. No athlete has embodied the soul of a city and the spirit of its people as Richard did in the 1940s and '50s in Montreal. The Rocket's triumphs were the people's triumphs. In a match the previous Sunday, Richard had twice viciously slashed his nemesis, Hal Laycoe of the Boston Bruins, and then assaulted a linesman. Richard was then suspended for the remaining regular season. Richard had led the Canadiens to three Stanley Cups and had scored 50 goals in 50 games, but he had never won a scoring title and was on the brink of his first. The Richard Riot is generally considered the first explosion of French-Canadian nationalism, the beginning of a social and political dynamic that shapes Canada to this day.

    2. This is a letter by Buteux to the father general, dated at Three Rivers, September 21, 1649. The little settlement of Three Rivers is so slightly defended that the French are in daily peril of their lives. Christophe Regnaut was one of the donnés in the Huron mission, although he did not witness this tragedy, he obtained full particulars of it from the Christian Hurons taken captive by the Iroquois, who were present throughout the horrible torments inflicted upon the unfortunate Jesuits. He relates these in detail, and then describes the condition of the martyrs' remains. Abraham Martin is imprisoned on a scandalous charge connected with the poor girl, but his trial is postponed till the arrival of the vessels. A few weeks later the second execution of Justice took place. September 20 - 22, Father Bressani arrived from the Huron country, with two bands of Indians, and the French traders and soldiers come down. Bringing 5,000 livres' weight of beaver skins. Bressani sets out on his return to the Huron mission but a few days later he comes back with his Huron companions, who probably through fear of the Iroquoi refuse to go beyond the river Des Prairies. When the last vessel returns to France it conveys an Iroquois captive. This year's trade amounts to 100,000 livres. A number of Hurons come down to three Rivers and Quebec to spend the winter; they are aided by the Jesuits with food, blankets, and more. Early September a reinforcement arrived consisting of four additional missionaries and a lot of Frenchmen besides. This gave the Fathers new courage and they even strive to extend their labors to more distant tribes.

    1. They say that perfect is the enemy of good, and I'm coming to realise that something like a video course can never be perfect anyway. I can only do my best with the time and energy I have available. I'd rather finish this course and share my experience and insights on using Svelte with the world, than to plan it forever and never launch.
    1. 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.

      This could be both good and bad.

      potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.

      Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.

      Ah, good, I see they touched on some of these points in the sections:

      • Benefits of patching over forking
      • When to fork instead
    2. # fix a bug in one of your dependencies vim node_modules/some-package/brokenFile.js # run patch-package to create a .patch file npx patch-package some-package

      I love how directly this allows you to make the change -- directly on the source file itself -- and then patch-package does the actual work of generating a patch from it. Brilliant.

    1. Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.

      tag?: what scope of provided features / recommended happy path is needed?

    2. It’s worth mentioning that Svelte limits its scope to being only a UI component framework. Like React, it provides the view layer, but it has more batteries included with its component-scoped CSS and extensible stores for state management. Others like Angular and Vue provide a more all-in-one solution with official routers, opinionated state management, CLIs, and more. Sapper is Svelte’s official app framework that adds routing, server-side rendering, code splitting, and some other essential app features, but it has no opinions about state management and beyond. Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.

      tag?: what scope of provided features / recommended happy path is needed?

    3. With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.
    4. Making UIs with Svelte is a pleasure. Svelte’s aesthetics feel like a warm cozy blanket on the stormy web. This impacts everything — features, documentation, syntax, semantics, performance, framework internals, npm install size, the welcoming and helpful community attitude, and its collegial open development and RFCs — it all oozes good taste. Its API is tight, powerful, and good looking — I’d point to actions and stores to support this praise, but really, the whole is what feels so good. The aesthetics of underlying technologies have a way of leaking into the end user experience.
  2. developer.mozilla.org developer.mozilla.org
    1. Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.
    2. Better contribution workflow: We will be using GitHub’s contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
    1. I think the main difference between the two are the way API are served. Some smelte components need you to input big chunk of json as props, while i prefer keep props as primitive types and in the other hand give you different components tags to compose.

    Tags

    Annotators

    1. p. 198:

      Given any five points on a sphere, show that some four of them lie on a hemisphere that includes its boundary.

      I'll admit, I already looked at the hint for this problem, and yes, my initial approach did indeed consist of trying to find the 'worst' configuration.

      I can think of two ways to determine whether or not two points on a sphere lie within the same hemisphere:

      • First off, since any two points on a sphere may be connected by a great circle, they're in the same hemisphere if they're separated by no more than \(\frac{\tau}{2}\) radians along this shortest path.
      • Equivalently, the length of the line segment connecting them must be less than or equal to \(2r\), where \(r\) is the radius of the sphere.

      One other note:

      • It's always possible to divide the sphere in half in such a way that any two points lie within the same hemisphere. (This is a corollary of the first point, above. Note that two antipodal points must necessarily fall on the boundary of such a division.)

      So, I have a picture in my mind of the sphere divided into eight regions of equal area by way of three great circles which intersect one another at right angles. (Think the Equator, the Prime Meridian, and a third great circle drawn through the poles at 90 degrees longitude.) My thinking now tends more toward combinatorics and the pigeonhole principle than geometry proper.

    1. But something about the comforting rigidity of the process, its seductive notation, but perhaps mostly its connotations of intellectual privilege, has drawn a diverse selection of disciplines to the altar of mathematical reasoning. Indeed, the widespread misappropriation of the language of mathematics in the social and biological sciences has to be one of the great tragedies of our time.

      The deliberate misappropriation of the language of mathematics.

  3. Nov 2020
    1. Mold allergy is caused by mold spores, which are microscopic fungi that are present everywhere in the air. In a few cases, indoor mold allergy can get more serious leading to breathing-related problems like bronchitis and asthma. Before anything else, the only way to treat an allergy to mold is by taking preventive measures to avoid exposure to triggers of mold allergy. Whenever you suspect mold allergy symptoms, do consult your doctor or a leading allergist for your condition.

    1. Traditional online funnels — more often than not — require you to have a separate:Content management system (ex. WordPress, Joomla)Web host (ex. SiteGround, Bluehost)Page builder (ex. Elementor, Beaver)Email autoresponder (ex. MailChimp, Aweber, GetResponse)Order formShopping cartWeb analyticsOther marketing tools
    1. Svelte by itself is great, but doing a complete PWA (with service workers, etc) that runs and scales on multiple devices with high quality app-like UI controls quickly gets complex. Flutter just provides much better tooling for that out of the box IMO. You are not molding a website into an app, you are just building an app. If I was building a relatively simple web app that is only meant to run on the web, then I might still prefer Svelte in some cases.
    1. @monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see
    2. This one gets the SEO, so I hope you're successful @raythurnevoid.

      I assume this gets search traffic because people hope/assume that since there's a React "material-ui" that there might already be a "svelte-material-ui" port/adaptation available. So they search for exactly that (like I did). That and being the first to create that something (with that name).

    1. You could decide to trust yourself and your teammates to always remember this special case. You can all freely use short-circuiting, but simply don't allow a short-circuit expression to be on the last line of a script, for anything actually deployed. This may work 100% reliably for you and your team, but I don't believe that is the case for myself and many other developers. Of course, some kind of linter or commit hook might help.
    1. In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
    2. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
    1. How many times have you heard the cliché, for example, read between the lines? It turns out, the key to reading between the lines is actually to write between the lines. Once you start, you'll discover a whole new reading experience, elevated from that of a one-sided lecture to a two-sided conversation.

      reading as a conversation between myself and the text.

    1. web applications embed too much code. This is a reality and it has a big impact on their performances. The time lapse before a possible interaction with the web application you want to access, the famous "time to interactive", is not only related to the network time needed to download the application's content but also to the time spent by the JavaScript engine to parse and interpret the code.