We would not have it again. Sometimes we think of the nations lying asleep, Curled blindly in impenetrable sorrow, And then the thought confounds us with its strangeness. The tractors lie about our fields; at evening

ISO 8601 specifies the use of uppercase letter T to separate the date and time. PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems.

but Government, even in its best state, is but a necessary evil…

As a result, hisindex is simultaneously a relic of research and a reminder of the pitfalls of all such effortsto create systematic knowledge, regardless of the underlying technology – paper, digitalor otherwise.

Beyond the realm of historians, advocates called card indexes ‘the only portable,elastic, simple, orderly and self-indexing way of keeping records’, and the practice wascommon enough that Gustave Flaubert parodied the unending and ultimately futilepursuit of all knowledge in his 1881 satire Bouvard et Pe ́cuchet (Dickinson, 1894).

In the building is an altar to all the gods in common. Now return back again to the Altis opposite the Leonidaeum.

the first things that I think is important to understand from our perspective we've been taught Through the Ages that every life form on the face of the planet has its proper place as divinely ordained by our Almighty 00:31:03 Creator when one looks to the human body and the complexities every so has an importance and Chief Seattle taught us that all things are connected what we do 00:31:15 to the Earth we do to ourselves we are but one strand in a very complex Web of Life and our ancestors also foretold of a Day of Reckoning and we are in that 00:31:27 Day of Reckoning right now

there are some sources of energy which  which create a negative value because of   00:48:39 of of global climate change and climate working  and warming and you know all the negative   external effect of using some energy so we have  some to make some of the energy uh sources just   illegal you know we have to keep some of the oil  in the ground we have to stop looking for new oil   and gas so you know so the solution to some of  the of the energy questions we have is just to to   00:49:04 to make illegal you know the use of certain energy  and to to to move to other energy so that's part   of the answer now if we if we have done that  and we deal with with energy that don't have the   the negative this much bigger negative impact  on mankind than their positive productive impact   then you know redistribution of wealth must be  about all forms of wealth you know whether it's   00:49:32 rent or energy or financial assets or i  was seeing you know we we need to have a   permanent circulation of wealth and power so you  know that's the way i i view you know taxation of   wealth is will be a permanent you know progressive  tax on net wealth which in effect will will will   wipe out all the biggest uh wealth right away you  know say up to 90 percent tax per year for you   00:49:59 know for for billionaires but among you know there  will still be some people who want 100 000 dollars   some people who earn 1 million or 2 million but  there will be a permanent circulation of wealth   holdings within within this limited uh wealth  gap that that will still exist and this should   be for all forms of wealth you know whether it's  land or housing or whatever whatever the origin

to get rid   of monopoly rent you have to return basic key  uh infrastructure to the public domain where   it was before 1980 so that uh basic needs can be  supplied at low prices not uh creating monopoly   for uh the one percent uh and i guess i'm saying  you have to realize that finance has used as well   00:25:12 to take over the economy and this has to  be reversed uh because uh once you have   uh wealth taking the form of uh claims uh  loans and claims on other people's debt   we'll count you up compound interest any rate of  interest is a doubling time and compound interest   is always going to grow faster than the economy's  real growth and the only way to prevent this isn't   00:25:37 simply to lower the interest rate which you've  done today 0.1 uh the only solution is to wipe out   the overall debts that are stopping economic  growth and these debts are the savings of the   one percent the good thing about cancelling debts  is you cancel the savings of the one percent   and as long as you leave these savings in  place there's not going to be a solution

We will also run into some issues when we consider adding new channels to Service Desk like an API. We should have a streamlined process of rendering notes (messages) etc. Having a base64 image (or even attachment) in mail but not in the API might be inconsistent and also adds a lot of code that needs to be maintained.

The pencilled dots in the margin of many books in the Codrington Library at All Souls are certain evidence that A.L. Rowse was there before you.

opts = method(__method__).parameters.map(&:last).map { |p| [p, eval(p.to_s)] }.to_h SomeOtherObject.some_other_method(opts)

that's right, we don't want to do params = { ... } because then we're hardcoding the implementation and it becomes very coupled. The benefit of doing it like in my examples is that you can change the method signature and still automatically capture all keyword parameters.

