There has to be a better way for us to manage Javascript build/run scripts. Everything for this platform seems tacked together. quotes with escaped quotes and npm builds to call other 'npm run' builds.. This is getting pretty painful.

Prettier intentionally doesn’t support any kind of global configuration. This is to make sure that when a project is copied to another computer, Prettier’s behavior stays the same. Otherwise, Prettier wouldn’t be able to guarantee that everybody in a team gets the same consistent results.

In PostgreSQL, there is an entity called a schema (which we believe should be called folders).

With Vitest you get to define the configuration for your dev, build and test environments as a single pipeline, sharing the same plugins and the same vite.config.js.

Vitest aims to position itself as the Test Runner of choice for Vite projects, and as a solid alternative even for projects not using Vite.

Think of a client island as an interactive widget floating in a sea of otherwise static, lightweight, server-rendered HTML. Server islands can be added for personalized or dynamic server-rendered elements, such as a logged in visitor’s profile picture.

So, if we have a class that is a repository dealing with invoice entities, we should name it something like `InvoiceRepository`, which will tell us that it deals with the Invoice domain concept and its architectural role is that of a repository.

As Frameless Art Curator, Rosie O’Connor states: “We know that people who visit galleries as children are more likely to consume culture as they reach adulthood, but they can struggle with the height of the paintings and inaccessible language rooted in the art world. At Frameless the whole experience has been designed to be entertaining and accessible to all with an aim to spark an interest in these magnificent artworks and to hopefully even inspire visitors to seek out the original versions”.

Noah Geisel,

this leads to the undermining of every aspect of the nation-state: the welfare state; the power of the legal system; the national economy; the corporatist systems that connected one with the other; and the parliamentary democracy that governed the whole.

It makes a lot of sense to have this different strategy of being rooted in the real physical world and have digital nomads being as like a guild of knowledge workers that seed their specialized knowledge because localism is necessary and good, but it's also not necessarily very innovative. Most people at the local level just keep repeating stuff. It's good to have people coming in from the outside and innovating.

advances in prompt engineering1, agents2, retrieval-augmented generation (RAG)3, and fine-tuning4

if Consciousness were to go floating around how the hell do you explain how it can see anything without eyes

we think of kindness and compassion in a way that's very similar to the way scci other scientists think about language

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

At the heart of Chinese philosophy is a belief in the innate goodness of humanity. This principle is encapsulated in the ancient phrase: “Man on earth, good at birth. The same nature, varies on nurture.”

working group three is just Exxon in Disguise um you know there are good people in working group three but working group three and integrated assessment models good people working some of the people are good people there working in deeply subjective boundaries that have been set up by we mustn't Rock the political boat

encourage doing ‘less bad’ on the environment as compared to the alternative (McDonough and Braungart, 2013).

America has lost its capacity the American state has been hollowed out they cannot build Bridges they used to be able to really very well

Over the last 25 years, shotgun metagenomic sequencing1 and associated computational methods have developed as robust, efficient ways to study the taxonomic composition

Romanticizing any society as purely altruistic undermines their sophistication and resilience.

Fortunately, we do not have to agree on everything. Linked Data enables layered agreements, in which a few rules need to be adopted by many, and sets of additional rules are agreed upon by smaller groups as required.

Freedom of course always comes at a cost: what constitutes a victory for personal rights and freedom of speech also facilitates the spread of illegal messages, since decentralized networks make it harder to control what information is exchanged. Legality is of course a tricky matter, as some countries instate laws that prevent their citizens from voicing opinions that would be legal elsewhere.

There are two things that I enjoy: a test framework written in my own Domain Specific Language (DSL) that is easily understood by all those on a project and the ability for all participants to easily read, search, and view the tests.

Humanity in general is to develop tools to identify detect and communicate with all kinds of intelligences and very unconventional embodiments that we are not good at

input

Disable all observers in your test suite by default. They should not be complicating your model tests because they should have separate concerns anyway. You don't need to unit test that observers actually fire, because ActiveRecord's test suite does that, and your integration tests will cover it.

