That’s paid for by the state from a $40 million fund approved by the legislature.

Ramalope says they also don’t go far enough. “I think the weakness of JETPs is that they’re not encouraging 1.5 [degrees] Celsius,”

Just Energy Transition Partnerships, or JETPs, an attempt to catalyze global finance for emerging economies looking to shift energy reliance away from fossil fuels in a way that doesn’t leave certain people and communities behind.

this is now quantifying this this safe space but for the first time also doing it for justice so measuring the maximum allowed 00:15:33 of significant harm to people and the key take home here is the following in the outer ring here the red and green you see the safe boundary definitions 00:15:45 the blue lines are the assessment of justice so not surprisingly if we care about people the safe bound is about the stability of the planet but if we care about avoiding significant harm to hundreds of millions of people across 00:15:58 the world the climate boundary shrinks from 1.5 down to one degree

If it's dangerous, note it in the class/method Javadocs, don't just blindly slam the door shut.

A workers' plan to shut down oilfields

Just because the code is described as part of the WebDAV spec doesn't mean it's WebDAV-specific! Status codes are supposed to be generic.

Within the Earth Commission, we aim to propose ‘safe and just Earth system boundaries’ (ESBs) that go beyond planetary boundaries as they also include a justice perspective and suggest transformations to achieve them3.

The above proposals for just ends need to be subject to wide discussion to further refine our proposals and better meet principles of procedural justice and to analyse the transformations that will achieve this. Just means include ensuring that different knowledge systems are represented in assessments and collective action that challenges dominant sociocultural norms and assumptions about misrecognized groups.

Since minimum access levels for the poor cannot be met within the ESBs without substantial reallocation of resources, we propose minimum access levels for all people. These levels provide the floor or foundation of a corridor, while the ESBs constitute the ceiling (Fig. 6). If resources, responsibilities and risks are allocated in a just manner (Fig. 1), we consider this a ‘safe and just corridor’.

The black line in Fig. 5 shows that redistribution is not enough; if everyone’s emissions are equalized at escape from poverty levels, then we would still overshoot the climate boundaries

Preserving ecosystem area is sometimes critiqued as ‘fortress conservation’ by environmental justice scholars, limiting access for poor or Indigenous people68. An ecosystem area boundary therefore requires careful consideration and involvement of the local communities, for example by not demanding that intact areas preclude human inhabitation and sustainable use and/or recognizing the role of Indigenous peoples and local communities in already protecting these areas.

Safe and just ESBs aim to stabilize the Earth system, protect species and ecosystems and avoid tipping points, as well as minimize ‘significant harm’ to people while ensuring access to resources for a dignified life and escape from poverty. If justice is not considered, the biophysical limits may not be adequate to protect current generations from significant harm. However, strict biophysical limits, such as reducing emissions or setting aside land for nature, can, for example, reduce access to food and land for vulnerable people, and should be complemented by fair sharing and management of the remaining ecological space on Earth4.

joint knowledge to identify safe and just ESBs

we have committed to spend 6.2 billion dollars we've made that public to give ourselves real Zero by 2030.

there are amazing people worldwide that are working to protect the local to Global Commons the next step is to involve businesses 00:11:44 countries cities and people worldwide to accept Earth system boundaries and the just Transformations we need to live within these boundaries

can we quantify safe and just Earth 00:04:20 system boundaries or an earth system corridor in 2019 the Global Commons Alliance created the Earth commission to answer this question

we need in this Century a safe and just Corridor for all people to exit the danger zone but also to ensure that all people have access to basic needs rights 00:04:07 uh rights to a water food energy and infrastructure

we're taking colossal risks with the future of civilization on Earth We're degrading life support system that we all depend on we're actually pushing 00:00:57 the entire Earth system to a point of destabilization pushing Earth outside of the state that has support civilization since we left the last ice age 10 000 years ago this requires a transformation to safe 00:01:11 and just Earth system boundaries for the whole world economy

