as with any social group that is a power law curve meaning for instance eighty percent of Trump supporters will change their view if they're listened to consistently maybe 19% are going to be resistant and need a good few conversations for them to at least have doubts and 1% are frankly psychopathic and they're never gonna change

require require('file_path') でluaファイルをモジュールとして読み込みます。Neovimの runtimepath ディレクトリ内の lua ディレクトリに格納されているLuaファイルを require で読み込めます。 例 init.vim lua require('plugins') ~/.config/nvim/lua/plugins/init.lua を読み込みます。 lua require('plugins.completion') ~/.config/nvim/lua/plugins/completion.lua を読み込みます。 lua require('plugins/completion') . or / どっちでもOKです。 . のほうがよく見ます。

Web3 is best under­stood as a game, or a game of games. I don’t intend that as a dig: it’s a really good game! Vast and open-ended, deeply social, with lots of scores to tally … AND you can win real money?? I mean, that’s terrific.

This message was emailed to the Media Lab committee. The assumed audience is subscribers who know roughly what Web3 is supposed to be, but aren’t sure what to think about it. (Here’s more about assumed audiences.)

lit­tle plac­ards up top mak­ing it clear they are aimed at dif­fer­ent groups of read­ers. Those groups might overlap! They might also: not.

the way they push back against the “context collapse” of the internet, in which every pub­lic post is, by default, addressed to everyone.

or email me at “j@thisdomain”

Because Jamstack projects don’t rely on server-side code, they can be distributed instead of living on a single server. Serving directly from a CDN unlocks speeds and performance that can’t be beat. The more of your app you can push to the edge, the better the user experience.

You can either use require to bypass typescript special import.

const TsconfigPathsPlugin = require('tsconfig-paths-webpack-plugin')

Leverages hash-based routing, which is optimal for SPAs and doesn't require any server-side processing

Many 3rd parties has some magic parameter which blocks the cookie, but doesn't block the functionality of the element, and I'm looking for something like that. For example brightcove player has a data attribute. Video is working, cookies are not set.

In the future, these attributes may expand without the API being versioned. The current attributes are:

PR has tests / docs demo, and is linted.

Thank you, I put the restaurant_params both in def new & def create but only need it in the def create