In cases where I've been concerned about the migration of data (e.g. copying my entire home directory from one system to another), I've used fingerprint to generate a transcript on the source machine, and then run it on the destination machine, to reassure me that the data was copied correctly and completely.

Sure, it is not needed, we can always write things in a different way. As a matter of fact, with such an argument, hardly any improvement should be accepted.

The Dominican Republic has been a political and economic success story in contrast to its neighbor and, unlike Haiti, is secure enough for the secretary of state to spend the night.

with the Verve foundation's help we set up ecologies of practices uh we have a practice called dialectic into dialogos that helps people get into mutually shared flow states of cognitive exploration and people discover collective intelligence as something that is phenomenologically present and almost agentic in what's happening

We present high quality image synthesis results using diffusion probabilistic models,a class of latent variable models inspired by considerations from nonequilibriumthermodynamics. Our best results are obtained by training on a weighted variationalbound designed according to a novel connection between diffusion probabilisticmodels and denoising score matching with Langevin dynamics, and our models nat-urally admit a progressive lossy decompression scheme that can be interpreted as ageneralization of autoregressive decoding. On the unconditional CIFAR10 dataset,we obtain an Inception score of 9.46 and a state-of-the-art FID score of 3.17. On256x256 LSUN, we obtain sample quality similar to ProgressiveGAN. Our imple-mentation is available at https://github.com/hojonathanho/diffusion.

there are a lot of things that can damage the mitochondria okay poor diet in general will damage 00:09:16 the mitochondria because mitochondria are made of fats but they're made of specific fats and if you don't get enough of those specific fats in your diet essential fatty acids in your diet you can't make good mitochondria

11. Noble Cause CorruptionThe greatest evils come not from people seeking to do evil, but people seeking to do good and believing the ends justify the means. Everyone who was on the wrong side of history believed they were on the right side.

I'm surprised no one has mentioned disambiguate in this context. It sounds horrible and outlandish on first hearing, has a reasonably transparent meaning (which may shed some light on the semantics of dis-), and seems to be used almost exclusively by linguists.

Who says it's not a word? Not a word, simply because lexicographers have not recognized it? When a lexicographer recognizes it, it has already been in use! Even Mr. Fiske says it is a word, although he obviously disprefers it.

I believe it is possible to disprefer something while either 1. not disliking it, or 2. liking it but not intensely enough to be the preference. As in, "I like tart apples, but I sometimes disprefer them as an ingredient on a green salad." It doesn't and hasn't, meant I would refuse to eat a salad with this ingredient included, but there are times when my preference would have been to have a salad without them.

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.

If you said anti-prefer, I'd have a better idea of what the word meant.

Amy: It's a real word. I use it all the time (of course, I'm a linguist, and I allow the possibility that I picked it up from my linguist chums, though it doesn't seem particularly jargony to me). For me, "disprefer X" means something like "not choose X when other options are available". This is subtly different from "prefer anything over X", quite different from "not prefer X", and totally distinct from "dislike X" or "object to X".

"We can do more to heal Grandmother Earth and protect her sacred children. The birth of this calf is both a blessing and warning.”

Although many projects and ideas share Elinor Ostrom's personal, cooperative and Earth-helping significance, they lack the chain reaction that keeps them going.

“etheric realm,” as well as in some fifteen thousand hours of recordings that have for many years been stored in a concrete bunker in Montana.

This is probably confusing because the "host" in --network=host does not mean host as in the underlying runner host / 'baremetal' system. To understand what is happening here, we must first understand how the docker:dind service works. When you use the service docker:dind to power docker commands from your build job, you are running containers 'on' the docker:dind service; it is the docker daemon. When you provide the --host option to docker run it refers to the host network of the daemon I.E. the docker:dind container, not the underlying system host.

The cell phone providers usually call them "mobile" phones which is more precise since "cell" refers to a kind of technology.

However, it is increasingly becoming just a "phone", as landlines continue to disappear from households.