DeWine said he has talked directly with the director and several members of the six-member Ohio Casino Control Commission, to which the legislature gave the job of regulating the fledgling industry.

2030 (UNGA, 2015) provides a global consensus on key justice principles of access and a starting point for an analysis of a safe and just corridor that aims to ensure that “no one will be left behind.

By identifying safe and just target ranges, the question arises: How can we achieve these targets and live within the corridor? Transforming toward a “just” world may be a pre-condition for being able to achieve a “safe” world. Leverage points to achieve such transformations are essential for governing our commons.

We propose that the stricter of the safe and just target ranges for each variable should define the safe and just corridor (Figure 2). Furthermore, we propose to identify a spread of safe and just targets corresponding to different physical risk tolerances and different understandings of environmental justice.

Second, a key question is how biophysically “safe” targets can be achieved while also meeting goals for human well-being and justice. For example, meeting the social goals of Agenda 2030 without widespread transformations may lead to crossing safe targets for the biophysical state of the Earth system (Sachs et al., 2019). Achieving biophysical targets, such as 1.5°C for climate or increasing ecosystem protection, can undermine well-being, if, for example, bioenergy competes with food production, or protected areas undermine local livelihoods (Hasegawa et al., 2020).

First, an “unsafe” world is likely to increase inequality, so “safe” would seem a necessary pre-condition for “just”—but not always a sufficient one. A “safe” target from a biophysical perspective may not be adequate to prevent large-scale risks to humans in specific contexts. For example, there are large risks for many human populations even with a 1.5°C climate target (Hoegh-Guldberg et al., 2018).

Identifying safe ranges for these systems in isolation, for example as the planetary boundary framework has done (Rockström et al., 2009; Steffen, Richardson, et al., 2015), will not be enough to describe a safe corridor.

An integrated framework is needed that aligns safe and just Earth system variables while also accounting for sub-global scales and interactions between Earth system processes.

our goal of synthesizing a range of safe and just conditions rather than prescribing any specific solution.

An integrated people and planet perspective is required to guide human development and use of the global commons We outline an approach to defining a safe and just corridor for a stable and resilient planet supporting human development A conceptual framework for linking safe and just Earth system targets is proposed

safe as primarily referring to a stable Earth system and just targets as being associated with meeting human needs and reducing exposure to risks.

Keeping the Earth system in a stable and resilient state, to safeguard Earth's life support systems while ensuring that Earth's benefits, risks, and related responsibilities are equitably shared, constitutes the grand challenge for human development in the Anthropocene. Here, we describe a framework that the recently formed Earth Commission will use to define and quantify target ranges for a “safe and just corridor” that meets these goals.

the belief that citizens should have the right to come together to decide what’s best for their community

the container ship was simply becoming so large so unwieldy that much of the infrastructure around them is struggling to cope a lot of the decisions to build Supply chains were really based on

The problem is that the caller may write yield instead of block.call. The code I have given is possible caller's code. Extended method definition in my library can be simplified to my code above. Client provides block passed to define_method (body of a method), so he/she can write there anything. Especially yield. I can write in documentation that yield simply does not work, but I am trying to avoid that, and make my library 100% compatible with Ruby (alow to use any language syntax, not only a subset).

Just because a movie is what people call "cliche", doesn't mean its inherently bad.

Learned right, which means understanding, which meansconnecting in a meaningful way to previous knowledge, informationalmost cannot be forgotten anymore and will be reliably retrieved iftriggered by the right cues.

Everything else in this issue is just figuring out how to make that happen, which turns out to be rather involved.

Just because you can create a plugin for any tool and manage its versions with asdf, does not mean that is the best course of action for that specific tool.

I'm building a Rails API with a separate web frontend app as "just another API client" (various smartphone apps to follow as well). In the previous "monolithic" version of the service, where all the server side was rolled into one Rails app

it falls within TACE

4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.

