259 Matching Annotations
  1. Last 7 days
  2. Oct 2021
  3. Sep 2021
    1. Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

      Good move. Rather than having 2 different methods, and requiring people to "go out of their way" to "opt in" to using chunks by using the longer-named javascript_packs_with_chunks_tag, they changed it to just use chunks by default, out of the box.

      Now they don't need 2 similar but separate methods that do nearly the same, which makes things simpler and easier to understand (no longer have to stop and ask oneself, which one should I use? what's the difference?).

      You can't get it "wrong" now because there's only one option.

      And by switching that method to use the shorter name, it makes it clearer that that is the usual/common/recommended way to go.

    1. Why can you remove it? The loader will first try to resolve @import as a relative path. If it cannot be resolved, then the loader will try to resolve @import inside node_modules.
  4. Aug 2021
    1. Even considering all these peculiarities, color is one of the simplest cases of nebulosity

      shades of gray

    1. two notes that are five pitches away from each other, one, two, three, four, five

      Out of context, this sounds like an OBOE (off by one error). You typically wouldn’t count the origin: the two notes are four (semitones) away from one another. That becomes quite useful when you think about all of this as sets and, perhaps, start doing some computation with these. In context, it might simplify things for the moment. It’s just a bit strange to keep all of these in mind. The major third (so, the third note in the scale) is “five pitches” away from the root. The perfect fourth would be “six pitches” away. The perfect fifth “eight pitches away”. Major sixth “10 pitches away”. And the major seventh “12 pitches away”. Which means the octave is “13 pitches away”. Could lead to interesting confusion.

  5. Jul 2021
    1. This came in the context of weighing what she stood to gain and lose in leaving a staff job at BuzzFeed. She knew the worth of what editors, fact-checkers, designers, and other colleagues brought to a piece of writing. At the same time, she was tired of working around the “imperatives of social media sharing.” Clarity and concision are not metrics imposed by the Facebook algorithm, of course — but perhaps such concerns lose some of their urgency when readers have already pledged their support.

      Continuing with the idea above about the shift of Sunday morning talk shows and the influence of Hard Copy, is social media exerting a negative influence on mainstream content and conversation as a result of their algorithmic gut reaction pressure? How can we fight this effect?

    2. Matt Taibbi asked his subscribers in April. Since they were “now functionally my editor,” he was seeking their advice on potential reporting projects. One suggestion — that he write about Ibram X. Kendi and Robin DiAngelo — swiftly gave way to a long debate among readers over whether race was biological.

      There's something here that's akin to the idea of bikeshedding? Online communities flock to the low lying ideas upon which they can proffer an opinion and play at the idea of debate. If they really cared, wouldn't they instead delve into the research and topics themselves? Do they really want Taibbi's specific take? Do they want or need his opinion on the topic? What do they really want?

      Compare and cross reference this with the ideas presented by Ibram X. Kendi's article There Is No Debate Over Critical Race Theory.

      Are people looking for the social equivalent of a simple "system one" conversation or are they ready, willing, and able to delve into a "system two" presentation?

      Compare this also with the modern day version of the Sunday morning news (analysis) shows? They would seem to be interested in substantive policy and debate, but they also require a lot of prior context to participate. In essence, most speakers don't actually engage, but spew out talking points instead and rely on gut reactions and fear, uncertainty and doubt to make their presentations. What happened to the actual discourse? Has there been a shift in how these shows work and present since the rise of the Hard Copy sensationalist presentation? Is the competition for eyeballs weakening these analysis shows?

      How might this all relate to low level mansplaining as well? What are men really trying to communicate in demonstrating this behavior? What do they gain in the long run? What is the evolutionary benefit?

      All these topics seem related somehow within the spectrum of communication and what people look for and choose in what and how they consume content.

  6. Jun 2021
    1. "While it takes time to make these changes now, it's a one-time engineering cost that will have lasting impacts, both internally and externally," Sorenson said in an email. "We're in this for the long game, and we know inclusive language is just as much about how we code and what we build as it is about person-to-person interactions."
  7. May 2021
    1. In the earlier example, I used “no-reply@” because this is, unfortunately, a common practice used by many email marketers. As a brand utilizing email, you should never expect a personal experience like email to ever be one-sided.
    1. Nicolas Berrod. (2021, April 9). Population majeure vaccinée avec au moins une dose (une seule dose/deux doses), au 8 avril: -Tous âges: 19,3% (12,6%/6,6%) -moins de 75 ans: 13,3% (10,5%/2,8%) -75 ans ou plus: 62,5% (28,2%/34,2%) Les pourcentages sont arrondis. #Covid19 https://t.co/EUsyr9LSo8 [Tweet]. @nicolasberrod. https://twitter.com/nicolasberrod/status/1380586797542039554

  8. Apr 2021
    1. Of course you must not use plain-text passwords and place them directly into scripts. You even must not use telnet protocol at all. And avoid ftp, too. I needn’t say why you should use ssh, instead, need I? And you also must not plug your fingers into 220 voltage AC-output. Telnet was chosen for examples as less harmless alternative, because it’s getting rare in real life, but it can show all basic functions of expect-like tools, even abilities to send passwords. BUT, you can use “Expect and Co” to do other things, I just show the direction.
  9. Mar 2021
    1. Trying to force this one thing to work for everyone is the worst way to do that.
    2. The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.
    3. As to opinions about the shortcomings of the language itself, or the standard run-times, it’s important to realize that every developer has a different background, different experience, different needs, temperament, values, and a slew of other cultural motivations and concerns — individual opinions will always be largely personal and, to some degree, non-technical in nature.
    1. That said, I wish more people would talk both sides. Yes, every dependency has a cost. BUT the alternatives aren't cost free either. For all the ranting against micropackages, I'm not seeing a good pro/con discussion.
  10. afarkas.github.io afarkas.github.io
    1. Webshim is also more than a polyfill, it has become a UI component and widget library. Webshim enables a developer to also enhance HTML5 capable browsers with more highly customizable, extensible and flexible UI components and widgets.

      And now that it's deprecated (presumably due to no longer needing these polyfills), not only do the polyfills go away (no longer maintained), but also these unrelated "extras" that some of us may have been depending on are now going away with no replacement ...

      If those were in a separate package, then there would have been some chance of the "extras" package being updated to work without the base webshims polyfills.

      In particular, I was using $.webshims.addCustomValidityRule which adds something that you can't do in plain HTML5 (that I can tell), so it isn't a polyfill...

    1. Peñe, kenn du ko able.

      Un peigne, personne ne le prête.

      peñe bi -- (French) comb.

      kenn -- no one.

      du -- to be (negative). ➖

      ko -- it.

      able v. -- to lend.

  11. Feb 2021
    1. For branching out a separate path in an activity, use the Path() macro. It’s a convenient, simple way to declare alternative routes

      Seems like this would be a very common need: once you switch to a custom failure track, you want it to stay on that track until the end!!!

      The problem is that in a Railway, everything automatically has 2 outputs. But we really only need one (which is exactly what Path gives us). And you end up fighting the defaults when there are the automatic 2 outputs, because you have to remember to explicitly/verbosely redirect all of those outputs or they may end up going somewhere you don't want them to go.

      The default behavior of everything going to the next defined step is not helpful for doing that, and in fact is quite frustrating because you don't want unrelated steps to accidentally end up on one of the tasks in your custom failure track.

      And you can't use fail for custom-track steps becase that breaks magnetic_to for some reason.

      I was finding myself very in need of something like this, and was about to write my own DSL, but then I discovered this. I still think it needs a better DSL than this, but at least they provided a way to do this. Much needed.

      For this example, I might write something like this:

      step :decide_type, Output(Activity::Left, :credit_card) => Track(:with_credit_card)
      
      # Create the track, which would automatically create an implicit End with the same id.
      Track(:with_credit_card) do
          step :authorize
          step :charge
      end
      

      I guess that's not much different than theirs. Main improvement is it avoids ugly need to specify end_id/end_task.

      But that wouldn't actually be enough either in this example, because you would actually want to have a failure track there and a path doesn't have one ... so it sounds like Subprocess and a new self-contained ProcessCreditCard Railway would be the best solution for this particular example... Subprocess is the ultimate in flexibility and gives us all the flexibility we need)


      But what if you had a path that you needed to direct to from 2 different tasks' outputs?

      Example: I came up with this, but it takes a lot of effort to keep my custom path/track hidden/"isolated" and prevent other tasks from automatically/implicitly going into those steps:

      class Example::ValidationErrorTrack < Trailblazer::Activity::Railway
        step :validate_model, Output(:failure) => Track(:validation_error)
        step :save,           Output(:failure) => Track(:validation_error)
      
        # Can't use fail here or the magnetic_to won't work and  Track(:validation_error) won't work
        step :log_validation_error, magnetic_to: :validation_error,
          Output(:success) => End(:validation_error), 
          Output(:failure) => End(:validation_error) 
      end
      
      puts Trailblazer::Developer.render o
      Reloading...
      
      #<Start/:default>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:success>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Left} => #<End/:validation_error>
       {Trailblazer::Activity::Right} => #<End/:validation_error>
      #<End/:success>
      
      #<End/:validation_error>
      
      #<End/:failure>
      

      Now attempt to do it with Path... Does the Path() have an ID we can reference? Or maybe we just keep a reference to the object and use it directly in 2 different places?

      class Example::ValidationErrorTrack::VPathHelper1 < Trailblazer::Activity::Railway
         validation_error_path = Path(end_id: "End.validation_error", end_task: End(:validation_error)) do
          step :log_validation_error
        end
        step :validate_model, Output(:failure) => validation_error_path
        step :save,           Output(:failure) => validation_error_path
      end
      
      o=Example::ValidationErrorTrack::VPathHelper1; puts Trailblazer::Developer.render o
      Reloading...
      
      #<Start/:default>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:validation_error>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:success>
      #<End/:success>
      
      #<End/:validation_error>
      
      #<End/:failure>
      

      It's just too bad that:

      • there's not a Railway helper in case you want multiple outputs, though we could probably create one pretty easily using Path as our template
      • we can't "inline" a separate Railway acitivity (Subprocess "nests" it rather than "inlines")
    2. step :direct_debit

      I don't think we would/should really want to make this the "success" (Right) path and :credit_card be the "failure" (Left) track.

      Maybe it's okay to repurpose Left and Right for something other than failure/success ... but only if we can actually change the default semantic of those signals/outputs. Is that possible? Maybe there's a way to override or delete the default outputs?

    3. This connects the failure output to the previous task, which might create an infinity loop and waste your computing time - it is solely here for demonstrational purposes.
    1. Source maps eliminate the need to serve these separate files. Instead, a special source map file can be read by the browser to help it understand how to unpack your assets. It "maps" the current, modified asset to its "source" so you can view the source when debugging. This way you can serve assets in development in the exact same way as in production.
    1. When Sprockets was introduced, one of the opinions that it held strongly, is that assets such as CSS and JS should be bundled together and served in one file.
    2. The alternative was to have multiple scripts or stylesheet links on one page, which would trigger multiple HTTP requests. Multiple requests mean multiple connection handshakes for each link “hey, I want some data”, “okay, I have the data”, “alright I heard that you have the data, give it to me” (SYN, ACK, SYNACK). Even once the connection is created there is a feature of TCP called TCP slow start that will throttle the speed of the data being sent at the beginning of a request to a slower speed than the end of the request. All of this means transferring one large request is faster than transferring the same data split up into several smaller requests.
    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.
  12. Jan 2021
    1. 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.
    2. Show me good PRs, bug triaging, documentation fixes, whatever and you're a candidate if you ask for it.
    1. Untamed freedom and naturality versus human creativity Ingenuity A difficult balance to find, but when looking to the great white north of Canada you see that this is not an impossible blend. Banff Dugout and One Hitter in Toronto Canada

    1. something that the alternative online media has been unable to do is where mainstream media platforms are still unrivalled – being a one-stop repository for different sets of news consumers. MSM digital platforms, despite many flaws, thrive as catch-all baskets for round-the-clock information seekers, ranging from politics to cricket, from fashion to music and important news (which doesn’t only mean the unusual massacres) from a hamlet in Arwal district in Bihar to that from a Delhi suburb.

      This will be impossible for a small digital media startup to achieve.

      I rather see the independent digital news as a gateway to important, contentious, controversial or rather plain and non flashy news. News of the kind ignored by mainstream media due to their perverse incentive structures.

      I don't think the coverage on cricket for example or entertainment from newslaundry would be any drastically different from mainstream media. In that sense it would be wiser not to compete and squander resources on such kind of reporting just to be a one stop shop.

  13. Dec 2020
    1. it focuses on compiling non-standard language extensions: JSX, TypeScript, and Flow. Because of this smaller scope, Sucrase can get away with an architecture that is much more performant but less extensible
  14. Nov 2020
    1. One pane: With one pane outliners, the content is displayed immediately below the category. A printed legal document is an example of a one-pane document. A web site with a table-of-contents "frame" on the left hand side is similar to a two-pane outline. A Usene t news group is similar to a three pane outline. When writing documents, or organizing ideas for a project (such as a speech, or for software design) I much prefer one pane outlines. I find they are more conducive to collapsing ideas, because you can mix text with categories, rather than radically split ting the organizational technique from the content (as the two and three pane outlines do).

      In one pane outliners the text is displayed under its parent.

      This can be more conducive to writing because you're not splitting work on the organization from work on the content. In writing this separation is fuzzy anyway.

  15. Oct 2020
    1. Incurring high-cost changes isn't evolutionary design-it's oscillation caused by poor planning and requirements specification on a high cost-of-change component-it tips the anticipation/adaptation balance too far towards adaptation.
    1. The other reason I am writing it, however, is that I know that many of my fellow exvies have, like me, struggled for years to make an open break with their families because of the pressure to conform that comes from inherently abusive fundamentalist socialization.

      Some of this reminds me of the insularity and abusive practices of the Hasidim in the recent documentary One of Us. I think there are more pockets of people living like this than most people admit or we as a society should allow.

      I also think there's a link to Fukuyama's growth of politics here which is highlighted by Jonah Goldberg's Suicide of the West.

    1. React does not attempt to provide a complete "application library". It is designed specifically for building user interfaces[3] and therefore does not include many of the tools some developers might consider necessary to build an application.
    1. Kevin's Response

      How To Write This Poem

      begin here …with TIME

      where words

      are layered with text

      where the pen

      etches into screen …

      then go here … https://www.vialogues.com/vialogues/play/61205

      ... only to leap from one place to another, where my mind goes I hardly every know, only that it ventures forward ...

      https://paper.dropbox.com/doc/How-to-Read-a-Poem-by-me--A9AH3OSbHZqKqxia0PQOSa1~Ag-pHyO4XNCl1aIq4KoX22Be

      … heard by hearts, ​​and scattered stars, ​​where I see the sky fall, ​​you find the debris …. ​​https://nowcomment.com/documents/234044

      Your thoughts?

    2. Step One: 

      Use Hypothes.is to annotate the poem. I have seeded the poem with questions and comments that you can reply to.

  16. Sep 2020
    1. I'm certainly not claiming that we should use clever tricks to scrunch our code into the most compact form possible at the expense of readability. Nor am I claiming that reducing lines of code is necessarily a worthwhile goal, since it encourages turning readable code like this...
    1. When you're using urql to send one-off queries or mutations
    2. This may be useful when we don't plan on cancelling queries or we don't care about future updates to this data and are just looking to query a result once.
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
    1. They might even hate each other; the creature who already lived loathed his own deformity, and might he not conceive a greater abhorrence for it when it came before his eyes in the female form? She also might turn with disgust from him to the superior beauty of man; she might quit him, and he be again alone, exasperated by the fresh provocation of being deserted by one of his own species.

      A lot of misogyny is radiating from these lines. Victor is implying that his female creation might be so ugly that even his male creation will be offended by her existence one he sees her. But on the other hand, what if his creation isn't her type and just abandon's him? It's interesting to see how much thought Victor puts in when it comes to making a female creation...I thought he was trying to create a new species?

    1. If your reaction to the video was 'fine, but if we use TypeScript and write plugins for each editor then we can get all the autocomplete and syntax highlighting stuff' — in other words, if you believe that in order to achieve parity with CSS it makes sense to build, document, promote and maintain a fleet of ancillary projects — then, well, you and I may never see eye to eye!
    2. And you don't have to find solutions to the additional problems that CSS-in-JS introduces.
    1. With Svelte, components and files have a one-to-one relationship. Every file is a component, and files can't have more than one component. This is generally a "best practice" when using most component frameworks.
  17. Aug 2020
    1. Here's what 20 seconds of googling turned up: University of Rochester Grammar Style Guide oh hey look, a stackoverflow thread The truth about grammar: bailout versus bail out and there are so many more...