That modality, as Freinacht suggests, will also already exhibit its own negative results and excesses, eventually needing a purification generator.

Another limitation in this implementation is that passing other options in the shebang to vite-node won't work, as I expect exact indexes in order to figure out what are the arguments to forward. It's not perfect but I think it's good enough to unblock people like me as a start. 👍

It is through embodied proprioception that we can make the transition to the more fulfilling interactions of a cybernetic reality that is not merely virtual but actual.

I believe the digital age simply makes obvious the virtual nature of what we have long taken as reality, so that now, its lack of genuine substance is no longer deniable. And this is what drives us into addiction. For, no virtual substance, no one-sidedly artificial affirmation or negation, can fill in for the paradoxical actuality of our fleshly being.

the point of futuring is that you need to connect facts and fictions because that is how this these future Visions become socially performative

Why not a library? We've found it extremely hard to develop a library that: Supports the many database libraries, ORMs, frameworks, runtimes, and deployment options available in the ecosystem. Provides enough flexibility for the majority of use cases. Does not add significant complexity to projects.

The goal of Lucia v3 was to be the easiest and cleanest way to implement database-backed sessions in your projects. It didn't have to be a library. I just assumed that a library will be the answer. But I ultimately came to conclusion that my assumption was wrong. I don't see this change as me abandoning the project. In fact, I think it's a step forward. If implementing sessions wasn't easy, I wouldn't be deprecating the package. But why wouldn't a library be the answer? It seems like a such an obvious answer. One word - database. I talked about how database adapters were a significant complexity tax to the library. I think a lot of people interpreted that as maintenance burden on myself. That's not wrong, but the bigger issue is how the adapters limit the API. Adapters always felt like a black box to me as both an end user and a maintainer. It's very hard to design something clean around it and makes everything clunky and fragile, especially when you need to deal with TypeScript shenanigans.

Once an authenticated session has been established, the session ID (or token) is temporarily equivalent to the strongest authentication method used by the application, such as username and password, passphrases, one-time passwords (OTP),

Friedman is correct, for example when he points out the importance of changes like the rise of India or China, the spatial fragmentation of the production process through offshoring or the lowering of transaction costs that makes more and more services tradable.

Until some company or scientist says ‘Here’s the proof! We can definitely have a safety mechanism that can scale to any level of intelligence,’ I don’t think we should be developing those general superintelligences.We can get most of the benefits we want from narrow AI, systems

This lack of recognition is what I think ails the contemporary doctrinaire left. It does that because it has over time adopted the prejudices of capitalist liberalism, which sees only abstract individuals, not people rooted in histories and territories. By failing to protect the working majorities, the somewheres, it drives them to the populist right, and it does this because they are 'nowheres', unrooted. It is precisely this un-rootedness, this up-rootedness, that makes them blind to the issues of the somewheres, and it is also what drives identity politics.

Most environmental books now are about practical technological innovation or social changes that have to happen. My argument is that’s not going to work. That’s not going to happen. It requires a transformation in our assumptions about the nature of what we are and what the world is. Otherwise, that instrumental and exploitative relation will remain.

There's not necessarily a process by which that communities decide who comes in or countries decide who comes in to work on these problems that have been decided outside.

I had a wonderful conversation with an American a few years ago when he was interviewing me and he said Graham this is really intriguing because it sounds like you end up with very light need for regulation that this would appeal to the libertarian end and I said absolutely there's almost no need to tax these companies because the state may be a stakeholder with rights to dividends and capital gain so you don't need to tax the company you don't need regulation

you have to have the power of stewardship first of all you have to have stewards representing the voice of nature

If we are underestimating, then does that mean our carbon budget figures are too high and we don't have 5 years of carbon budget remaining at the BAU rate, but significantly less?

working group three does exons and the fossil fuel companies for them by delaying action by stuffing their models full of all sorts of spuris pseudo Tech to mean we don't have to do things by well but now by the literally within a few years I mean what really matters now is what we actually do between now and 2030 that's the time frame of action not the time frame to bring about action the time frame in which to act