All this hoopla seems out of character for the sedate man who likes to say of his work: ''Whatever I did, there was always someone around who was better qualified. They just didn't bother to do it.''

War assault weapons have no place except with military?

just include jQuery from a CDN

jQuery is, last I checked, over 200k unminified.

The security of the data (authentication, confidentiality, integrity and forward secrecy) is handled by the transport security protocol, BTP. The same protocol is used for all transports. BTP is an obfuscated protocol: to anyone except the intended sender and recipient, all data is indistinguishable from random. So BTP's first job is to let the recipient know who sent the data, so the recipient can use the right key to authenticate and decrypt it.

could a few carefully-placed lines of jQuery

your 40-pound jQuery file and 83 polyfills

magic

And events are just data so can process, enrich, filter, aggregate, visualise the data with your own tools.

only jquery

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.

Just Christoph Udenius, for example, sug-gested leaving thirty or forty blank pages at the end of a commonplace book to be filled in with a well-made subject index, or devoting a separate in-octavo booklet for this essential task;

existe una mayor probabilidad de contratación si se cuenta con una carrera universitaria.

Even if #foo is originally on the page and then removed and replaced with a #foo which contains baz after a short wait, Capybara will still figure this out.

As long as you stick to the Capybara API, and have a basic grasp of how its waiting behaviour works, you should never have to use wait_until explicitly.

Let’s make that really clear, Capybara is ridiculously good at waiting for content.

apybara could have easily figured out how to wait for this content, without you muddying up your specs with tons of explicit calls to wait_until. Our developer could simply have done this: page.find("#foo").should have_content("login failed")

Calling a software convention "pretty 90s" somewhat undermines your position. Quite a lot of well-designed software components are older than that. If something is problematic, it would be more useful to argue its faults. When someone cites age to justify change, I usually find that they're inexperienced and don't fully understand the issues or how their proposed change would impact other people.

All these problems are solved in zeitwerk mode, it just works as expected, and require_dependency should not be used anymore, it is no longer needed.

And on any given day, developing with Svelte and its reactive nature is simply a dream to use. You can tell Svelte to track state changes on practically anything using the $: directive. And it’s quite likely that your first reactive changes will produce all the expected UI results.

Let's not get over-excited. Actually, we're only part-way there; you can compile this code with the TypeScript compiler.... But is that enough?I bundle my TypeScript with ts-loader and webpack. If I try and use my new exciting import statement above with my build system then disappointment is in my future. webpack will be all like "import whuuuuuuuut?"You see, webpack doesn't know what we told the TypeScript compiler in the tsconfig.json.

Noticed that with 100+ s, I am not alone here. There are definitely a lot of devs wanting this feature. So I took some time out and decided to give this a go myself. I have created a PR for the same

What happens when you look it up in a dictionary rather than as a phrase in Google? Google just catalogues other people's [mis-]uses

hover and resize window support #965 Closed Sorry, something went wrong. Collaborator jnicklas commented on Feb 25, 2013 Go, go @twalpole!

Meanwhile, we remain trapped in two countries. Each one is split by two narratives—Smart and Just on one side, Free and Real on the other. Neither separation nor conquest is a tenable future. The tensions within each country will persist even as the cold civil war between them rages on.

Just America is a narrative of the young and well educated, which is why it continually misreads or ignores the Black and Latino working classes.

In the same way that libertarian ideas had been lying around for Americans to pick up in the stagflated 1970s, young people coming of age in the disillusioned 2000s were handed powerful ideas about social justice to explain their world. The ideas came from different intellectual traditions: the Frankfurt School in 1920s Germany, French postmodernist thinkers of the 1960s and ’70s, radical feminism, Black studies. They converged and recombined in American university classrooms, where two generations of students were taught to think as critical theorists.

'...ee' is usually paired with an '..er', isn't it? Employee/Employer, Trainee/Trainer. I wouldn't use Coachee because to me, it implies you're a Coacher, not a Coach.

When mocking is deemed profitable:

