I've found that a lot of um Pioneers who have had brilliant ideas and have fought through and you know sort of um uh spent a lot of energy in their life pushing 00:42:00 some someone with some new idea those people are often the most resistant to other new ideas it's amazing

Instance methods Instances of Models are documents. Documents have many of their own built-in instance methods. We may also define our own custom document instance methods. // define a schema const animalSchema = new Schema({ name: String, type: String }, { // Assign a function to the "methods" object of our animalSchema through schema options. // By following this approach, there is no need to create a separate TS type to define the type of the instance functions. methods: { findSimilarTypes(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); } } }); // Or, assign a function to the "methods" object of our animalSchema animalSchema.methods.findSimilarTypes = function(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); }; Now all of our animal instances have a findSimilarTypes method available to them. const Animal = mongoose.model('Animal', animalSchema); const dog = new Animal({ type: 'dog' }); dog.findSimilarTypes((err, dogs) => { console.log(dogs); // woof }); Overwriting a default mongoose document method may lead to unpredictable results. See this for more details. The example above uses the Schema.methods object directly to save an instance method. You can also use the Schema.method() helper as described here. Do not declare methods using ES6 arrow functions (=>). Arrow functions explicitly prevent binding this, so your method will not have access to the document and the above examples will not work.

I'm rather concerned about adding svelte.config.js support to things that already have well established mechanisms for configuration.

Note that you can address this by creating signal handlers in Bash to actually do the forwarding, and returning a proper exit code. On the other hand that's more work, whereas adding Tini is a few lines in your Dockerfile.

The energy sector contains a large number of long‐lived and capital‐intensive assets. Urban infrastructure, pipelines, refineries, coal‐fired power plants, heavy industrial facilities, buildings and large hydro power plants can have technical and economic lifetimes of well over 50 years. If today’s energy infrastructure was to be operated until the end of the typical lifetime in a manner similar to the past, we estimate that this would lead to cumulative energy‐related and industrial process CO2 emissions between 2020 and 2050 of just under 650 Gt CO2. This is around 30% more than the remaining total CO2 budget consistent with limiting global warming to 1.5 °C with a 50% probability (see Chapter 2)

I'd love something similar to automatically crawl and index every site I visit. I'm forever losing stuff. I know I saw it but I can't remember where. reply parent chillpenguin () 1 hour ago on I use BrowserParrot for this. Works really well.https://www.browserparrot.com/ reply parent thinkmassive () 2 hours ago on ArchiveBox documents how to automatically archive links from your browser history:https://github.com/ArchiveBox/ArchiveBox/wiki/Usage#Import-l... reply parent mttjj () 5 hours ago on This is Mac only and I have no affiliation other than I like this developer but your request reminded me that he just launched this app: https://andadinosaur.com/launch-history-book reply parent akrymski () 1 hour ago on I use Google for this. It's really annoyingly good at finding previously visited pages. reply parent asselinpaul () 3 hours ago on https://heyday.xyz comes to mind reply parent fudged71 () 2 hours ago on Vortimo

Its good to know how to implement it. I would prefer to use a gem myself.

The VTE widget was originally designed as the back-end for Gnome Terminal but was fortunately designed as a GTK widget so that other terminal emulator applications could leverage it instead of rolling their own. Many popular Linux terminal emulators use this component.

curl -o ~/.config/direnv/helpers.sh

In fact, npm is not trying to reinvent the wheel. You can find similarities between all three Workspace implementations.

Rather than write new tooling we decided to take advantage of tooling we had in place for our unit tests. Our unit tests already used FactoryBot, a test data generation library, for building up test datasets for a variety of test scenarios. Plus, we had already built up a nice suite of helpers that we coud re-use. By using tools and libraries already a part of the backend technology’s ecosystem we were able to spend less time building additional tooling. We had less code to maintain because of this and more time to work on solving our customer’s pain points.

Note: as for setting boolean variables: not only are true/false and 0/1 acceptable values, but also T/F and on/off. Thanks, coercible!

