1,375 Matching Annotations
  1. May 2021
    1. More importantly, using a plain email would save lots of time and effort. As a goal-driven-lazy person, that’s a good enough reason to start experimenting.
    1. Previous analyses of station observations of snow were confined to regional analyses. Here, we present an Alpine-wide analysis of snow depth from six Alpine countries – Austria, France, Germany, Italy, Slovenia, and Switzerland – including altogether more than 2000 stations of which more than 800 were used for the trend assessment. Using a principal component analysis and k-means clustering, we identified five main modes of variability and five regions which match the climatic forcing zones: north and high Alpine, north-east, north-west, south-east, and south and high Alpine.
    1. Beltran, D. G., Isch, C., Ayers, J. D., Alcock, J., Brinkworth, J. F., Cronk, L., Hurmuz-Sklias, H., Tidball, K. G., Horn, A. V., Todd, P. M., & Aktipis, A. (2021). Mask wearing behavior across routine and leisure activities during COVID-19. PsyArXiv. https://doi.org/10.31234/osf.io/2qya8

  2. Apr 2021
    1. Analyse der Realisierungschancen des Plans der Biden-Administration bis 2030 zu halbieren. Viel Hintergrund-Informationen zu den politischen Bedingungen. Erkennbar werden, das aus einigen Bereichen der Industrie gebremst werden wird. Deutlich ist auch, dass Biden die Klimapolitik mit dem Ziel verbindet und argumentiert, die US-Wirtschaft nach vorne zu bringen und industrielle Arbeitsplätze in den USA zu schaffen. Biden’s Bet on a Climate Transition Carries Big Risks - The New York Times

    1. Drei führenden Klimawissenschaftler *kritisieren die Illusion der "Net Zero-Politiken", die darauf setzen, das 1,5°-Ziel durch die Entfernung von CO2" aus der Atmosphäre zu erreichen. Sie werfen vielen ihrher KollegInnen vor, unrealistischen Konzepten nicht offen entgegenzutreten, um ihren politischen Einfluss nicht zu verlieren. Sie kritisieren auch die bisherigen Integrated Assessment Models des Weltklimarats, die von der Voraussetzung ausgehen würde, die Klimakatastrophe ließe sich mit marktwirtschaftlichen Mitteln beheben und fordern auf, deutlich zu sagen, dass sich eine Erhitzung der Erde auf 3 und mehr Grad nicht durch kleine Schritte, sondern nur durch einen Bruch mit dem bisherigen Wirtschaftssystem erreichen läßt.

      Anstatt uns unseren Zweifeln zu stellen, beschlossen wir Wissenschaftler, immer aufwändigere Fantasiewelten zu konstruieren, in denen wir sicher wären. Der Preis, den wir für unsere Feigheit zahlen mussten: Wir mussten den Mund halten über die immer größer werdende Absurdität der geforderten Kohlendioxid-Entfernung im planetarischen Maßstab.

      Greta Thunberg hat diesen Aufsatz als einen wichtigsten und informativsten Texte zur Klima- und ökologischen Krise bezeichnet.

      Climate scientists: concept of net zero is a dangerous trap. Thread von Greta dazu auf Twitter: https://twitter.com/GretaThunberg/status/1385869663188492290

    1. Über einen Bericht der Swiss Re, der die globale Erhitzung als Problem für das Wachstum ansieht. Danach würde eine Temperatursteigerung um 2,3° bis 2050 in diesem Jahr zu einer Minderung des globalen Wachstums um 23 Trillionen USD führen. Die armen Länder wären davon am stärksten betroffen. Es werden auch Szenarien mit größeren Temperatursteigerungen durchgerechnet. Der Bericht steht in der Nachfolge des Stern-Reports, in dem zum ersten Mal detailliert versucht wurde, die wirtschaftlichen Kosten der Klimakrise zu berechnen. Climate Change Could Cut World Economy by $23 Trillion in 2050 - The New York Times

    1. Wurde der US-Klimagipfel also zum "Gamechanger"? Die Zusage der USA bedeute beinahe eine Verdopplung des vorherigen Ziels, erklärt die Politikwissenschafterin Alina Brad von der Uni Wien. "Dazu gibt es auch ernst zu nehmende Anzeichen, wie das zwei Billionen Dollar schwere Infrastrukturpaket." Ähnlich fasst es Klimaökonom Karl Steininger zusammen: "Biden ist es ernst, seiner Partei auch." Die Rufe nach mehr Klimaschutz könnten global weitere Initiativen anstoßen, sagt der Ökonom, betont aber das Wort "könnten".
    1. cept as

      Angrily, I begin annotating in the thing called "written word" this second attempt at noting the significance of the words "13a" and the end of slavery with this day, 4/22/2021.

      It's 40 years after the "Novus Ordo Seclorum" speech heralding a "new order of the ages" and 60 years after the Kennedy speech about a ruthless monolithic conspiracy; all relating to what apparently is Latin for "Unicorn" and my own interpretation of these words:

      Legatus, Semper Fi, Babylon the Great, Medusa

      Specifically a "fusion of law and land" that actually marks this place and this document as something like a connection between "living" and plain old ink on paper.

      Legislature, Legislation, Legacy of Novus Ordo ... and "at us" Legatus--something like the Monolithic "thing of ten" that also today God noted was "a funny thing to shun" in connection to the word "Phoenecian" which also links another silly bird and "CIA" to something Earthene

      A legatus (anglicised as legate) was a high-ranking Roman military officer in the Roman Army, equivalent to a modern high-ranking general officer. Initially used to delegate power, the term became formalised under Augustus as the officer in command of a legion.

      From the times of the Roman Republic, legates received large shares of the military's rewards at the end of a successful campaign. This made the position a lucrative one, so it could often attract even distinguished consuls or other high-ranking political figures within Roman politics (e.g., the consul Lucius Julius Caesar volunteered late in the Gallic Wars as a legate under his first cousin once removed, Gaius Julius Caesar).

      ... amd I recall a time before C3P0 had a silver leg and gold was a thing of "carbonite steel ethereality"

    1. New research shows that lake "stratification periods" – a seasonal separation of water into layers – will last longer in a warmer climate. These longer periods of stratification could have "far-reaching implications" for lake ecosystems, the paper says, and can drive toxic algal blooms, fish die-offs and increased methane emissions.

      Eine neue Studie ergibt, dass die globale Erhitzung die Ökosysteme von Seen weltweit schädigt. Die Periode, in der sich das Wasser in Schichten teilt, dauert länger. Dramatische Veränderungen mit Schäden für die Biodiversität lassen sich z.B. in den großen amerikanischen Seen beobachten. Kurzbericht: Climate Change Could Cause ‘Irreversible Impacts’ to Lakes - EcoWatch, Details: Climate change could cause ‘irreversible impacts’ to lake ecosystems | Carbon Brief, Studie: Phenological shifts in lake stratification under climate change | Nature Communications

    1. Ein neuer Bericht der @IEA prognostiziert, dass die globalen CO2-Emissionen aus fossilen Brennstoffen im Jahr 2021 wieder ansteigen werden, mit dem zweitgrößten Anstieg in der Geschichte. In diesem Fall hätte 2021 die dritthöchsten Emissionen in der Geschichte, nach 2018 und 2019. Global Energy Review 2021 – Analysis - IEA, Zeke Hausfather auf Twitter

    1. There was a “relentless” intensification of the climate crisis in 2020, according to the UN’s World Meteorological Organization.

      Die Klimakrise hat sich 2020 uneingeschränkt verschlimmert, stellt der Abschlussbericht der World Meteorological Organization fest. Ohne die Kühlwirkung von La Niña wäre 2020 das heisseste Jahr der Geschichte gewesen. So teilt es sich den Spitzenplatz mit 2016 und 2019. Weltweit wurden Rekorde für Extremwetter gebrochen. Die Coronapandemie hat sich nicht auf die Menge der Treibhausgase in der Atmosphäre ausgewirkt, aber ihre Folgen für ärmere Regionen noch verschärft. ‘Relentless’ climate crisis intensified in 2020, says UN report | Climate change | The Guardian, Klimawandel: 2020 laut Weltwetterorganisation eines der drei wärmsten Jahre - DER SPIEGEL, Übersicht zu einzelnen Entwicklungen: 12 reasons why 2020 was a bad year for climate change - The Planet

    1. Yet, it certainly is important to make the proper choices when picking up style. Similarly to fashion, code style reflects our credo as developers, our values and philosophy. In order to make an informed decision, it’s mandatory to understand the issue at stake well. We all have defined class methods many times, but do we really know how do they work?
    1. We are a small development studio and we work on our projects in our spare time, we love what we do and we are working hard on our games to give the best experience possible for our players, but we have to work in other jobs to earn money which decreases working time in the studio.

      Not really needful to explain, but one can relate...

    1. "Weltweit steigt mit dem Klimawandel das Risiko von extremen Regenfällen und Überschwemmungen", fasst Will Steffen von der australischen Nationaluniversität zusammen. Der Professor ist einer der führenden Klimatologen Australiens. "Die globale Durchschnittstemperatur ist bereits um etwa 1,1 Grad Celsius gestiegen. Für jeden Temperaturanstieg von einem Grad kann die Atmosphäre etwa sieben Prozent mehr Wasser aufnehmen", so Steffen
    1. If we accept the idea that the entire surface of the earth is migratory, then why not landscapes in particular? A landscape — as a scene, landschap, ecosystem, and socio-political territory — is a material assembly of moving entities, a dynamic medium which changes in quality and structure through the aggregate movements or actions of the things that constitute it.
    1. The same is true with my time. So I started blocking all 24 hours of my time (mental breaks, yoga workouts, prepping dinner, sleep, everything) into my digital calendar. There is no time unaccounted for. 

      This Is the Time-Management Hack That Helped Me Double My Income

    1. We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules. For these reason, we generally don't start laying out the final rulebook until production art is complete. Writing and laying out a 20 page rule book like this generally takes about 3 months from start to finish, usually requiring a complete rewrite or two, and involves dozens of editors.
  3. Mar 2021
    1. Promoting the idea of a more inclusive calendar that marks the rise of humanity as the year zero, so that we have a better overall view of human progress.

      Uses the idea of HE (human era) instead of BCE, CE, etc.

    1. Sorry you’re surprised. Issues are filed at about a rate of 1 per day against GLib. Merge requests at a rate of about 1 per 2 days. Each issue or merge request takes a minimum of about 30 minutes (across at least 2 people) to analyse, put together a fix, test it, review it, fix it, review it and merge it. I’d estimate the average is closer to 3 hours than 30 minutes. Even at the fastest rate, it would take 3 working months to clear the backlog of ~1000 issues. I get a small proportion of my working time to spend on GLib (not full time).
    2. Age of a ticket is completely irrelevant as anyone can request anything but the number of developers is limited. If you'd like to see something implemented, please consider providing a patch. Thanks!
    3. In the meantime, people do seem to appreciate a developer spending 2 minutes to reply to comments on old issues, just so they’re not ignored and to manage expectations.
    1. Many people think of the waiting-time paradox as a paradox because a typical waiting time at a bus station is longer than half of the average interval of time between buses
    1. On the “lows” side, I’d say the worst thing was the impact of not being present enough for my family. I was working a full-time job and doing faastRuby on nights and weekends. Here I want to give a big shout out to my wife. She supported me through this and didn’t cut my head off in the process.
    1. If you want the issue fixed as fast as possible, then you should try to help the maintainers as much as possible. Make an example app! Even if it takes extra time for you, it will ultimately lead to your issues getting fixed faster.
    2. Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?
  4. Feb 2021
    1. For instance, when faced with a 60% off, 12 hour only coupon that reduces a $1,200 winter coat to $400, you can’t help but rush to the store to buy it, even if it is 95 degrees out. A few things are happening here. For one, the $1200 acts as an anchor price that psychologically forces you to realize you’re getting an enormous deal at the $400 price point. Plus, the promotion limiting the time the offer is available forces you into an impulse.
    1. found that using only the Pascal-provided control structures, the correct solution was given by only 20% of the subjects, while no subject wrote incorrect code for this problem if allowed to write a return from the middle of a loop.
    1. Our mission is to allow people to make money via educational efforts and to dedicate the rest of their time to creating great open source products.

      What does this mean exactly? "Our mission is to allow people to make money via educational efforts"

    1. For mobile phones, technologies like SMS, MMS and data access were historically usually considered value-added services, but in recent years SMS, MMS and data access have more and more become core services, and VAS therefore has begun to exclude those services.
    1. No one has requested it before so it's certainly not something we're planning to add.
    2. To give a little more context, structures like this often come up in my work when dealing with NoSQL datastores, especially ones that rely heavily on JSON, like Firebase, where a records unique ID isn't part of the record itself, just a key that points to it. I think most Ruby/Rails projects tend towards use cases where these sort of datastores aren't appropriate/necessary, so it makes sense that this wouldn't come up as quickly as other structures.
  5. Jan 2021
    1. Trust me, I'm not trying to stress you right now, but I just wanted to do a friendly bump in case you forgot about this. (I know how it is sometimes) If you get this notification and feel "Ugh, I really don't have time" you don't have to comment here and I'm sorry. I'm just sending you a notification in case you forgot. If not, feel free to archive the email and not click/tap on anything.
  6. Dec 2020
    1. The ground-water compo- nent of streamflow was estimated from a streamflow hydrograph for the Homochitto River in Mississippi,

      pengamatan time series seperti ini jarang dilakukan dalam penelitian-penelitian hidrogeologi di indonesia.

    1. The length of the Ark gives him occasion to discussthe membership of the Church (who are the occupants of the different chambers of thetriple-decked Ark) through three divisions of time: the age of nature, the age of law, andthe age of grace, in a concise chronological summary of spiritual history (paras. 11–13).

      spiritual history

  7. Nov 2020
    1. We are the species that has invented itself the most, by creating the exogenetics of language and culture which carry our continual further inventions to each other over time and space to invent and reinvent our futures.

      continued self invention exogenetics of language culture (re)invent the future

    1. I'd say it's better overall because it replaces paths at compile-time. It means there is no runtime dependency or any performance overhead.
    1. Loaders use a mapping configuration to map module names to files at run-time, see RequireJs documentation and SystemJS documentation.
    1. Lead Time for Work Items: The lead time graph shows how much time developers spend working on something before it is released. The graph caught the attention of the product management because, when translated to a business context, the increased lead times mean a longer time to market. The variability in lead times (the shaded, green area in the graph) was also a concern since it indicates low predictability during development or inappropriately scoped work items, often both.

      [[lead time]] - how long developers spend working on something before it's released. What this means to [[product management]] is that it will take longer to get to market.

      If there is [[variability in [[lead time]]]] - it can be a sign of challenges with scoping work, and and unpredictability during development.

    1. When you email me, please include a minimal bash script that demonstrates the problem in the body of the email (not as an attachment). Also very clearly state what the desired output or effect should be, and what error or failure you are getting instead. You are much more likely to get a response if your script isn't some giant monster with obtuse identifiers that I would have to spend all afternoon parsing.
    1. It took us a long time for everyone to get on the same page about the requirements spanning frameworks, tooling and native implementations. Only after pushing in various concrete directions did we get a full understanding of the requirements which this proposal aims to meet.
    1. I think it is indeed important that we get this right but I'd prefer to hold off on implementing such a system until we have grown contributors and until the project is successful. I expect that after the initial open source release and before the end of the year we'll want to move pretty quickly on this project and I recommend revisiting the RFC based model early next year. Does that sound like a good plan?
    2. 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.
    3. 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. 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.
  8. Oct 2020
    1. Win back your calendar and stop wasting time in meetings. Our screen recorder can provide the context and connection of a meeting without the time commitment.
    1. export const validationSchema = {
        field: {
          account: [Validators.required.validator, iban.validator, ibanBlackList],
          name: [Validators.required.validator],
          integerAmount: [
      

      Able to update this schema on the fly, with:

        React.useEffect(() => {
          getDisabledCountryIBANCollection().then(countries => {
            const newValidationSchema = {
              ...validationSchema,
              field: {
                ...validationSchema.field,
                account: [
                  ...validationSchema.field.account,
                  {
                    validator: countryBlackList,
                    customArgs: {
                      countries,
                    },
                  },
                ],
              },
            };
      
            formValidation.updateValidationSchema(newValidationSchema);
          });
        }, []);
      
    1. Doing so also means adding empty import statements to guarantee correct order of evaluation of modules (in ES modules, evaluation order is determined statically by the order of import declarations, whereas in CommonJS – and environments that simulate CommonJS by shipping a module loader, i.e. Browserify and Webpack – evaluation order is determined at runtime by the order in which require statements are encountered).

      Here: dynamic loading (libraries/functions) meaning: at run time

    2. This PR replaces nested require statements in files in vendor/postcss with import declarations, so that they can be properly resolved at build time.
    1. As programmers, we’re kind of inherently built to want the ABSOLUTE BEST HIGHEST FIDELITY FORMATS OF ALL TIME. Like dammit, I need the timestamp down to the micromillinanosecond for every cheeseburger that gets added to my bespoke Watch-The-BK-Throne app. If I do not have this exact knowledge to the millisecond of when I consumed this BBQ Bacon WHOPPER® Sandwich From Burger King® I may die.

      I totally want this as a Post Kind on my website now!

    1. “Yes. My objection is, that your proposal obliges us to wait.”

      It would be rather anti climactic for the mystery to be dependant on waiting for the reclaim of the diamond from the bank. It makes me believe that something else is likely to happen in between that timeframe, perchaps a new fact that reveals a different location of the diamond. At any rate it seems as if this part of the plot (the diamond resting in a bank) may not be what's really going on... Interested to see what is missing here, maybe Franklin will somehow remember something from before that event that renders this fact irrelevant, assuming that Rachel is truthful and did indeed see Franklin steal the diamon.

  9. Sep 2020
    1. But when you’re using Svelte within a larger Rails app, you probably already have a CSS system in place and there’s no reason to change that. You can just use the same CSS classes as you do elsewhere in your app, and everything will be fine.
    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.
    2. Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
    1. This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.
    2. The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.
    1. You'll have to create a new component that brings in the functionality of both. TooltipButton, TooltipLink, Link, and TooltipRoutedLink. We're starting to get a lot of components to handle a bit of added functionality.
    2. For the tooltip example, if you had a whole bunch of tooltips on different elements, it would be annoying to have different event listeners and "should it be shown" variables for each one.
    1. Perhaps at that point we're better off settling on a way to pass components through as parameters? <!-- App.html --> <Outer contents={Inner}/> <!-- Outer.html --> <div> <div>Something</div> <[contents] foo='bar'/> </div>
    2. I would hope for it to come with React-like behavior where I could pass in a string (like div or a) and have it show up as a normal div/a element when the child component used it.
    1. The lack of spread continues to be a big pain for me, adding lots of difficult-to-maintain cruft in my components. Having to maintain a list of all possible attributes that I might ever need to pass through a component is causing me a lot of friction in my most composable components.
    1. Three tests to prove a small piece of behavior. Although it might seem overkill for such a small feature, these tests are quick to write—that is, once you know how to write them
    1. Sometimes answering a single question can be very time consuming (such as setting up a benchmark), but discussions tend to stall out if concerns don't get thoroughly addressed.
    1. For example, you might want to use the browser’s knowledge of the user’s current time zone to group a collection of elements by date.
  10. Aug 2020
    1. Ray, E. L., Wattanachit, N., Niemi, J., Kanji, A. H., House, K., Cramer, E. Y., Bracher, J., Zheng, A., Yamana, T. K., Xiong, X., Woody, S., Wang, Y., Wang, L., Walraven, R. L., Tomar, V., Sherratt, K., Sheldon, D., Reiner, R. C., Prakash, B. A., … Consortium, C.-19 F. H. (2020). Ensemble Forecasts of Coronavirus Disease 2019 (COVID-19) in the U.S. MedRxiv, 2020.08.19.20177493. https://doi.org/10.1101/2020.08.19.20177493