The field/element/path extraction operators return NULL, rather than failing, if the JSON input does not have the right structure to match the request; for example if no such key or array element exists.

“You can’t use HTML5 or CSS3 in email.” Due to their “limited” support, the idea that using HTML5 and CSS3 in email is “impossible” remains a commonly-held notion throughout the email design industry. However, we’re calling it a complete myth.

Just because there can be issues with CSS in HTML emails doesn’t mean you should abandon efforts to use it. It all comes down to determining which codes are absolutely needed and how to style them so they can be rendered by email platforms.

(Yes, I realize from a technical, end-user perspective this really doesn't matter.)

Although echo "$@" prints the arguments with spaces in between, that's due to echo: it prints its arguments with spaces as separators.

unsuspecting childlikeness

Many designers strive to create products that are so easy to navigate, their users can flow through them at first glance. To design something with this level of intuitiveness, it’s imperative designers understand affordances—what they are and how to use them.

# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end

find_field finds by id, name or placeholder text - so find_field('Prefix') should find the element with matching placeholder text rather than needing xpath.

The beauty of hypertext is that we’re able to quickly add much-needed context helpful for n00bs but easy enough for those already in-the-know to scan over. And making documentation more human-readable benefits everyone.

Svelte is there when I need it with useful APIs, but fades into the background as I put my app together.

One part of React that I've always championed is how it's just JavaScript. I like that in React you don't use a distinct template syntax and instead embed JavaScript, compared to Svelte's templating language

I will always find React's approach easier - at least in my head - and I think more friendly to people familiar with JavaScript who are learning a library.

Just? The meaning of the word is the reason we used the word.

It means "You're about to talk about words, but words don't matter."

I am wondering if it wasn't faster for maintainers/developers who know the glib code to just provide a fix instead of writing comments on this issue.

Those sorts of complaints are like saying that someone is not a buddhist unless they speak Pali.

Another important MicroJS attribute is independence. Ember, Backbone—even Bootstrap to a degree–have hard dependencies on other libraries. For example, all three rely on jQuery. A good MicroJS library stands by itself with no dependencies. There are exceptions to the rule, but in general, any dependency is another small MicrojJS library.

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

Last week, I shared how to check if an input is empty with CSS. Today, let’s talk about the same thing, but with JavaScript.

You can do and impressive amount of form validation with just HTML attributes. You can make the user experience pretty clean and clear with CSS selectors.

the client form validation is the one I like a lot, because, for example, by adding required attribute to an input, I don’t need to write any additional JavaScript to warn a user, when the user submits a form without filling out the required fields

Here's another plain ES2015/2017 version

There’s no additional logic from Trailblazer happening here. The function returns a well-defined hash which is passed as an argument to step.

Keyword arguments allow to define particular parameters as required. Should the parameter be missing, they also provide a way to set a default value. This is all done with pure Ruby.

This is failing CI because CI is testing against Rails < 6. I think the appropriate next steps are: Open a separate PR to add Rails 6 to the CI matrix Update this PR to only run CSP-related test code for Rails >= 6.0.0 Can you help with either or both of those?

That such minimalism is possible does not mean that it is necessarily desirable

This is how the same example would look like using raw monads:

which entails computer programming (process of writing and maintaining the source code), but also encompasses a planned and structured process from the conception of the desired software to its final manifestation

Operations define the flow of their logic using the DSL and implement the particular steps with pure Ruby.

The main realization came when I figured out that the main_model was just another association. This means we can move a lot of logic to just that class and reason about it a lot better.

This branch is 22 commits ahead, 207 commits behind newsapps:master.

Naming is just one part of the micro-design activity that we call programming. If design weren’t hard, we wouldn’t find good design so satisfying.

when it comes to personal machines, I expect them to just work so I can work.

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.

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)

If you teach your users to trust that URL bar is supposed to not change when they click links (e.g. your site uses a big iframe with all the actual content), then the users will not notice anything in the future either in case of actual security vulnerability.