and then the deepest level is what's maybe more relevant for our discussion 00:27:04 we call it we call it all pervasive it's a conditioned kind of suffering and it's conditioned by ignorance the ignorance that does not understand reality correctly okay and that's really 00:27:17 what we're that's the opposite of what we're talking about when we talk about you know shunyata or emptiness uh this ignorance is 100 180 degrees opposite um so in that last level of suffering is 00:27:32 really the underpinnings of all the other sufferings okay so if we can address and remove that level of ignorance then all the other sufferings fall away 00:27:43 and you could also see it as all of our attachments that get us into trouble our aversions that can end in anger hatred and now we see so much violence in the world all that and 00:27:55 and our selfishness and our greed and you know on and on all that just falls away when we begin to get rid of this ignorance and we begin to not only intellectually understand emptiness but 00:28:08 we put it into our lives it percolates down and it starts to be part of our attitude the way we think the way we feel it permeates every aspect of our sleep and wake life and when that happens it's 00:28:22 it's like a revolution i don't speak from personal experience because i don't have that but according to the great saints and masters who have it's like a total revolution it's full of joy it's complete love and compassion 00:28:36 there's no moment where there isn't and it's always bathed in this wisdom of emptiness taking things as you said so beautifully in the beginning of your remarks carlo that everything is 00:28:48 in relation there are no discrete entities at all there's no independent existence i think those are the words that were used by david bohm who was a very close friend of his holiest the dalai lamas and as 00:29:01 you know a well-recognized quantum physicist um so those are just some contextual opening remarks to put us in in the in the right ball field if you will uh as a 00:29:15 with an american background baseball field right could be a soccer field

I think RSpec should provide around(:context)/around(:all). Not because of any particular use case, but simply for API consistency. It's much simpler to tell users "there are 3 kinds of hooks (before, after and around) and each can be used with any of 3 scopes (example, context and suite)". Having some kinds of hooks work with only some kinds of scopes makes the API inconsistent and forces us to add special case code to emit warnings and also write extra documentation for this fact.

Organizations as varied as Y Combinator, MIT’s Radiation Lab, and ARPA have astonishing track records in catalyzing progress far beyond their confines.

Easy Star All-Stars

today I'm here to describe that everything really is connected, 00:02:02 and not in some abstract, esoteric way but in a very concrete, direct, understandable way. And I am going to do that with three different stories: a story of the heart, a story of the breath, and a story of the mind.

Of course, we can always add more special cases to the type system to detect the specific case of iterating over a known-bounded object literal, but this just leads to the "Why does this code not behave like this other nearly-identical code?" problem when we fail to properly exhaust all the special cases.

or maybe it was how he used fire 15 to describe the trees.

You can help make Node.js and browsers more unified. For example, Node.js has util.promisify, which is commonly used. I don’t understand why such an essential method is not also available in browsers. In turn, browsers have APIs that Node.js should have. For example, fetch, Web Streams (The Node.js stream module is awful), Web Crypto (I’ve heard rumors this one is coming), Websockets, etc.

Run the Rails server (bin/rails s) and the Webpack Dev Server (bin/webpack-dev-server) via your preferred method. Two terminal tabs will work or create a Procfile and run via overmind or foreman.

Epics can contain both issues and epics as children

It also makes your code harder to follower because you are using SCREAMING_SNAKE_CASE instead of nice, readable methods.

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.

All The People

With every other change I make, I have to test in a dozen clients and make sure it looks fine. Why is there so much variation in email style implementation amongst different clients?

I've worked with people at companies where this was their only responsibility. Setting up emails for clients, making sure they pass a battery of tests and look great in all browsers and clients. It's an incredible PITA and it's not a set it and forget it thing. Clients can change month to month; spam filters change, etc...

STREAMS originated in Version 8 Research Unix, as Streams (not capitalized).

Valleyspeak

I think the issues/problems specified in the comments are not present with a Hash-only implementation. :) I would be supportive of re-considering this feature just for use with a Hash, where I believe 80% of the real-life use cases would (and do) exist. I have encountered this need before in the wild, but not with Arrays.

It would be very nice if that was consistent across every application.

Trying to force this one thing to work for everyone is the worst way to do that.

The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.

I would much rather have a "cosine" module than a "trigonometry" module because chances are good I only need a small fraction of the utilities provided by the larger trig module.