I wouldn't focus too much on "posted only after human review" - it's worth noting that's that's worth nothing. We literally just saw a case of obviously riduculous AI images in a scientific paper breezing through peer review with noone caring, so quality will necessarily go down because Brandolini's law combined with AI is the death sentence for communities like SE and I doubt they'll employ people to review content from the money they'll make

"that post is written in a very indirect and unclear way" -- that is intentional, no? The company has been communicating in this style for quite some time now. Lots of grandiose phrases to bamboozle the audience while very little is actually being said. It's infuriating.

On the surface, this is a very nice sentiment - one that we can all get behind.

Don't think that I just naturally perfectly segment these commits when creating the feature. I heavily rebase and edit the commits before creating a PR.

Asking questions ensures they fully understand whatever it is they’re doing. They don’t go into projects blindly or assume anything. They ask probing questions to gain a complete understanding of what it is they’re trying to accomplish, why they’re working towards that goal, and everything else in between. Having an analytical mind ensures that they don’t let any details slip through the cracks.

It means the booth specifically, without any extra bits. By way of example: "Times Square" might often be used to refer to the area around Times Square, but may include things which are not actually part of the Square. To narrow such a usage, one might say "I mean only the actual Times Square" or "I mean Times Square proper."

To prevent accidental unsubscriptions, senders return landing pages with a confirmation step to finish the unsubscribe request. A live user would recognize and act on this confirmation step, but an automated system would not. That makes the unsubscription process more complex than a single click.

I suppose it would be easy to make a pushshopt function like there is a pushd, and use bash arrays to remember previous option before setting them. Like pushshopt +extglob -nocasematch and popshopt

Our diagrams and charts make it easy to see where every dollar of your hard-earned money is flowing, so you can track your spending patterns at a glance.

Don't worry about performance too early though - it's more important to get the design right, and "right" in this case means using the database the way a database is meant to be used, as a transactional system.

I find it ridiculous that we spend energy on debating whether an alternate spelling is "correct" - real people, not English professors and dictionary authorities, are the authorities on English-as-used, and will ultimately make the distinction irrelevant.

It's like someone creating a new List and a new Set, printing their size(), and then asking what's the difference. Of course, there is none: The size is 0 for both.

nowadays many people work with docker containers. Most default docker images do not have bash and something like [[ $string == *foo* ]] will not work.

It's not so much a criticism as the preference of a more universal solution over a more limited one. Please consider that, years later, people (like me) will stop by to look for this answer and may be pleased to find one that's useful in a wider scope than the original question. As they say in the Open Source world: "choice is good!"

The title of the question is what triggered the process of finding this Q/A for material that aided development of the above to solve a real life problem described by the title. The OP declared that base64 decode was not the "real" problem; pedantic constraint of answers to a particular "example" seems less helpful. When this question and its answers were key to helping solve real problems, alternate answers can be gifts to the community in recognition of the fact that many more people will use this Q/A to solve problems. Since the answer is on-topic per the title, I feel it is "game on".

The main change with Ruby 3.0 is that it differentiates between passing a hash and passing keyword arguments to a method with variable or optional keyword parameters. So def my_method(**kwargs); end my_method(k: 1) # fine my_method({k: 1}) # crashes

Yes, but to what version? A patch version only, e.g. you released 1.0.0, so the "next" version is 1.0.1? Why not 1.1.0? You don't know ahead of time what version you'll be releasing until it's actually released

Then I gave the question a longer, more descriptive title: I made it an actual question (with a question mark and everything), and replaced the term "lazy evaluation" with a more concrete description. The goal is to make the question more recognizable and more searchable. Hopefully this way, people who need this information have a better chance of finding it with a search engine; people who click through to it from a search page (either on Stack Overflow or from external search) will take less time to verify that it's the question they're trying to answer; and other curators will be able to close duplicates more quickly and more accurately. This edit also improves visibility for some related questions (and I made similar changes elsewhere to promote this one appropriately).

