it confirms something found in the Buddhist tradition uh which is this notion of innate basic goodness that all human beings are born with Buddha nature we all have the seeds of kindness within us and scientific research strongly confirms that this is true

we're really invoking a call for philanthropy to be in the liberation of capital in a way that can support transition pathways. What we refer to as transition pathways is other ways of being and knowing that are in co-creative relationship with life itself.

e

The seeming luxury of having multiple words to choose from is not sufficient to offset the lingering fear that no matter which word you pick it will be the wrong one, causing people to silently laugh at you and judge both you and your grammar school teachers

For years developers have followed the same arcane dozen steps to create a long-lived daemon process on Unix-based systems. These steps were state of the art in 2000 but they are no longer best practice today.

Modern parallel languages have much easier to use execution models. The thread model was one of the original parallel execution models, which may account for why it has persisted despite being difficult to use.

there is one thing that I want to to do on top of proving you know or disproving fact falsifying or not this theory is to finding ways in which people that are ready can have an extraordinary experience of Consciousness like did not through drugs but through methods you know way to breathe or different ways of special meditations what have you they are sufficiently welld developed that they can help the process of people experiencing themselves their Unity with one

I want to figure out find out help find out ways in which we can have things where maybe at the most you need to dedicate a week of your life you know because you need to be in a special environment in order to have the the sort of the the conditions in which this can happen and can have those experiences and if say 30% of the people that claim to be ready actually have one of those experien that would be a marvelous objective to reach so that's what I'm thinking right now

I'd agree that much of the time 'not prefer' is a perfectly adequate way of conveying the same sense as 'disprefer' (just as 'not agree' will for most purposes convey the same sense as 'disagree', and 'not like' the same sense as 'dislike'). However, they aren't strictly equivalent; I might neither prefer nor disprefer Coke to Pepsi, but rather be neutral between them. Possibly the purpose for which 'disprefer' is most useful is cancelling implications – 'I don't prefer it – though I don't disprefer it either'.

How can I wait for container X before starting Y? This is a common problem and in earlier versions of docker-compose requires the use of additional tools and scripts such as wait-for-it and dockerize. Using the healthcheck parameter the use of these additional tools and scripts is often no longer necessary.

Bind mounting your host's daemon socket is safer, more flexible, and just as feature-complete as starting a dind container.

The best-known, most recent version of the story is the 1995 WaltDisney animated film. Strikingly beautiful, unnervingly buxom, and morelike a pop culture diva than a member of the Tsenacommacah tribe,Disney’s Pocahontas fabulously communes with nature, befriending araccoon, talking to a tree;

The input format of the xargs command doesn't match what any other command produces. Yes, it's bizarre. With -I, xargs ignores indentation, which is why the file names with initial spaces are mangled. Do not use xargs except with the -0 option or when you know your input doesn't contain characters that would confuse it.

Prepare to transition away from Google Sync Google Sync doesn’t support OAuth authentication, 2-factor authentication, or security keys, which leaves your organization’s data less secure.

Autoloading in Rails was based on const_missing up to Rails 5. That callback lacks fundamental information like the nesting or the resolution algorithm being used. Because of that, Rails autoloading was not able to match Ruby's semantics, and that introduced a series of issues. Zeitwerk is based on a different technique and fixed Rails autoloading starting with Rails 6.

ActiveRecord::Base.normalizes declares an attribute normalization. The normalization is applied when the attribute is assigned or updated, and the normalized value will be persisted to the database. The normalization is also applied to the corresponding keyword argument of query methods, allowing records to be queried using unnormalized values.

I agree with this statement so much. We should absolutely be failing hard rather than forcing people to debug thread safety issues at runtime. I can't think of anything more infuriating than debugging an issue that happens "sometimes".