Second, I don't agree that there are too many small modules. In fact, I wish every common function existed as its own module. Even the maintainers of utility libraries like Underscore and Lodash have realized the benefits of modularity and allowed you to install individual utilities from their library as separate modules. From where I sit that seems like a smart move. Why should I import the entirety of Underscore just to use one function? Instead I'd rather see more "function suites" where a bunch of utilities are all published separately but under a namespace or some kind of common name prefix to make them easier to find. The way Underscore and Lodash have approached this issue is perfect. It gives consumers of their packages options and flexibility while still letting people like Dave import the whole entire library if that's what they really want to do.

Onceability can be the result of the exaggerated demand for un-memorable passwords.

I'd suggest there ought to be config to disable source maps specifically, and specifically for either CSS or JS (not alwasy both), without turning off debug mode. As you note, debug mode does all sorts of different things that you might want with or without source maps.

There's not a way to do it at the moment without enabling all debug features.

Notice that the HTML elements (BUTTON, DIV, etc.) are in CAPS. We know this is bending the standard Ruby style rules slightly, but we think it reads better this way.

Knowing what your elements are lets browsers use sensible defaults for how they should look and behave. This means you have less customization work to do and are more likely to get consistent results in different browsers.

Dafa ànd ak moroom yi àll ba, fori aloom.

If set to true the UI of all input widgets (number, time, month, date, range) are replaced in all browsers (also in browser, which have implemented these types). This is useful, if you want to style the UI in all browsers.

not all answers pass this tests

This is where all our learnings about semantics, outputs, signals and the DSL come together.

step :direct_debit

This connects the failure output to the previous task, which might create an infinity loop and waste your computing time - it is solely here for demonstrational purposes.

Please note that I/O works for both “simple” tasks as well as nested activities.

Yes, we could and should use Reform or Dry-validation here.

Write special-case classes. For example, you will have User base class with multiple error-subclasses like UserNotFound(User) and MissingUser(User). It might be used for some specific situations, like AnonymousUser in django, but it is not possible to wrap all your possible errors in special-case classes. It will require too much work from a developer. And over-complicate your domain model.

No one has requested it before so it's certainly not something we're planning to add.

To give a little more context, structures like this often come up in my work when dealing with NoSQL datastores, especially ones that rely heavily on JSON, like Firebase, where a records unique ID isn't part of the record itself, just a key that points to it. I think most Ruby/Rails projects tend towards use cases where these sort of datastores aren't appropriate/necessary, so it makes sense that this wouldn't come up as quickly as other structures.

This branch is 22 commits ahead, 207 commits behind newsapps:master.

However, sometimes actions can't be rolled back and it is unfortunately unavoidable. For example, consider when we send emails during the call to process. If we send before saving a record and that record fails to save what do we do? We can't unsend that email.

I typically save everything I can first, and then call the side-effects afterwards. If the side-effects fail I can handle them elsewhere and retry when necessary.

Group Rules from the Admins1NO POSTING LINKS INSIDE OF POST - FOR ANY REASONWe've seen way too many groups become a glorified classified ad & members don't like that. We don't want the quality of our group negatively impacted because of endless links everywhere. NO LINKS2NO POST FROM FAN PAGES / ARTICLES / VIDEO LINKSOur mission is to cultivate the highest quality content inside the group. If we allowed videos, fan page shares, & outside websites, our group would turn into spam fest. Original written content only3NO SELF PROMOTION, RECRUITING, OR DM SPAMMINGMembers love our group because it's SAFE. We are very strict on banning members who blatantly self promote their product or services in the group OR secretly private message members to recruit them.4NO POSTING OR UPLOADING VIDEOS OF ANY KINDTo protect the quality of our group & prevent members from being solicited products & services - we don't allow any videos because we can't monitor what's being said word for word. Written post only.

One lesser-appreciated user-behaviour is when a user would like to choose an alternative download location. On a download link, your user can right-click -> “save link as…” and place the download directly into a folder of their choice. Handy if you want something to go directly to removable media, for example. On a download button, there’s no such option.

If you want a reference to the global object that works in any context, you can read this from a directly-called function. const global = (function() {return this})();. This evaluates to window in the browser, self in a service worker and global in nodejs.

As was mentioned in the comments above, the material design spec for buttons specifies that the text should be uppercase, but you can easily override its CSS property: paper-button { text-transform: none; }