Regardless of what your arguments are, the personal reasons of the developer are what matters for what platforms this game is provided on. You can choose to pay for the game, or not. Paying for the game supports the developer, and allows them to develop more. It is not reasonable to argue that someone should have put in additional unpaid effort to do something for unknown future benefit, or that they should charge less for a game because it's only available on one platform; that's their choice, and their decision.For context, development of Taiji was started in mid 2015; it took seven years to finish. That's with the Commercial Game Engine, and even with that, there were platform-based bugs that needed to be worked around (issues that won't be present on other platforms, or will have different presentations); here's just one of those, involving an issue around mouse sluggishness:https://taiji-game.com/2020/07/13/68-in-the-mountains-of-madness-win32-wrangling...If the developer is not already familiar with Linux, then there's a small mountain of language barriers around using Linux that needs to be overcome first, before being able to get to the game development phase. It's rare for game development to work on different platforms when it can't be tested on those different platforms. While it might be easy to cross-compile on a Windows system (e.g. via IL2CPP), that's only if everything works perfectly (which is unlikely to be the case). 

when you actually have chronic anything usually it's not a good result

Leave Their Belongings—and Heal

Board view Subtasks are shown slightly indented from the main task Subtasks can be dragged out of the parent task to a new list to indicate their status. For subtasks with a different status to their parent, it displays a dummy parent (ghosted), above the subtask in the list, with the parent's status label visible against the dummy. Dragging the parent task to a different list changes the label of the child tasks as well, and any sub tasks already in its new list are re-organised under the parent and any dummy removed

Using an issue tracker without them is, in my opinion, a little like using an outlining program that only supports two levels of nesting, or like using Wiki software that doesn't have the concept of reverse links. Makes me sad!

It's also common to want to compute the transitive closure of these relations, for instance, in listing all the issues that are, transitively, duped to the current one to hunt for information about how to reproduce them.

We use GitLab to manage software on interconnected embedded systems. What often comes up is this: New functionality on one system changes the protocol in a slightly incompatible way. Software on other systems have to be updated to understand the new protocol, take advantage of the new functionality, and stop complaining about the unexpected data. For this I would create multiple issues: Issues for the new functionality that we need. (Project A) Issue for defining the protocol changes. (Project A) Issue for implementing the protocol changes on the module. (Project A) Issues in related software projects for implementing the changes required to understand the new protocol. (Project B, C, D...)

I'm not sure that isolating design is something I'd prefer. I'd rather have an issue tagged (labeled) as such, and then attach design artifacts. I start a design in the same way I start frontend, with a list of requirements and acceptance criteria in mind, the design is just an artifact, a deliverable, an asset.

I feel we need a agreeable definition of work-items. It is getting confusing already. If the goal is to avoid confusion then exceptions must be avoided.

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.

Additionally, it reiterates the need to define "What isn't a Work Item?"

but from previous experiences like this, the feature set has to be robust at the start or I think adoption will suffer.

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.