The problem is that in the case where an app is multi-threaded, and we don't switch off autoload, the case would be that it probably won't blow up, but random stuff will mysteriously sometimes fail in weird ways. So ask yourself this, what would you rather want, option 1) where you can get an exception at runtime, or option 2) where you get random, unpredictable, weird, hard to explain, difficult to debug bugs at runtime. Personally, I'm going to choose option 1. The downside of thread-safety issues is so much worse than the downside of the possibility of an exception. The way you're handling it makes it sound as though thread-safety is not important, as though Rails is still optimizing for the single-threaded case. That seems like a huge step back.

I think we have a responsibility not only to ourselves, but also to each other, to our community, not to use Ruby only in the ways that are either implicitly or explicitly promoted to us, but to explore the fringes, and wrestle with new and experimental features and techniques, so that as many different perspectives as possible inform on the question of “is this good or not”.

If you’ll forgive the pun, there are no constants in programming – the opinions that Rails enshrines, even for great benefit, will change, and even the principles of O-O design are only principles, not immutable laws that should be blindly followed for the rest of time. There will be other ways of doing things. Change is inevitable.

Despite attempts such as the HistoryWorkshop movement in Great Britain, Scandinavia, and Germany to break out ofthe narrow confines of the historical discipline and to encourage the writing ofhistories of and by common people, new fields of history, such as women’s andgender studies, are centered mostly at universities and follow established careerlines.

As an aside, I think I now prefer this technique to Python for at least one reason: passing arguments to the decorator method does not make the technique any more complex. Contrast this with Python: <artima.com/weblogs/viewpost.jsp?thread=240845>

When you call 'foo' in Ruby, what you're actually doing is sending a message to its owner: "please call your method 'foo'". You just can't get a direct hold on functions in Ruby in the way you can in Python; they're slippery and elusive. You can only see them as though shadows on a cave wall; you can only reference them through strings/symbols that happen to be their name. Try and think of every method call 'object.foo(args)' you do in Ruby as the equivalent of this in Python: 'object.getattribute('foo')(args)'.

def document(f): def wrap(x): print "I am going to square", x f(x) return wrap @document def square(x): print math.pow(x, 2) square(5)

If it interests you, GPC lists phrases like dysgu ar gof. This page then gives the example, "Yn yr hen ddyddiau byddai pobl yn dysgu cerddi ar gof" - like saying "to learn by heart" in English.