third thing okay um and the fourth thing soft power within the United

we now realize the base pairs come to join each other up together as the system unravels and forms a new pair of DNA molecules well up to a point it does and that point is known to be accurate to about one in 10,000 base pairs now if you and I wrote an article and there was only one typo in a 10,000w article we'd be very pleased but this is nowhere near enough for a DNA sequence of three billion base pairs there would be half a million at least of Errors

if I send you a Google doc and we start all collaborating in the same same thing and it's amazing we're sharing all this data um it's kind of silly that we have to move the updates through the backb to some server out there and shipping them back here when we now have really sophisticated algorithms that can do um you know smart Conflict Free resolution that allows us to collaborate in real time and yet we're still moving all the updates to the backbone right this is very silly and it gets worse when you think about the network falling apart

let's go and and create all this great software to deploy it and kind of equalize the the the disparity of wealth across the world and ends up being locked out for by stupid issues like latency and bandwidth

Will gradual typing be supported long term or is it a fad? Will this be an abandoned investment?

development becomes as popular as mindfulness

if development becomes as popular as mindfulness

the soul is also a collective being right so you know you have to have done your own individual work so to speak before you do that because otherwise you're going to have conflicts with the with the collective because you know if you're not yet individuated you're going to have issues with a collective because you have to be paradoxically an individual in order to actually fully function within a collective without being swallowed

Then there are, for example, in the United States, you have to do a a lot more scrutiny of dollars you receive because they don't get taxed.

Dikert et al. (2016), in theirseminal study on challenges and success factors for large-scale agile transformations, drawattention to the need for more studies that address the agile transformation process with abroader perspective, going beyond software development practices.

The fact that many here are maintainers of Ruby implementations also has a biased effect on new features, as they might represent a burden on them. I'm not saying this is a bad thing, I love the diversity of points of view that this brings! OTOH, it's fair that people that do take time to discuss things here have a bigger influence on the direction that Ruby follows.

Dikert et al. (2016), in their seminal study on challenges and success factors for large-scale agile transformations, draw attention to the need for more studies that address the agile transformation process with a broader perspective, going beyond software development practices.

The point of GPL licenses is to protect the user of the software, not the developer. If you want "protection" as a developer, use MIT (disclaimer of warranty). GPL "infects" other parts of a system to combat a work-around which was used to violate the software freedom of the user, by firewalling sections of GPL'ed code from the rest of the system. If you don't care about your users' software freedom in the first place, then (L)GPL is the wrong choice.

Our estimated safe ESB is that around 50–60% of global land surface should be in largely intact, natural condition to halt species extinction, secure biosphere contributions to climate regulation, and stabilise regional water cycles.

The small prefixes were also added, even without such a driver, in order to maintain symmetry.

You can also schedule a block to run immediately and periodically with Timers::Group#now_and_every

Despite this panoply of stories, we are in fact living in a time between stories, because the d

I think people need to understand we are up against an event 00:36:00 that is one of six in Earth's history like hurtling towards it at an outrageous Pace in order to kind of galvanize especially leaders

the thought has occurred to me that we need a new religion that religion is one of the few things 01:09:15 that will make people act in ways beyond their own immediate interest well i've heard a lot of people say that

most of the great religions in the world have been attempts to to restrain or reform uh human nature or at least uh channel our worst impulses into something 01:10:48 more productive or higher something loftier um and in this this is exactly what we need here it's something that will create a form of altruism which doesn't only extend to people we see around us now but extends 01:11:00 to the future generations

i think it's a near miss it's the most likely thing to save us

who are these people that have a high LDL but they are metabolically healthy

I think you linguists worry too much. It's a simple enough formation using a very common prefix, and while it is not clear whether "I disprefer" means "I do not prefer" or "I prefer something other than" or "I prefer the opposite of" or "I stop preferring", either it'll settle down to one meaning or it'll carry a range. So what? This is the first time I've heard the word but I don't find it particularly puzzling.

