TheCalculagraph

He filled the library at Vivarium with texts onthese subjects and transformed the production of manuscripts in hisscriptorium by developing proper standards and methods forcopying. As one of the few notable scholars of his period,Cassiodorus played a vital role in the survival of classical culture inItaly, saving books from the smoking ruins of Roman libraries,preserving and reproducing them

Before the Xerox machine, this was a labour-intensive counsel of perfection; and it is no wonder that many of the great 19th-century historians employed professional copyists.

If a passage is interesting from several different points of view, then it should be copied out several times on different slips.

Instead read this gems brief source code completely before use OR copy the code straight into your codebase.

You would take a Didion sentence like 'Only the very young and the very old may recount their dreams at breakfast, dwell upon self, interrupt with memories of beach picnics and favorite Liberty lawn dresses and the rainbow trout in a creek near Colorado Springs,' and learn how to see it as "Only the ____ and the ____ may ____, ____, ____ and ____." A reusable format for pointing out similarities between two distinct things.

Great writers become great by closely studying and copying other great writers. This is how cultural knowledge works. We learn the foundational skills from each other first, and then get all weird and experimental later on once the normal rules become boring.

I used to think copying was unseemly before one of my writing professors in college filled me in on the big, unkept secret. He handed us a small trove of writing samples from folks like Joan Didion, John McPhee, Barbara Kingsolver, and Ernest Hemingway. Essentially a Who's Who of New Yorker essayists. We had to copy out their work, then write our own pieces using the copied sentences as 'templates.'

Also cross-compatibility with mail clients can be hairy, so you should see what the industry experts are doing.

Now if you think about it, PJAX sounds a lot like Turbolinks. They both use JS to fetch server-rendered HTML and put it into the DOM. They both do caching and manage the forward and back buttons. It's almost as if the Rails team took a technique developed elsewhere and just rebranded it.

There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.

http://facebook.github.io/jsx/#why-not-template-literals (respectfully disagree)

Svelte chooses a reverse approach.

I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.

While react hooks were one of the catalysts for v3 we don't agree with with the APIs or the model and won't be emulating it.

both copied much of their API from Redux Form, so, despite working very differently under the hood, there is a lot of overlap in their APIs.

If you’ve used Flow before, the syntax is fairly similar. One difference is that we’ve added a few restrictions to avoid code that might appear ambiguous.

For context, the previous API had a lazy promise. Currently I’m thinking we could just return a closure like in the React API

This is the same as useEffect in React, incidentally — the function must be synchronous in order to avoid race conditions.

The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.

Does it look like a decorator plugin in Ractive, right

The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)

Studying the masters will help you understand how all copywriting elements fit together.

one that would borrow the best features from the ABC language