paranoia has some surprising behaviour (like overriding ActiveRecord's delete and destroy)

I've worked with and have helped maintain paranoia for a while. I'm convinced it does the wrong thing for most cases. Paranoia and acts_as_paranoid both attempt to emulate deletes by setting a column and adding a default scope on the model. This requires some ActiveRecord hackery, and leads to some surprising and awkward behaviour.

the important thing to point out is that when we think of the self this way the self isn't my body or my mind i don't take my body to be myself and 00:17:39 we're going to see that in a moment but i think of the self the target of this analysis the snake in the wall as the thing that has a body the thing that has a mind and of course if we were 00:17:50 operating in india and taking a doctrine of reincarnation or rebirth for granted we would think of it as the thing that in different lives appropriates different bodies and minds um and 00:18:02 but remains the same through those lives but if we're not in a kind of reincarnation and rebirth kind of mood um then we might think that it's just the thing that endures through our entire life while everything else 00:18:15 changes that is um the thing that was me when i was an itty-bitty baby when i was a young handsome guy when now that i'm an old guy um that it's there's something continuous there and we think of that as 00:18:28 the self

In anthropology, Verstehen has come to mean a systematic interpretive process in which an outside observer of a culture attempts to relate to it and understand others.

You can access Events through a few interfaces: Webhooks (we POST data to your URL). The Events API (you GET data through the API). The Logs tab of the Control Panel (GUI).

Yes, it was right, but nowadays Dockerfiles are not specific to Docker. Dockerfiles also work with Buildah & Podman (and there might be other ones in the future) and they have generalized the naming: “Containerfile.”

I don’t know what that knowing was a knowing about.

This effort, which Americans have supported almostfrom the beginning of the national existence and which is oneof the cornerstones of our democratic way of life, has hadremarkable results.

'Pretty Peggy O' was collected by Cecil Sharp from Mrs Combs, Knott County Kentucky in 1908.

an equivalent of R's signif function in Ruby.

we often have too narrow an appreciation of   knowing focusing too much on one or two kinds  of knowing but to live well in a complex world   we need to effectively engage with four kinds  of knowing and perfectly they all begin with a P

Whig history (or Whig historiography), often appearing as whig history, is an approach to historiography that presents history as a journey from an oppressive and benighted past to a "glorious present".[1] The present described is generally one with modern forms of liberal democracy and constitutional monarchy: it was originally a satirical term for the patriotic grand narratives praising Britain's adoption of constitutional monarchy and the historical development of the Westminster system.[2] The term has also been applied widely in historical disciplines outside of British history (e.g. in the history of science) to describe "any subjection of history to what is essentially a teleological view of the historical process".[3] When the term is used in contexts other than British history, "whig history" (lowercase) is preferred.[3]

In studies comparing European American children withMayan children from Guatemala, psychologists Maricela Correa-Chávez andBarbara Rogoff asked children from each culture to wait while an adultperformed a demonstration—folding an origami shape—for another childnearby. The Mayan youth paid far more sustained attention to the demonstration—and therefore learned more—than the American kids, who were oftendistracted or inattentive. Correa-Chávez and Rogoff note that in Mayan homes,children are encouraged to carefully observe older family members so that theycan learn how to carry out the tasks of the household, even at very young ages.

All known use cases of require_dependency have been eliminated with Zeitwerk. You should grep the project and delete them.

Rails 7.0 will aim to give you a default setup based on import maps, and leave the Webpacker approach as an optional alternative.

The reason for the new name is that the "dist-upgrade" name was itself extremely confusing for many users: while it was named that because it was something you needed when upgrading between distribution releases, it sounded too much as though it was only for use in that circumstance, whereas in fact it's much more broadly applicable.

In the Warlpiri Aboriginal language of Central Australia, you do notdescribe positions of things with yourself as the focal reference point.Rather, your position is defined within the world around you. InWarlpiri, my computer is south of me, my cat is sleeping west of meand the door is east of me. It requires you to always know thecardinal directions (north, south, east and west), no matter yourorientation. Any one person is not the centre of the world, they arepart of it.

The First Astronomers challenges commonly held views thatIndigenous ways of knowing do not contain science.

These ways of knowinghave inherent value and are leading Western scientists to betterunderstand celestial phenomena and the history and heritage thisconstitutes for all people.

Dispatch a custom event. This differs from Svelte's component event system, because these events require a DOM element as a target, can bubble (and do by default), and are cancelable with event.preventDefault(). All SMUI events are dispatched with this instead of Svelte's createEventDispatcher.

If booksellers like to blame publishers for books not being available, publishers like to blame printers for being backed up. Who do printers blame? The paper mill, of course.

Instead of render props, we use Svelte's slot props: // React version <Listbox.Button> {({open, disabled} => /* Something using open and disabled */)} </Listbox.Button> <!--- Svelte version ---> <ListboxButton let:open let:disabled> <!--- Something using open and disabled ---> </ListboxButton>

Object.hasOwn() is recommended over hasOwnProperty(), in browsers where it is supported.

Saying that web devs used to be fine with relative imports is like saying that human beings used to be fine living without refrigerators. Sure we did. But was it better than it is now? No. No, it wasn't.

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.

Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.

This is no different from other popular libraries or frameworks making huge architectural changes (think React 16.8 with hooks or Python 3). The longer you wait to make the switch, the more painful it will be for your project when you finally do. And in the meantime, you’ll be missing out on valuable improvements to a fundamental part of the workflow of every single project you work on.

Node Sass does not yet support your current environment indicates that the version of node-sass you are trying to run is not compatible with the version of node installed.

target="_blank" which opens the anchor in a new window(which has been redirected to tabs by browser settings usually)

This attribute is considered a legacy attribute and redefined as allow="fullscreen".

This will obviate the need for a helper function of any kind.

However instead of using array.length for latter items; e.g. array[array.length-1] for the last item, you can call array.at(-1)

you can use the new delegation syntax (...) that is introduced in Ruby 2.7. def foo(...) target(...) end

Different ways to prepend a line: (echo 'line to prepend';cat file)|sponge file sed -i '1iline to prepend' file # GNU sed -i '' $'1i\\\nline to prepend\n' file # BSD printf %s\\n 0a 'line to prepend' . w|ed -s file perl -pi -e 'print"line to prepend\n"if$.==1' file

The first argument to shared_context (the shared group name) is superfluous. It feels a bit like "what's this argument for again?" (Note that you could still use it with include_context to include the group manually, but it's a bit odd to mix-and-match the approaches).

Once a variable is specified with the use method, access it with EnvSetting.my_var Or you can still use the Hash syntax if you prefer it: EnvSetting["MY_VAR"]

GitLab is transitioning from controller specs to request specs.

If you don't need to support IE9 or lower, you can use flexbox freely, and don't need to use floated layouts.

get: function(target, prop, receiver) { return "world"; }

CommonJS has served us well for many years, but ESM comes with many benefits, like language-level syntax, browser support, defaults to strict mode, async loading, top-level await, improved static analysis & tree-shaking, and more.

Lumberjack 1.0 had a concept of a unit of work id that could be used to tie log messages together. This has been replaced by tags. There is still an implementation of Lumberjack.unit_of_work, but it is just a wrapper on the tag implementation.

Students As Knowledge Creators

What you want is not to detect if stdin is a pipe, but if stdin/stdout is a terminal.

stdin can be a pipe or redirected from a file. Better to check if it is interactive than to check if it is not.

What is the equivalent of unbuffer program on Windows?

unbuffer works with piping to less. That may be an easier syntax than what you've got.

Factory FunNER is the sequel and a very solid improvement to Factory Fun. It uses hexes instead of squares to allow more creative building, and some subtle improvements to scoring, length, and machine placement rules really improve things.

For path names with newlines it is better to quote each pathname.

But we can use a two characters delimiter: / (space slash) That pair of characters could only exist at the beginning of a new (absolute) path:

Now that we’ve gotten newer layout features — again, like grid and flexbox — floats, too, have sort of fallen by the wayside, perhaps either because there are better ways to accomplish what they do

My preference here is biased by the fact that I spend everyday at work building web components, so Svelte's approach feels very familiar to slots in web components.

The precise semantic interpretation of an atomic formula and an atomic sentence will vary from theory to theory.

Most “legacy” operations don’t have this output, yet. However, the Model() macro now supports this terminus.

One thing that would be useful to this debate an analysis of a language ecosystem where there are only "macropackages" and see if the same function shows up over and over again across packages.

D3 now passes events directly to listeners, replacing the d3.event global and bringing D3 inline with vanilla JavaScript and most other frameworks.

That’s it. If you have a previous “precompile” array, in your app config, it will continue to work. For continuity sake I recommend moving over those declarations to your manifest.js file so that it will be consistent.

Instead of having this confusing maze of lambdas, regexes, and strings, we could, in theory, introduce a single entry point of configuration for Sprockets to use, and in that file declare all assets we wanted to compile. Well, that’s exactly what the manifest.js file is.

Each of the programming language generations aims to provide a higher level of abstraction of the internal computer hardware details, making the language more programmer-friendly, powerful, and versatile.

You’re allowed to blame us for a terrible developer experience in Trailblazer 2.0. It’s been quite painful to find out which step caused an exception. However, don’t look back in anger! We’ve spent a lot of time on working out a beautiful way for both tracing and debugging Trailblazer activities in 2.1.

The activity gem is an extraction from Trailblazer 2.0, where we only had operations. Operations expose a linear flow which goes into one direction, only. While this was a massive improvement over messily nested code, we soon decided it’s cool being able to model non-linear flows. This is why activities are the major concept since Trailblazer 2.1.

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

Yes, Trailblazer is adding new abstractions and concepts and they are different to the 90s-Ruby, but now, at the latest, it becomes obvious how this improves the developing process. We’re no longer talking in two-dimensional method stack traces or byebug hoops, the language and conception is changing to the actual higher level code flow, to activities sitting in activities structured into smaller step units.

We removed the trailblazer-loader gem just like Apple removed the headphone jack from the iPhone 6. This brings you faster startup and consistency with Rails autoloading.

{a: 1, b: 2, c: 3, d: 4} => {a:, b:, **rest} # a == 1, b == 2, rest == {:c=>3, :d=>4}

{a, b, ...rest} = {a: 1, b: 2, c: 3, d: 4}

ActiveInteraction plays nicely with Rails. You can use interactions to handle your business logic instead of models or controllers.

Since we're using an interaction, we don't need strong parameters. The interaction will ignore any inputs that weren't defined by filters. So you can forget about params.require and params.permit because interactions handle that for you.

No one has requested it before so it's certainly not something we're planning to add.

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.

Examples of different ways of defining forms

As of today, you can Wishlist OpenTTD on SteamE. Historically, OpenTTD always had a single home from where we distributed the game. We used to be hosted on SourceForge (you know you are old, if you remember that being a thing :D), and slowly moved towards our own self-created distribution methods. These days, we mostly distribute our game via our website. But times are changing, and so is our hair. Over the last few months, we have silently been working to become a bit more visible in the world. Don’t worry, not for reasons you might think: OpenTTD has as many active users as it had in 2007. But more because we no longer think it is the right approach to only distribute via our own website. This became painfully apparent when we noticed other people post OpenTTD on some stores. They are not always updated with new releases, sometimes even slacking behind a few years. And maybe more important to us: we can not guarantee that the uploaded version is unmodified and is the version as we intended. So, instead of fighting it, why not turn around and join them! Why not release our own, verified, builds on those stores! And this is exactly what we have been working on lately. And when I say “we”, a bit ironic to me, I mean the two developers that are around longest (myself and orudge) ;) A while back orudge added OpenTTD to the Microsoft Store. And today, I am happy to announce we will be on SteamE too! Well, we are on Steam, but we haven’t released anything there yet (sorry that I got your hopes up, just to squash them right after :( ). This is partially because of how Steam works, but also because we know we can bring a better experience for Steam with our upcoming release. That brings me to the most exciting news: if everything goes as planned, we will release OpenTTD 1.11 on Steam on the first of April, 2021! And that is not even an April fools’ joke! You can already Wishlist OpenTTD today .. and till we release on Steam, you can find our game via our website ;)

As of today, you can Wishlist OpenTTD on SteamE. Historically, OpenTTD always had a single home from where we distributed the game. We used to be hosted on SourceForge (you know you are old, if you remember that being a thing :D), and slowly moved towards our own self-created distribution methods. These days, we mostly distribute our game via our website. But times are changing, and so is our hair. Over the last few months, we have silently been working to become a bit more visible in the world. Don’t worry, not for reasons you might think: OpenTTD has as many active users as it had in 2007. But more because we no longer think it is the right approach to only distribute via our own website.

Well, I'm glad they did, because Turbolinks is a much better piece of software than jquery-pjax ever was. It's actively maintained and doesn't require jQuery at all! So we're one step closer to our dream of ditching $.

Flexbox and grid play well together, and are a huge step forward from the float & table hacks they replace.

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.

Depending on what other component libraries you’ve used, you may be used to handling events by passing callback functions to component properties, or using a special event syntax – Svelte supports both, though one is usually more appropriate than the other depending on your situation. This post explains both ways.

Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.

The Web Storage API provides mechanisms by which browsers can store key/value pairs, in a much more intuitive fashion than using cookies.

delete myObject.regex; // or, delete myObject['regex']; // or, var prop = "regex"; delete myObject[prop];

For future reference, webpack 2 removed everything but modules as a way to resolve paths. This means root will not work.