But in all this incongruous abundance you'll certanly find the links to expect It's just what is wanted: the tool, which is traditionally used to communicate automatically with interactive programs. And as it always occurs, there is unfortunately a little fault in it: expect needs the programming language TCL to be present. Nevertheless if it doesn't discourage you to install and learn one more, though very powerful language, then you can stop your search, because expect and TCL with or without TK have everything and even more for you to write scripts.

Reopening #162

Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution

The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false or nil.

My reasoning for not gemifying ActiveForm is that the custom not-rails-core logic is relatively small

I've utilized as many Rails modules as I can to make maintenance a lot easier as I just have to update Rails and I get the updates for free. By utilizing Rails core modules, it's a really small library - there are only 10 methods in the Base module!

I'd like to know specifically what you were aiming to achieve with this Gem as opposed to simply using https://github.com/apotonick/reform? I am happy to help contribute, but equally if there is a gem out there that already does the job well, I'd like to know why we shouldn't just use that.

I have checked the following close stackoverflow sources : Relation passed to #or must be structurally compatible. Incompatible values: [:references]

well... it's the same question

I've only done components that need to/can be Svelte-ified. For some things, like RTL and layout grid, you can just use the MDC packages.

This is Sass based, and therefore doesn't require Svelte components

hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.

It causes some implementation complexity just by existing.

Hooks embrace JavaScript closures and avoid introducing React-specific APIs where JavaScript already provides a solution.

Templates are prone to unnoticed runtime errors, are hard to test, and are not easy to restructure or decompose.

In contrast, Javascript-made templates can be organised into components with nicely decomposed and DRY code that is more reusable and testable.

In contrast, React apps shun templates and require the developer to create their DOM in Javascript, typically aided with JSX.

It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.

Links are just <a> elements, rather than framework-specific <Link> components. That means, for example, that this link right here, despite being inside a blob of markdown, works with the router as you'd expect

As you can see, it uses Javascript label syntax to tell the compiler where recalculation should be carefully managed. And you thought that no one uses labels any more.

You can construct both by setting other properties inside the Promise callbacks, but we have {#await} and I feel like it should be used for this, instead of special casing the logic every time.

In a similar vein to (#33), it is arguably just something that compensates for the lack of power in the template language relative to JavaScript.

Yes, we use CSS. I thought a Svelte mantra was to use the existing language(s). This is fundamental CSS

The complaint is that by choosing less powerful languages, template-based frameworks are then forced to reintroduce uncanny-valley versions of those constructs in order to add back in missing functionality, thereby increasing the mount of stuff people have to learn.

In general, I'm unpersuaded by these arguments (learning curve is determined not just by unfamiliar syntax, but by unfamiliar semantics and APIs as well, and the frameworks in question excel at adding complexity in those areas).

One of the arguments that's frequently deployed in favour of JSX-based frameworks over template-based ones is that JSX allows you to use existing language constructs:

Suffering

Any top-level statement (i.e. not inside a block or a function) can be made reactive by prefixing it with the $: JS label syntax.

If you've found a problem in Ruby on Rails which is not a security risk, do a search on GitHub under Issues in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to open a new one.

It's funny that in such a complex gem like this, there's only one open issue, exactly about what I came here to post.

I'd say that "dump" in the CS sense, both as noun and verb, is merely another application of its preexisting meanings even without the vulgar one, particularly the ones related to unloading/releasing contents. (For example, "dump truck".)

For some geeky reason, the computer programming world has long maintained a tradition of using words in new ways, with a studied obliviousness to their prior, rude meanings: for example, 'dump'. 'Falsey' is merely another word in this long, and quite useful, tradition.

ike I said, using the trading view chart is the best thing that you guys could have done. It's not, you know, like I said, don't, don't reinvent the wheel. It's already perfectly round. This one works great.

But I'm also not looking at necessarily reinvent the wheel, but the tools are offering specific applications, do a really good job at what they do.

Um, instead of building it from scratch cause they've done a good job and I believe that have a easier enough api to pull in, uh, those tools into your own