序 前言 數盲，其實普遍存在於生活之中 　　「數學向來是我最爛的一科。」 　　「100萬美元、10億美元、1兆美元，隨便。只要我們可以解決這件事，多少錢都不是問題。」 　　「我和傑瑞不能去歐洲了，都是恐怖分子害的。」 　　數盲，是指沒有能力自在地應對和數字以及機率有關的基本概念。這項缺點讓太多在其他方面博學多聞的人受了很多苦。這些人會因為別人混用「隱含」和「推斷」而感到苦惱，但看到數字上出現錯誤與矛盾，就算是嚴重失當，回應時也絲毫不見尷尬。我還記得，有一次在派對上聽到一個人侃侃而談「繼續」和「持續」有什麼差別，當晚稍後我們看新聞報導，氣象播報員說星期六的下雨機率是50％，星期天也是50％，結論是那個週末下雨的機率是百分之百。那位自封文法家的先生覺得這話很對，就連我向他解釋錯在哪裡之後，他也沒什麼表示。但如果天氣播報員的語法錯誤，他可能會比較火大。人常會隱藏其他缺點，但數學不好這件事不一樣，多半都是明目張膽表現出來：「我連平衡收支帳都做不到。」「我這個人關心的是人，我不關心數字。」或者「我向來痛恨數學。」 　　人們會洋洋得意於自己對數學很無知，部分原因是數學不好造成的後果，不像其他缺點這麼明顯。基於這一點，再加上我堅信人對於用具體範例來說明更有反應，對於一般性的描述比較無感。因此，本書會檢視許多真實世界裡的數盲範例，包含股票詐騙、擇偶、報紙專欄上的占卜師、飲食和醫療主張、恐怖主義的風險、占星、運動賽事數據、選舉、性別歧視、幽浮、保險和法律、心理分析、超心理學、樂透以及藥物試驗等等。 　　我努力避免太自以為是的言論，也不要用哲學家艾倫．布魯姆（Allan Bloom）式的批判，來泛論流行文化或是教育系統，但我還是提出了一些通論式的評論與觀察，但願我舉的例子能支持我的論點。我的看法是，有些人無法游刃有餘地面對數字和機率，是源於對不確定性、巧合或問題呈現方式的自然心理反應。或者是，出於焦慮，或是對數學的本質和意義懷抱不切實際的誤解。 　　數盲會造成一種罕有人討論的後果：數盲和相信偽科學有關。本書會討論兩者之間的交互關係。在現代這個社會，每天都會出現基因工程、雷射科技、積體電路等新科技，讓我們更進一步理解這個世界。但有很多成人仍相信塔羅牌、通靈和水晶的力量，特別讓人難過。 　　更不妙的是，科學家對於各種風險的評估，和一般人對於這些風險的認知大不相同，兩者間的落差最後要不就引發沒有根據、但殺傷力極大的焦慮，要不就導致人們要求得到根本做不到、而且會癱瘓經濟的無風險保證。政治人物在這方面幫不上忙，因為他們的工作就是處理公眾的意見，因此不樂於說清楚可能會造成哪些危險，以及有哪些相應的取捨，但這是幾乎所有政策要面對的問題。 　　本書大部分談的是各種不當，比方說沒有數字觀點、過度重視無意義的巧合、輕信偽科學、無能識別社會中的各項取捨等等，寫來很有破解流言的意味。但我希望我有避開很多人這麼做時，都會露出的過度激昂和譴責語氣。 　　本書盡量用溫和可讀的方式來談數學，只採用一些基本的機率和統計概念。雖然某種程度上來說有一點深，但只需要具備常識與一些演算能力即可領會。而我也會分享一些概念，是過往很少用淺顯易懂的方式來討論的。我的學生多半很喜歡這些內容，但他們也常會問：「考試時會考這個嗎？」讀這本書不用考試，所以讀者可以好好享受，偶爾一些比較困難的段落，跳過也沒問題。 　　本書的主張之一，是數盲會基於個人經驗、或因為媒體側重個別性與戲劇性效果，而受到誤導，有強烈的對人不對事傾向。但這句話不代表數學家就不帶個人情感、或是一板一眼，我就不是，這本書也不是。我寫這本書的訴求對象，是受過教育但是數盲的人。或者，至少是對數學還沒有怕到死，不會看到數學兩字就癱軟的人。如果能因此講清楚數盲在我們的公、私生活中有多麼普遍，寫這本書就值得了。

For consumers, the equivalent of "build or buy" could be called "ads or nerds". "Ads" meaning ad-supported services, like consumer Gmail or Facebook. "Nerds" meaning hobbyist services based on free software and commodity hardware.

the SoNeC approach could potentiallybring about results related to these areas, but not limited to these

With all the solar panels in the world linked up, the daylight side of the planet could power the night side ad infinitum, Ingels suggested.

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.

because the value isn't there yet. A promise is just a marker that it will be available at some point in the future. You cannot convert asynchronous code to synchronous, though. If you order a pizza, you get a receipt that tells you that you will have a pizza at some point in the future. You cannot treat that receipt as the pizza itself, though. When you get your number called you can "resolve" that receipt to a pizza. But what you're describing is trying to eat the receipt.

Rupert Read has the best idea I have heard re international climate negotiations: countries that are serious should have their own conference where they collaborate on strong targets, plans, etc. Part of which should be recognising the dangers of remaining reliant on the petrostates, planning to transcend that reliance and sanctioning them