Having read this, it appears that there is a reasonable consensus and, given that, I will probably add it to my vocabulary as it does fill a niche – but I'll be careful where and with whom I use it.

There's a void — a need where a word should fit. There's a construction — a prefix and a root, which fit together to fill the void. Meaning is clear on first encounter. A need is met. What is the problem?

One participant in particularsaid, “My favorite aspect of Blackboard is the accessibility of thegrades and find course documents–when professors followa standard layout.”

A major implication of the lack of effective training is thatstudents are often left to struggle through disjointed, flawedlearning experiences while using LMSs during a class.

robust theme in the reasons given for preferringface-to-face delivery formats is the perceived lack of interactionwith an instructor in online courses.This was evident in statementsthat suggested that students believe they would have to “teachthemselves”, or that they would prefer a course taught by a “hu-man” or a “real teacher”.

Ain't it possible that every message I send or forward will just be replaced to the outbox and will be send by Thunderbird in the background ? I really hate it that every message sends itself away, running on top of all other windows, and it makes me wait till it has been sent from reading my other messages...

as you come up with a list of the subject areas or categories you want to include in your zettle costume i recommend that for at least some of them you add some subcategories maybe go two or three levels deep as you can see i've done here for my philosophy subject area you're going to have to hit pause if you want to look at this any longer now although i recommend that you build out some of your subject areas unless the subject area is one you are already really knowledgeable about i recommend that you not build out that subject area beyond just two or three levels that's because the vast majority of how your settle costing is organized should be determined only as you are creating new cards to put in your xettlecostin that at least is how lumen did things as schmidt points out in the article about the zettelcosta method that i mentioned earlier lumen opted for organizing entries or new cards based on the principle that they must have only some relation to the previous entry or previous card without also having to keep some overarching system in mind

The purported reason seems to be the claim that some people find "master" offensive. (FWIW I'd give that explanation more credence if the people giving it seem to be offended themselves rather than be offended on behalf of someone else. But whatever, it's their repo.)

How to use “case” to match class names? (=== not so funny)

But what if you want to reuse one layout within another?

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

That helps us keep GitLab simple as long as we can.

[With Zeplin] we started to engage both UX and engineering teams in the same conversations and suddenly that opened our eyes to what was going on, and overall streamlined our build process.

Why should this conversation be separate from other conversations about the work to be done? Design is one consideration alongside frontend and backend considerations, which often all intersect and require the same participants. Shifting this discussion to a separate work item can result in disjointed conversations and difficulty finding where a decision was made.

You can see how the constant jumping between these two tools in the first scenario is super annoying, and also very risky as none of the changes you make in Figma are also automatically being updated in the same GitLab designs.

I don't know how much impact the "Design management" widget vs. "Design" object decision will have, except for the extremely small number of teams that work exactly like we do.

Personally I think we could get a ton more benefits and would also be able to pull new users into our platform by finding better ways to integrate/link/connect/display Figma in our work item objects. Today the biggest downside for "Design management" is that it's basically just a copy of what's happening inside of Figma that has to be manually kept in sync and requires users to constantly switch back and forth:

The third is the brain of the observer. This is also a strong element in film criticism where the camera is the third eye, the eye of the artificial narrator. The most intelligent film about the third eye spying on the action is `Snake Eyes,' where we last saw Gugino. (You may want to check my comments on that film to see what I mean.)

the canonical unit, the NCU supports natural capital accounting, currency source, calculating and accounting for ecosystem services, and influences how a variety of governance issues are resolved

And because the upsides are so obvious, it’s particularly important to step back and ask ourselves, what are the possible downsides? … How do we get the benefits of this while mitigating the risk?”

you do need people who would take the discoveries and findings of Science and translate them into terms that will be accessible to the vast 00:54:05 majority of of the public and again if you don't have any scientists who tell the history of humanity then you will have people who have no regard for to 00:54:17 for science whatsoever doing I think a much much worse job telling the history of humanity

I disagree. What is expressed is an attempt to solve X by making something that should maybe be agnostic of time asynchronous. The problem is related to design: time taints code. You have a choice: either you make the surface area of async code grow and grow or you treat it as impure code and you lift pure synchronous logic in an async context. Without more information on the surrounding algorithm, we don't know if the design decision to make SymbolTable async was the best decision and we can't propose an alternative. This question was handled superficially and carelessly by the community.

The problem with this pile of questions is that, instead of helping the OP get out of the X Y problem, people stay focussed on Y, mark the question as a duplicate of Y in a matter of minutes and X is never properly addressed.

It would have been fantastic to eschew this ridiculousness, because we all make fun of branded vulnerabilities too, but this was not the right time to make that stand.

Non-aims (but may happen anyway):

I think we are a victim of behavioural norms and so many of the apps that I use have this pattern. That's not to say it's the right behaviour, but it may be hard to break the pattern for users.

rendered.should have_selector("#header") do |header| header.should have_selector("ul.navlinks") end Both of which silently pass - however, capybara doesn't support a :content option (it should be :text), and it doesn't support passing blocks to have_selector (a common mistake from Webrat switchers).

expect(described_class.active).not_to include_any_of [records_not_to_be_included]

XMI describes solutions to the above issues by specifying EBNF production rules to create XML documents and Schemas that share objects consistently.

New York-based startup DoNotPay created an AI-based way for people to contest traffic tickets—a user would wear smart glasses that would feed it information to say in court generated by AI—but before the creator could introduce it in court, he said he got threats from multiple bar associations about “unauthorized practice of law,”

I commonly find myself wanting to assert that a certain field contains a certain value.

Have you ever: Been disappointed, surprised or hurt by a library etc. that had a bug that could have been fixed with inheritance and few lines of code, but due to private / final methods and classes were forced to wait for an official patch that might never come? I have. Wanted to use a library for a slightly different use case than was imagined by the authors but were unable to do so because of private / final methods and classes? I have.

Been disappointed, surprised or hurt by a library etc. that was overly permissive in it's extensibility? I have not.

what I'm asking people to do is to start considering what that means to your life what I'm asking 00:38:53 governments to do by if like I'm screaming is don't wait until the first patient you know start doing something about we're about to see Mass job losses we're about to see you know Replacements 00:39:07 of of categories of jobs at large

“Why do we need to learn [this]?” where [this] is whatever I happened to be struggling with at the time.  Unfortunately for everyone, this question – which should always elicit a homerun response from the teacher

those who got the updated booster had one-tenth the risk of being hospitalized compared with those who are unvaccinated

First, dictionaries are not arbiters of highly literate writing; they merely document usage. For example, irregardless has an entry in many dictionaries, even though any self-respecting writer will avoid using it—except, perhaps, in dialogue to signal that a speaker uses nonstandard language, because that is exactly how some dictionaries characterize the word. Yes, it has a place in dictionaries; regardless of that fact, its superfluous prefix renders it an improper term.

to break up methods into logical paragraphs internally.

There's a fundamental error in your question: commits are not diffs; commits are snapshots. This might seem like a distinction without a difference—and for some commits, it is. But for merge commits, it's not.

tested

That tends to be the biggest cop out excuse for libraries. Just do a major version release. The fact this library lies about the encodingis extremely problematic and causes numerous bugs. Any program currently using this library is already incorrect because of this behavior. Actually exposing the problem makes it easier for people to fix.

Agree, but we're stuck with API compatibility for a good while.

Do you plan to continue merging MR and releaseing new versions for this Gem? I don't think there is any similar gem like this, so it would be sad to see it fade away.

it really all does 00:06:53 trace back to the start of our what we call civilization our civilization meaning Agriculture and then settlements and cities so prior to that we lived in approximate equilibrium with ecosystems

While this offers flexibility to address many operator use cases, it makes simple use cases, like the developer use case, more complicated to express than they need to be.

I have yet to see a Snapd or Flatpak build of Audacity that I'm happy with. Those builds are beyond our control as they are made by 3rd parties. I do find it mildly annoying that Flatpak direct users that have problems with their builds to us.

I have DNS settings in my hosts file that are what resolve the visits to localhost, but also preserve the subdomain in the request (this latter point is important because Rails path helpers care which subdomain is being requested)

I've developed additional perspective on this issue - I have DNS settings in my hosts file that are what resolve the visits to localhost, but also preserve the subdomain in the request (this latter point is important because Rails path helpers care which subdomain is being requested) To sum up the scope of the problem as it stands now - I need a way within Heroku/Capybara system tests to both route requests to localhost, but also maintain the subdomain information of the request. I've been able to accomplish one or the other, but haven't found a configuration that provides both yet.

Benoit Daloze of TruffleRuby points out that this is all much easier to read if you define your Ruby internals in Ruby, like they do. He's not wrong.

session = ActionDispatch::Integration::Session.new(Rails.application) response = session.post("/mypath", my_params: "go_here")

Testing frameworks often introduce their own abstractions for e.g. evaluation order, data validation, reporting, scope, code reuse, state, and lifecycle. In my experience, these abstractions are always needlessly different from (and inferior to) related abstractions provided by the language itself.

Check the "Auto-open DevTools for popups".

Changing the second line to: foo.txt text !diff would restore the default unset-ness for diff, while: foo.txt text diff will force diff to be set (both will presumably result in a diff, since Git has presumably not previously been detecting foo.txt as binary).

a little flaw (Google translation can not find the translation of the word "瑕疵", so can only use the word "flaw" instead)

so this means that there are no documentation telling you that this is the way you have to do it anywhere so naturally a lot of devs do not know about this, unless they ask about it by luck or of curiousity.

Definable grammars for pattern matching and generalized string processing

First and foremost, we need to acknowledge that even though the funding goal has been met–it does not meet the realistic costs of the project. Bluntly speaking, we did not have the confidence to showcase the real goal of ~1.5 million euros (which would be around 10k backers) in a crowdfunding world where “Funded in XY minutes!” is a regular highlight.

Machines understand languages, that are formal and rigid, with unique and unambiguous instructions that are interpreted in precisely one way. Those formal, abstract languages, and programming languages in general, are hard to understand for humans like ourselves. Primarily, they are tailored towards the requirements of the machine. The user is therefore forced to adapt to the complexity of the formal language.

it quickly becomes a mess of non related functions that anyone but the owner feels brave enough to import

The rules recorded in natural language are readable not only by humans but also by the computer and therefore no longer need to be programmed by a software developer. This task is now taken over by openVALIDATION.

The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.

Nobody expects the v3 schema to be more of a perfect guarantee than the v2 schema (as said above, consider operationId). Just release a schema and let the dice fall where they may.

One of the reasons I initially pushed back on the creation of a JSON Schema for V3 is because I feared that people would try to use it as a document validator. However, I was convinced by other TSC members that there were valid uses of a schema beyond validation.

without a schema, you do not have a spec, you have an aspiration.

When we do release a final version of JSON Schema, please do not use JSON Schema to guarantee an OpenAPI document is valid. It cannot do that. There are numerous constraints in the written specification that cannot be expressed in JSON Schema.

JSONPath contains verbiage that allows for an empty array to be returned in the case that nothing was found, but the primary return in these cases is false.

Multiple different people have been discussing multiple different problems, and asking for examples of the other problems, talking past each other and generally this thread got to an unreadable point due to this confusion.

We do not want to change or remove additionalProperties. Providing a clear solution for the above use case will dramatically reduce or eliminate the misunderstandings around additionalProperties.