Choose sentence case or title case over uppercase. (This being said, Material Design does use buttons with uppercase labels.)

It took us a long time for everyone to get on the same page about the requirements spanning frameworks, tooling and native implementations. Only after pushing in various concrete directions did we get a full understanding of the requirements which this proposal aims to meet.

Note that you can also use dynamic partials, that conditionally select the partial to render based on the value in the JSON.

we update the validation schema on the fly (we had a similar case with a validation that needs to be included whenever some fetch operation was completed)

Library author here. I'm always fascinated by new ways people can invalidate my assumptions. I mean that in a sincerely positive way, as it results in learning.

What would happen if we get the list from a rest api when the form component is mounted? That's an interesting topic, you can add a rule once a component has been mounted and update the associated validation schema.

Ok, I have seen that there are lot of built-in and third party validations, but sooner or later I will face a validation rule not covered by this buffet. Can I build a custom one? Of course you can!

Well. I also recall that people complained about this when I did it in redux-form, which resulted in a persistentSubmitErrors config parameter.

How to fix nasty circular dependency issues once and for all

In the many projects I have maintained so far, sooner or later I always run into the same issue: circular module dependencies. Although there are many strategies and best practices on how to avoid circular dependencies. There is very little on how to fix them in a consistent and predictable way.

Why will you children insist on giving parties!”

You might think something like “don’t request the same resource thousands of times a day, especially when it explicitly tells you it should be considered fresh for 90 days” would be obvious, but unfortunately it seems not.

This isn’t to say that multiplying code is good or bad – it’s a characteristic of all code regardless of quality.

just saying that if you're going to try to go with a markup approach, at least go all the way, instead of the frankenstein that is JSX

I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.

But the vast majority of things that our apps are doing are just conditional and list rendering.

Always fascinated to discover a use case I'd never have considered.

But this is only a halfway decent way to clarify that this is an external dependency, because the only way to resolve a peer dependency warning is to install react from npm—there's no way to notify npm that you resolve the dependency to a browser global. So peer dependencies should be avoided in favor of external declarations. Then Rollup will take care of warning about "unresolved dependencies", even if external declarations can't express a particular version range with which your library is compatible like peer dependencies can.

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.

This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.

The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.

Your LazyLoad image is now inextensible. What if you want to add a class? Perhaps the author of LazyLoad thought of that and sets className onto the <img>. But will the author consider everything? Perhaps if we get {...state} attributes.

You'll have to create a new component that brings in the functionality of both. TooltipButton, TooltipLink, Link, and TooltipRoutedLink. We're starting to get a lot of components to handle a bit of added functionality.

For the tooltip example, if you had a whole bunch of tooltips on different elements, it would be annoying to have different event listeners and "should it be shown" variables for each one.

Perhaps at that point we're better off settling on a way to pass components through as parameters? <!-- App.html --> <Outer contents={Inner}/> <!-- Outer.html --> <div> <div>Something</div> <[contents] foo='bar'/> </div>

I would hope for it to come with React-like behavior where I could pass in a string (like div or a) and have it show up as a normal div/a element when the child component used it.

Use case: Wrapper components that need to render an element (e.g. because they attach event listeners). You'd probably use a <div> there by default but there may be places where this is not desirable for semantic reasons (e.g. in lists).

Maybe good for some cases but not a general solution for this I think.

const components = { Label, Tree, Menu };

The lack of spread continues to be a big pain for me, adding lots of difficult-to-maintain cruft in my components. Having to maintain a list of all possible attributes that I might ever need to pass through a component is causing me a lot of friction in my most composable components.

The code is short and simple, if you have specific needs you will probably be better off writing something custom for your application.

Original Instructions.

require 'minitest/autorun' class BugTest < Minitest::Test

"AOO is not, and isn't designed to be, the 'super coolest open source office suite with all the latest bells and whistles,'" Jagielski continued. "Our research shows that a 'basic,' functional office suite, which is streamlined with a 'simple' and uncluttered, uncomplicated UI, serves an incredible under-represented community.

If you can, use AMP like any other JavaScript library to build your site and forget about the canonical linking. Using AMP to build a whole website dramatically reduces your maintenance burden.

Some may say that copied/not-copied goes without saying. I agree with Tallyrand: "If it goes without saying, it goes all the better for saying it."