exc:compose1 prov:qualifiedUsage [ a prov:Usage ; prov:entity exg:dataset1 ; prov:hadRole exc:dataToCompose ] .

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

I would put creativity into three buckets. If we define creativity as coming up with something novel or new for a purpose, then I think what AI systems are quite good at the moment is interpolation and extrapolation.

This standardized routine is known as the creative process, and itoperates according to timeless principles that can be foundthroughout history.

Amie Fairs, who studies language at Aix-Marseille University in France, is a self-proclaimed Open Knowledge Maps enthusiast. “One particularly nice thing about Open Knowledge Maps is that you can search very broad topics, like ‘language production’, and it can group papers into themes you may not have considered,” Fairs says. For example, when she searched for ‘phonological brain regions’ — the areas of the brain that process sound and meaning — Open Knowledge Maps suggested a subfield of research about age-related differences in processing. “I hadn’t considered looking in the ageing literature for information about this before, but now I will,” she says.

The DICER1 syndrome is an autosomal dominant tumor‐predisposi-tion disorder associated with pleuropulmonary blastoma, a rare pediatric lung cancer

Together: responsive, inline “autocomplete” pow­ered by an RNN trained on a cor­pus of old sci-fi stories.

Jean Paul invented a similar system and called it Witz. Like Tesauro, Jean Paul considered that the matter was to cede a prearranged ge-ography of places where everything had its own seat but was also compelled to remain in its own seat without possible deviation. The dismantlement of this architecture was required to change the rhetorical invention--that is, the retrieval of what is already known but has been forgotten--into an invention in the modern, scientific sense of the term.73 Also similar to Tesauro, accord-ing to Jean Paul, such an invention or discovery could occur only through the jumbled recording of notes taken from readings (or, from personal reflections) and retrievable by means of a subject index. By searching and recombining, the compiler would have put into practice the chance principle on which the whole knowledge storage mechanism was based; he would have likely discov-ered similarities and connections between remote items that he would have otherwise overlooked.

I pulled out my keyboard

Hobbes and Rousseau told their contemporaries things that werestartling, profound and opened new doors of the imagination. Nowtheir ideas are just tired common sense. There’s nothing in them thatjustifies the continued simplification of human affairs. If socialscientists today continue to reduce past generations to simplistic,two-dimensional caricatures, it is not so much to show us anythingoriginal, but just because they feel that’s what social scientists areexpected to do so as to appear ‘scientific’. The actual result is toimpoverish history – and as a consequence, to impoverish our senseof possibility.

Every serious (academic) historical work includes a conversation with other scholarship, and this has largely carried over into popular historical writing.

You do not configure Zeitwerk manually in a Rails application. Rather, you configure the application using the portable configuration points explained in this guide, and Rails translates that to Zeitwerk on your behalf.

great minds think alike (fools seldom differ)

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.

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

HTTP REST seems like an "out of external dependency" way to go.

The idea is to avoid additional dependency if it's possible.

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.

Unit tests are usually cheap, and you should consider them like the basement of your house

Only test the happy path, but make sure to add a test case for any regression that couldn’t have been caught at lower levels with better tests (for example, if a regression is found, regression tests should be added at the lowest level possible).

This style of testing is used to exercise one piece of code with a comprehensive range of inputs. By specifying the test case once, alongside a table of inputs and the expected output for each, your tests can be made easier to read and more compact.

“Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).

Meh... as I said earlier, I think using Webpack is the recommended way now. Another issue is there is no way to generate source maps in production.

Cross-posted to https://stackoverflow.com/questions/58632880/error-while-fetching-an-original-source-in-new-rails-app-sprockets-4-firefox, in hopes of reaching more people.

It is based on the idea that each validation is encapsulated by a simple, stateless predicate that receives some input and returns either true or false.

Since we're not passing any inputs to ListAccounts, it makes sense to use .run! instead of .run. If it failed, that would mean we probably messed up writing the interaction.

As a workaround, I guess I'll have to disable my strict CSP in development, but I'd prefer to keep it strict in development as well so that I ran into any CSP issues sooner...

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.

My focus is on make the API as simpler as possible to allows easy integration without even reading the docs but keeping and expand current features.

@monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see

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

I can't add special props and keywords to every single component I have and will ever create for this to work.

Explicitly exposing any attributes that might get overridden by a parent seems impractical to me.

There's no way to change style incapsulation method without patching the compiler, and this means maintaing a fork, which is not desirable.

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.

They don't need to add a prop for every action. The action itself can be passed in as a prop. <script> export let action; </script> <div use:action>whatever</div> The argument for the action can be another prop or can be part of the same prop.

It took only a couple decades for the internet to transform from a weird underground hobby to an entirely new medium for the self. One of the earliest draws of internet society was the invitation to become someone else — to obscure the dull strains of your real life behind a veil of mysterious text or behind an avatar, the image or persona you create to represent you online. In those days, it often seemed like people had collectively assented to participate in some degree of fiction about one another. The person on your forum or in your channel who loved to say inflammatory things was just some troll; you could even assume that he wasn’t like that in real life. That these were only mechanisms specific to the character he lived as online.

When submitting new methods for consideration, it is best if each method (or tightly related set of methods) is in it's own pull request. If you have only one method to submit then a simple commit will do the trick. If you have more than one it best to use separate branches. Let me emphasizes this point because it makes it much more likely that your pull request will be merged. If you submit a bunch of methods in a single pull request, it is very likely that it will not be merged even if methods you submitted are accepted!

We do the smallest thing possible and get it out as quickly as possible.

“The broader issue is clearing space for your transit to get through congestion, and most of that congestion is from private cars, not [ride-hail],” says Ben Fried, the group’s communications head. “Cities need to make transit fast, affordable, convenient." Truly attractive transit has to do that better than private cars.

Are there, in other words, any fundamental "contradictions" in human life that cannot be resolved in the context of modern liberalism, that would be resolvable by an alternative political-economic structure?

PRP PAINTING

MARUCHAN, INC.

GATEWAY PACIFIC CONTRACTORS INC.

The four general lines of argument are: (1) The Possible and Impossible; (2) Fact Past; (3) Fact Future; (4) Degree.