Modern cars, however, use a single stick that pivots around among the gears. It's designed in such a way that, on a modern stick-shift car, it is not possible to engage two gears at the same time.

there are good stories and bad stories uh good stories I mean this is very on a very very simplistic level but good stories 00:13:23 benefit people and bad stories can create you know Wars and genocides and and the most terrible crimes in history were committed in the name of some fictional story people believed very few 00:13:38 Wars in history are about objective material things people think that we fight like wolves or chimpanzees over food and territory this is not the case 00:13:52 at least not in the modern world if I look for instance at my country which is at present in at War the Israeli Palestinian conflict is not really about food and territory there is enough food 00:14:04 between the Jordan and Mediterranean to feed everybody there is enough territory to build houses and schools for everybody but you have two conflicting stories or more than two conflicting 00:14:17 stories in the minds of different people and they can't agree on the story they can't find a common story that everybody would be happy with and this is the the Deep source of the conflict

A personalized button gives users a quick indication of the session status, both on Google's side and on your website, before they click the button. This is especially helpful to end users who visit your website only occasionally. They may forget whether an account has been created or not, and in which way. A personalized button reminds them that Sign In With Google has been used before. Thus, it helps to prevent unnecessary duplicate account creation on your website.

Warning: Do not accept plain user IDs, such as those you can get with the GoogleUser.getId() method, on your backend server. A modified client application can send arbitrary user IDs to your server to impersonate users, so you must instead use verifiable ID tokens to securely get the user IDs of signed-in users on the server side.

If I wanted to integrate this with an existing login system, “signing out” would mean signing out of my own application (and not out of my Google account).

A personalized button reminds end users that they have used Sign in with Google before, and thus helps to prevent unnecessary duplicate account creation on your website. This is especially helpful to end users who visit your website only occasionally. They may forget the login methods they used.

This is a shell script that essentially does the same as the flaky test: #!/bin/sh cat <<EOS > m.rb module M sleep 0.5 def self.works? true end end EOS ruby -I. <<EOS autoload :M, "m" t = Thread.new { M } p M.works? EOS rm m.rb

there's an interesting book by Seth Klein Naomi Klein's brother the 00:56:39 just for about creating a mobilizing federal government provincial um almost a state of emergency to address 00:56:53 climate change uh and and that would if you had extraordinary powers then you could basically say well electric vehicles and 00:57:04 more cars is not the solution and we're gonna go in a different area we're going to secure for example the water supply we're going to secure the air supply 00:57:16 we're going to reduce emissions in a very structured way

One more example of a simple approach to this that might help a lot too is add a PORO generator. It could be incredibly basic - rails g poro MyClass yields class MyClass end But by doing that and landing the file in the app/models directory, it would make it clear that was the intended location instead of lib.

I think the real question then becomes: Where do Ruby classes, who I can't find a meaningful folder in app

lib/ is intended to be for non-app specific library code that just happens to live in the app for now (usually pending extraction into open source or whatever).

Everything has a place so do better and find it. There is a certain belief that everything within app should be organized into functionally-named directories and any files placed in app/lib actually belongs in app/services or app/interactors or app/models or someplace if the developers just tried harder. The implication is that developers are bad developers if they don’t yet know what kind of constant they have and where its forever home should be. I reject this. Over the lifespan of an application, there will be constants that have not yet found their functional kin, if those kin ever come to exist at all; sometimes you simply need some code and a place to put it. app/lib can be the convention for where those constants can live temporarily or as long as necessary. Autoloading is really nice, let’s treat them to it.

It is confusing that app/lib is named similarly to lib . I agree, but it is not uncommon to have directories with the same name and similar function nested under different contexts. I believe developers can handle this complexity. Most similarly, Linux has lib and usr/lib . Within a new Rails app, there are many such directories that are manageable: app/assets and lib/assets (sometimes even vendor/assets too) app/javascript and vendor/javascript storage and tmp/storage config and app/assets/config app/controllers and app/javascript/controllers