5,417 Matching Annotations
  1. Feb 2021
    1. Set your models free from the accepts_nested_attributes_for helper. Active Form provides an object-oriented approach to represent your forms by building a form object, rather than relying on Active Record internals for doing this.
    1. There is nothing wrong with accepts_nested_attributes_for. This is what you should use in your typical case. My post describes a non-typical case. ContactListForm is not an ActiveRecord object, it is an object that includes ActiveModel::Model, which does not support accepts_nested_attributes_for.
    1. p. 217:

      We also keep a higher percentage of our assets in cash than most financial advisors would recommend --- something around 20% of the value of our assets outside the value of our house.

      Compare this to my current allotment.

    1. We got this email from Parabo, the print shop app, and smiled. Instead of the very standard “Please confirm subscription” header text, we were greeted with a funny, whimsical hello that’s totally in their brand voice. “We really want you to want us” is a clever way to break up the usual mundane greeting, and, guess what? It totally reaffirmed why we thought we wanted to sign up for their emails in the first place.
    1. From having the DLC only items be both constantly in your face and the kind of things you should really have access to as a base (medium sized building, most of the decorations etc) to the maps layout being seemingly purposefully made to be agravating, everytme I tried to play and like this game I got spit in the face by the devs
    1. Patreon is a good example of why generic community platforms are not the future. You could certainly say that Patreon is already at the center of content, social, and commerce. But of course, Patreon has for years been getting unbundled into A, B, and C type businesses. The reason for Patreon’s erosion is that its product design is totally unsuitable for all three use cases: it’s a bad brand platform, a bad content platform, and a bad social platform. Patreon is a classic case of what Venkatesh Rao calls “Too Big to Nail,” and businesses that try to follow in its stead will face similar challenges.

      An interesting analysis of why Patreon is doomed to failure.

    1. <small><cite class='h-cite via'> <span class='p-author h-card'>InvisibleUp</span> in All Our Selves In One Basket (<time class='dt-published'>02/10/2021 10:46:46</time>)</cite></small>

    1. Alienated by the Town Square There was this article I read, titled Why You Hate Contemporary Architecture, that does a really good job at describing this issue. There was no point in beauty, no point in decoration, as it was useless, distracting from the primary usage of the building, and a needless expense.
    1. Yes, you do face difficult choices (moral) but you don't care about it. All you care are the reputation bars. So... Let's kill this guy, who cares if he is innocent, but this faction needs it or I'm dead. Sounds great on paper but to be honest... you just sit there and do whatever for these reputation bars. If you won't, then you lose
    1. We also find it hard to agree on what good names and bad names look like, which makes it hard to know when renaming improves a name.
    2. Scalability is the problem you want to have, and sooner rather than later, but maintainability is the problem you’re definitely going to have, sooner or later.
    3. ‘Programs are meant to be read by humans and only incidentally for computers to execute.’
    4. In principle, the naming things in code need only be temporary, but names in code stick just like nicknames at school.
    1. Space: Suppose we had infinite memory, then cache all the data; but we don't so we have to decide what to cache that is meaningful to have the cache implemented (is a ??K cache size enough for your use case? Should you add more?) - It's the balance with the resources available.
    2. 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).
    1. Now let me ask you, do you write JS for a single page application differently from a "traditional" web application? I sure hope you do! In a "traditional" application, you can get away with being sloppy because every time the user navigates to a new page, their browser destroys the DOM and the JavaScript context. SPAs, though, require a more thoughtful approach.
    2. where's the code that unloads the table-sorter plugin when the page unloads? There isn't any. There didn't need to be back in the day because the browser handled the cleanup. However, in a single-page application like Turbolinks, the browser doesn't handle it. You, the developer, have to manage initialization and cleanup of your JavaScript behaviors.
    3. When people try to port traditional web apps to Turbolinks, they often run into problems because their JS never cleans up after itself.
    4. All Turbolinks-friendly JavaScript needs to: Initialize itself when a page is displayed Clean up after itself before Turbolinks navigates to a new page.
    5. we plan to migrate to Angular 1, and we'll finish out the decade on React

      Wrong direction: I'd recommend migrate from Angular to React.

    1. when it comes to personal machines, I expect them to just work so I can work.
    2. the most productive environment possible for people that use their computer to create.What is a productive environment?How do you measure productivity in an operating system environment?How do you compare YOUR distribution to other distributions when it comes to productivity?Is the way in which 'people that use their computer to create' (creators) the same across all professions and activities?Does a photographer have the same requirements for a productive environment as a software engineer?Why do you think your distribution will be the best for delivering a productive environment than any other Linux distribution?
    1. And honestly, most people prefer the no hassle, especially after wasting too much time dabbling with distros that are "for advanced users" troubleshooting all kinds of dumbass problems that just worked out of the box in many other distros.
    1. I chose 18.04 because it's the latest LTS version, and I'm not keen on updating my OS every year or so. (I like getting things stable and not having to worry for a while)
    1. Switching to Pop!_OS From Apple If you are coming from Apple’s operating system using Pop!_OS for the first time, we can help make the transition smoother.
    2. Switching to Ubuntu from Apple If you are coming from Apple’s operating system and just using Ubuntu for the first time, we can help make the transition a little smoother.
    1. Tim Ingold's short but beautiful introduction Anthropology: Why It Matters.

      This could be an interesting read.

    1. I hope we see new CSS capabilities arise that allow this sort of effect without the need for trickery.
    2. Since CSS doesn’t (yet) offer a way to style grid cells, areas, or tracks directly, we have to stretch elements over the parts we want to style independently from the elements that contain content.
    1. Although one thing you want to avoid is using frames in such a manner that the content of the site is in the frame and a menu is outside of the frame. Although this may seem convienient, all of your pages become unbookmarkable.
    1. Iframes can have similar issues as frames and inconsiderate use of XMLHttpRequest: They break the one-document-per-URL paradigm, which is essential for the proper functioning of the web (think bookmarks, deep-links, search engines, ...).
    2. The most striking such issue is probably that of deep linking: It's true that iframes suffer from this to a lesser extent than frames, but if you allow your users to navigate between different pages in the iframe, it will be a problem.
    3. never care and try to understand design standards
    1. cultural capital

      Introduced by Pierre Bourdieu in the 1970s, the concept has been utilized across a wide spectrum of contemporary sociological research. Cultural capital refers to ‘knowledge’ or ‘skills’ in the broadest sense. Thus, on the production side, cultural capital consists of knowledge about comportment (e.g., what are considered to be the right kinds of professional dress and attitude) and knowledge associated with educational achievement (e.g., rhetorical ability). On the consumption side, cultural capital consists of capacities for discernment or ‘taste’, e.g., the ability to appreciate fine art or fine wine—here, in other words, cultural capital refers to ‘social status acquired through the ability to make cultural distinctions,’ to the ability to recognize and discriminate between the often-subtle categories and signifiers of a highly articulated cultural code. I'm quoting here from (and also heavily paraphrasing) Scott Lash, ‘Pierre Bourdieu: Cultural Economy and Social Change’, in this reader.

    1. We were especially excited to see Dorsey cite Mike Masnick's excellent Protocols, Not Products paper.

      I don't think I've come across this paper before...

      Looking at the link, it's obvious I read it on December 11, 2019.

    1. Similarly to a cell phone setup, you prepay your email quota. Although they famously used to offer credits that ‘never expired’, new changes mean that credits now expire after 12 months (or, if purchased before May 15th 2019, they’ll expire on May 15th 2020).
  2. Jan 2021
    1. Group Rules from the Admins1NO POSTING LINKS INSIDE OF POST - FOR ANY REASONWe've seen way too many groups become a glorified classified ad & members don't like that. We don't want the quality of our group negatively impacted because of endless links everywhere. NO LINKS2NO POST FROM FAN PAGES / ARTICLES / VIDEO LINKSOur mission is to cultivate the highest quality content inside the group. If we allowed videos, fan page shares, & outside websites, our group would turn into spam fest. Original written content only3NO SELF PROMOTION, RECRUITING, OR DM SPAMMINGMembers love our group because it's SAFE. We are very strict on banning members who blatantly self promote their product or services in the group OR secretly private message members to recruit them.4NO POSTING OR UPLOADING VIDEOS OF ANY KINDTo protect the quality of our group & prevent members from being solicited products & services - we don't allow any videos because we can't monitor what's being said word for word. Written post only.

      Wow, that's strict.

    1. I want to write my own scripts first, but may end up graduating to this.

    1. I'm still pretty proud of the project and I don't want to see it gone, so I want to keep updating it when needed. But on the other hand, the feature set is pretty stable and well working now (AFAIK) so I also don't see the need to pretend to be actively maintaining it.
    2. It's not impossible, but it's not likely I would accept someone I haven't worked with IRL or know on a personal level. That's because I want some form of creative control over the direction and I want to maintain the existing code style. If I know you I'm more likely to know that this will keep working the way I want it to.
    3. Show me good PRs, bug triaging, documentation fixes, whatever and you're a candidate if you ask for it.
    1. The relationship between cumulative CO2 emissions and temperature change is known as the “Transient Climate Response to Cumulative Emissions” (TCRE) and is a robust predictor of CO2-induced warming across a wide range of emissions levels and pathways.

      Ist für mich ein weiterer Topic bei der Darstellung der globalen Erwärmung.\(Insert LaTeX\)

    1. Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.
    1. overflow-wrap: break-word; makes sure the long string will wrap and not bust out of the container. You might as well use word-wrap as well because as the spec says, they are literally just alternate names for each other. Some browsers support one and not the other.
    1. It won't work if $HOME is not under /home. Really. Not even if you softlink. You need a bind mount
    2. Flatpak as a truly cross-distro application solution that works equally well and non-problematic for all
    3. Canonical would do well to make sure they dont complicate things for whatever the next big Linux shift is.
    4. What's wrong here is Canonical trying to position itself as a powerhouse and ascertain control over Linux users.
    5. If upstream code presumes things will work that dont in snap (e.g. accesses /tmp or /etc) the snap maintainer has to rewrite that code and maintain a fork. Pointless work. Packaging for .deb is a no-brainer.
    6. Why did I put the kdb in the snap file system? Because the app is sandboxed, so I had no choice.
    7. +1 For Devuan here, running it on my home and work machines, and on my son's laptop, despite his IT teacher telling him to install a proper operating system like Windows 10....
    8. >Linux needs an app delivery format Yeah, it's incredible that it has managed to survive for so long without one.
    9. It's Snap that drove me to Arch, so it did me a huge favour. Seeing things like GNOME as a snap and other 'core' products wasn't something I was comfortable with. Personally, I prefer flatpaks as a packaging format when compared to snap and appimage. I agree that Linux needs an app delivery format, but snap's current implementation isn't it.
    10. You stick with what you know. It's trouble free because you know how to use it. That's achievable on any of the main OSs, even (gasp!) Windows.
    11. Its not too complicated but it is an annoyance. I want /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, /etc/rc.local and all the standard stuff to work. The heavy lifting is done in the kernel. All they need to do is leave it alone. Its getting harder to make Ubuntu behave like Linux.
    1. 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.
    2. I think this is very important feature to implement. Because for now we need to wrap target components by useless wrapper nodes.
    1. Moving DOM elements around made me anxious and I wanted to preserve natural tab order without resorting to setting tabindex, so I also made a flexbox version that never moves DOM elements around. I think it's the superior solution, at least for the layouts I was going for. https://github.com/wickning1/svelte-components/blob/master/src/FlexCardLayout.svelte
    2. The CardLayout creates a store in context and the Card creates a standardized div container and registers it to the store so that the CardLayout has access to that DOM element. Then in afterUpdate you can move the DOM elements into columns and Svelte will not try to put them back where they go. It's a bit messy but it works.
    1. // read-only, but visible to consumers via bind:start export let start = 0;

      Can't do

      export const start = 0
      

      (because it needs to be mutable/assignable within this local component), so we have to do

      export let start = 0
      

      with a comment saying that it's read-only (by the consumer).

    1. While it is easy to imagine that all iterators could be expressed as arrays, this is not true. Arrays must be allocated in their entirety, but iterators are consumed only as necessary. Because of this, iterators can express sequences of unlimited size, such as the range of integers between 0 and Infinity.
    1. I've reproduced, in a very simple way, what I would like it to do: https://svelte.dev/repl/2b0b7837e3ba44b5aba8d7e774094bb4?version=3.19.1

      This is the same URL as the original example given in issue description.

      I'm guessing what happened is they started with that one, made some changes, and then I think they must have forgot to save their modified REPL (which would have generated a new, unique URL).

    1. https://github.com/sveltejs/svelte/issues/1037#issuecomment-737872461

      Explanation (from https://github.com/sveltejs/svelte/issues/1037#issuecomment-739458005):

      @AlexGalays register is an action created and passed in from the parent node (Wrapper) which allows the child to register with it. Not builtin to svelte.

      That's very clever @PatrickG. Nice one. I was a bit confused when first looking at it to understand what was going on, but I think that will be a handy tool in the toolbox.

      But why do we need this? If we remove all use:register, it still toggles just fine. Seems the only benefit is that this allows cleanup.

    1. Popper for Svelte with actions, no wrapper components or component bindings required! Other Popper libraries for Svelte (including the official @popperjs/svelte library) use a wrapper component that takes the required DOM elements as props. Not only does this require multiple bind:this, you also have to pollute your script tag with multiple DOM references. We can do better with Svelte actions!
    1. It’s fairly common to assume that there is an onHover event handler in React, especially when you consider the naming conventions of the other event handlers, such as onClick, onSubmit, and onDrag.Why wouldn’t there be an onHover event in React?
    1. JSONP is really a simply trick to overcome XMLHttpRequest same domain policy. (As you know one cannot send AJAX (XMLHttpRequest) request to a different domain.) So - instead of using XMLHttpRequest we have to use script HTMLl tags, the ones you usually use to load JS files, in order for JS to get data from another domain. Sounds weird?
    1. “JSONP is JSON with extra code” would be too easy for the real world. No, you gotta have little discrepancies. What’s the fun in programming if everything just works? Turns out JSON is not a subset of JavaScript. If all you do is take a JSON object and wrap it in a function call, one day you will be bitten by strange syntax errors, like I was today.
    1. No doubt privacyis valuable to people who have mischief to hide, but that is not enoughto make it generally worth protecting. However, it is enough to re-mind us that whatever value privacy has, it also has costs. The moreprivacy we have, the more difficult it is to get the information that

      Privacy is valuable to people who have mischief to hide. This is not enough to make it worth protecting, but it tells us that there is also a cost.

    1. Miracles are teaching devices for demonstrating it is as blessed to give as to receive.

      Please do not use this statement to justify a charity of any kind. The author speaks about the level of the Mind. When a musician shares his song with others, it hardly means for him it's lost; the spreading makes it stronger and gives him opportunities he didn't have before. The Course takes this idea and brings it to the level where you will be amazed for sure.

      If you share a physical possession, you do divide its ownership. If you share an idea, however, you do not lessen it. All of it is still yours although all of it has been given away. T-5.1.1

      A major learning goal this course has set is to reverse your view of giving, so you can receive ... God's gifts will never lessen when they are given away. They but increase thereby. W-105.3

      To learn that giving and receiving are the same has special usefulness, because it can be tried so easily and seen as true. W-108.6

      All that I give is given to myself. W-126

  3. view.connect.americanpublicmedia.org view.connect.americanpublicmedia.org
    1. The 2019 eponymous documentary from director Justin Pemberton is our choice for this month’s Econ Extra Credit film series.

      Film: Capital in the Twenty-First Century

      This looks interesting to watch

    1. While the very same software might be in a PPA and a snap, the fact that the snap is shown in Ubuntu Software is the point I’m making. Many people use that to install software. So making software appear there is beneficial for developers - their software is found, and beneficial for users - they discover new software.
    2. Most users frankly don’t care how software is packaged. They don’t understand the difference between deb / rpm / flatpak / snap. They just want a button that installs Spotify so they can listen to their music.
    3. Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.
    4. The best place to let the developers know, and track those bugs is in the bug tracker. There are hundreds of forums online, all over the place in many languages. We can’t be expected to read all of them. Anyone with a launchpad ID (thus, anyone who has an account on this discourse instance) has the capability to file a bug. I’d strongly recommend doing so, for each specific issue. Taking just a few minutes to do that will help tremendously.
    5. When there are imperfections, we rely on users and our active community to tell us how the software is not working correctly, so we can fix it. The way we do that, and have done for 15 years now, is via bug reports. Discussion is great, but detailed bug reports are better for letting developers know what’s wrong.
    6. The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.
    7. « Half solved » because, hey, still it’s proprietary so who knows ? You have to trust the software editor then, it’s just moving the trust cursor.
    8. ( sorry for 2 answers, can’t we edit posts here ? )
    9. What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.
    10. I - we all - totally agree about the benefits of snap for developers. But the loss of comfort and flexibility for end user is eventually a no-go option.
    11. And Unity ditching for something that’s still not on par with it, had already broken a bit my trust in Ubuntu as a stable option at work. Now snap is coming closer and broader…
    12. Users want work be done. Not struggling about how allowing access to removable medias or such a file on another partition… Not breaking their habits or workflows each time a snap replaces a deb.
    1. The trouble with leaving the verb off is that if a user experiencing low or no vision is browsing with the aid of a screen reader, they may not be able to determine what the noun is for. Screen readers can scrape the current page and create lists by content type (headings, links, buttons, etc.) for easer navigation. Static text that is placed in visual proximity to the download links will not come along for the ride if accessed via this method. While it might seem redundant to show the word “download” over and over again, including it can go a long way to providing context for users navigating without visual aids, or who have zoomed the page’s content to the point where the layout may not communicate the visual relationship.
    2. One lesser-appreciated user-behaviour is when a user would like to choose an alternative download location. On a download link, your user can right-click -> “save link as…” and place the download directly into a folder of their choice. Handy if you want something to go directly to removable media, for example. On a download button, there’s no such option.
    3. For larger files, the wait time can be especially problematic. A standard download is an all-or-nothing affair—interruptions can corrupt them and render them useless. Worse, it can waste valuable data on a metered data plan, an unfortunately all-too-relevant concern.
    1. I'd like to spin up a couple of these, both for my personal box (localhost-only) and for the development network.

  4. Dec 2020
    1. Add this to my toolchain (in particular, configure Lighthouse to run in our CI/CD pipeline).

    1. RFC 3463 [25], specifies further structuring of the reply strings, including the use of supplemental and more specific completion codes (see also RFC 5248 [26]).

      To-do: look at the mentioned RFCs.

    1. Or maybe a better standard was in the humanitarian world. “There’s a core ethical principle called the responsibility to protect, which is about organizations having a primary responsibility to protect their own personnel,” said Abramowitz. “What’s very clear is that many teachers are distrustful because they have been in deeply unsafe situations for a very long time.” Teachers are asked to deal with school shootings, violent children, aggressive adults, poverty, online bullying—a host of complex social problems that aren’t part of their job description, she said. “Educators are so abandoned, they no longer trust in their own system to protect them.
    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. I guess it's about "preloading" and not "navigation", if it's the case, then I guess there is still no way to attach to navigation events, and this issue should be kept open.
    2. No JS event is fired, so there currently isn't any clean way to do this that I can see.
    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 would be cumbersome, and would encourage developers to populate stores from inside components, which makes accidental data leakage significantly more likely.
    2. which makes it much harder to accidentally keep logged-in state visible after a client-side logout
    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. We usually only see people launching projects once they're already done. I'm sure there are countless more unfinished and unlaunched side projects that the world will never know about. Don't let your side project become one of them.
    2. 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. People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!
    1. You can afford to make a proper PR to upstream.
    2. The change would be useful to other people as-is.
    3. 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
    4. Yarn only runs the postinstall hook after yarn and yarn add, but not after yarn remove. The postinstall-postinstall package is used to make sure your postinstall hook gets executed even after a yarn remove.
    5. # 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.