Reason compiles to JavaScript thanks to our partner project, BuckleScript, which compiles OCaml/Reason into readable JavaScript with smooth interop. Reason also compiles to fast, barebone assembly, thanks to OCaml itself.

Revery is like flutter in that it does not use native widgets.

Today, Electron is one of the most popular tools for building desktop apps - using an HTML, JS, CSS stack. However, it has a heavy footprint in terms of both RAM and CPU - essentially packing an entire browser into the app.

I'm considering this, although I'm still leaning towards not including it and I'd love to just get rid of first if it wouldn't break so many peoples tests. Newcomers to Capybara don't understand (or aren't willing to learn) the issues that all/first (and last if added) have and massively overuse them. Yes the fact that all and first now wait by default will prevent some of the new user issues/confusion, but it won't fix the non-reloadability issue.

It makes sense that the incoherent render would not be committed to browser and that it would not have any consequences most of the time. But that means that you render logic must be ready to manage incoherency between props and states without crashing. E.g. a list of resource ids in props that doesn't match a list of http requests from a previous id list in the state could lead to weird situations. This is a worry that didn't exist in class components.

Since an uncontrolled component keeps the source of truth in the DOM, it is sometimes easier to integrate React and non-React code when using uncontrolled components.

This does not set the native input element to indeterminate due to inconsistent behavior across browsers. However, we set a data-indeterminate attribute on the input.

Please submit questions like this on StackOverflow next time. People answers on GitHub don't compound as much

the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.

Can I ask people to upvote my submission? No. Users should vote for a story because they personally find it intellectually interesting, not because someone has content to promote.

The thing is that each UI decision depends on countless other UI decisions. A simple example is keybindings. On UNIX/Linux, it’s nearly impossible to pick reasonable default bindings for global desktop navigation because they all conflict with bindings that some app is using. On Windows, the desktop navigation bindings are hardcoded, and no app uses them, because apps know for sure which bindings to avoid.

REST and GraphQL are wonderful tools to create an API that is meant to be consumed by third parties. Facebook's API, for example, is consumed by ~200k third parties. It is no surprise that Facebook is using (and invented) GraphQL; a GraphQL API enables third parties to extensively access Facebook's social graph enabling them to build all kinds of applications. For an API with that many consumers, GraphQL is the fitting tool. But, to create an internal API (an API developed and consumed by code written by the same organization), RPC offers a simpler and more powerful alternative. Large companies, such as Netflix, Google and Facebook, are starting to replace REST/GraphQL with RPC for their internal APIs. Most notably with gRPC which is getting popular in the industry.

Discourse

Some time ago I asked on Reddit: “What’s the consensus among the React community for testing React components?” Shawn Wang replied: “testing is an enormously complicated and nuanced topic on which there isn’t a consensus anywhere in JS, much less in React.” I was not trying to find the best library for testing React. Mainly because there isn’t one.

// This is not really a mock, but jest prevents out of scope // variables unless prefixed with "mock".

cant you see he has only 11 reputations, and how can he comment?

"While we hope that Google will lift these unwarranted sanctions for AdNauseam, it highlights a much more serious problem for Chrome users," the AdNauseam team adds. "It is frightening to think that at any moment Google can quietly make your extensions and data disappear, without so much as a warning."

Risk assessment◕Risk management strategy○Supply chain risk management◑

Risk assessment

none of them analyzed the threat of, and vulnerabilities to, a cyberattack spanning all three interconnections.

Problem definition and risk assessment

Problem definition and risk assessment.Addresses the particular national problems, assesses the risks to critical assets and operations—including the threats to, and vulnerabilities of, critical operations—and discusses the quality of data available regarding the risk assessment.

Further, federal agencies have performed three assessments of the potential impacts of cyberattacks on the industrial control systems supporting the grid.

The electric grid is becoming more vulnerable to cyberattacks via (1) industrial control systems, (2) consumer Internet of Things (IoT)45devices connected to the grid’s distribution network, and (3) the global positioning system (GPS).

molecular explanations of whether such shifts represent cause or effect of the disease itself are limited

export type Data = { [scope in Scopes]: ScopedData<scope> };

var entityTypes = { Report: <ReportEntityType>{ properties: { id: { dataType: "number" }, title: { dataType: "string", required: true, displayName: "Title" } } } };

7-Eleven moves to support animal welfare By Nick Hall | 17 Feb 2019 View comments Global convenience chain, 7-Eleven has made major changes to its supplier sourcing agreement, eliminating caged eggs for the first time. The move follows ongoing criticism of the Australian cage egg farming industry, with several brands and chains making the early decision to move to wholly sustainable sourcing in-line with welfare standards. Working closely with suppliers across all states, 7-Eleven has now ensured that only free range eggs would be available for order by all stores. Clayton Ford, General Manager Corporate Affairs, 7-Eleven said the decision to phase out cage eggs was developed in accordance with franchisee wishes, with the convenience giant announcing it will increase support to assist in the transition. “Whilst our franchisees are free to engage with alternative suppliers due to our franchise agreement, we will continue to work alongside them to encourage their involvement in this initiative by sourcing free range eggs via our centralised supply chain,” Ford said. “We recognise that this is just one step, and we will continue to review animal welfare commitments in our supply chain and 7-Eleven branded products as opportunities arise.” Want to launch a convenience store of your own? Take a look at all available franchising opportunities here.

Let's make the example even easier. function convertDate<T extends string | undefined>(isoDate?: string): T { return undefined } 'undefined' is assignable to the constraint of type 'T' Means: What you return in the function (undefined), matches the constraints of your generic type parameter T (extends string | undefined). , but 'T' could be instantiated with a different subtype of constraint 'string | undefined'. Means: TypeScript does not consider that as safe. What if you defined your function like this at compile time: // expects string return type according to generics // but you return undefined in function body const res = convertDate<string>("2019-08-16T16:48:33Z") Then according to your signature, you expect the return type to be string. But at runtime that is not the case! This discrepancy that T can be instantiated with a different subtype (here string) than you return in the function (undefined) is expressed with the TypeScript error.

There are many strings which I need to convert if not undefined. I could do as follows: { date1: date1 ? formatISODate(date1) : undefined, date2: date2 ? formatISODate(date2) : undefined ...

Both of the below are valid as far as T extends (...args: any[]) => any goes logFn((a, b) => a + b) logFn((a, b, c) => c) But if you refer back to the example I gave, the inner definition as: return (a, b) => fn(a, b); So option 2. will throw an error here, which is why typescript is warning you about it.

In the body of the function you have no control over the instantiation by the calling context, so we have to treat things of type T as opaque boxes and say you can't assign to it. A common mistake or misunderstanding was to constraint a type parameter and then assign to its constraint, for example: function f<T extends boolean>(x: T) { x = true; } f<false>(false); This is still incorrect because the constraint only restricts the upper bound, it does not tell you how precise T may really be.

P can't be assigned {}, since the Generic Type P can be a more defined (or restricted) type.

For the uninitiated, Granny Smith was Maria Ann Smith, a resident of the area who in 1868 "accidentally" grew the first batch of green apples that now bear her name.

Each year the winner is crowned with great fanfare at Eastwood Shopping Centre, which is owned by Yuhu Group, the company founded by billionaire property developer and political donor Huang Xiangmo.

you can have a Type that is more specific than a boolean like this

The value 10 is assignable to the constraint of T, but it is not assignable to this particular instantiation of T. If there was no error I would passing 10 where 3 is expected!

BrainHQ, is an online brain-training software also developed by Posit Science. It is the only software available in Greek being used to any portable computing device (tablet, smartphone, etc.) as an application either on Android or on IOS provided in different languages. Undoubtedly, improvement of brain performance can bring multiple benefits to everyday life. Both research studies and the testimonials of users themselves show that BrainHQ offers benefits in improving thinking, memory and hearing, attention and vision, improving reaction speed, safer driving, self-confidence, quality discussion and good mood. BrainHQ includes 29 exercises divided into 6 categories: Attention, Speed, Memory, Skills, Intelligence and Navigation.

RFClarification

Unfortunately, numerous widely-used tagless-final interfaces (like Sync, Async, LiftIO, Concurrent, Effect, and ConcurrentEffect) encourage you to code to an implementation.

Try to avoid mucking with native prototypes, including Array.prototype, if you don't know who will be consuming your code (3rd parties, coworkers, yourself at a later date, etc.). There are ways to safely extend prototypes (but not in all browsers) and there are ways to safely consume objects created from extended prototypes, but a better rule of thumb is to follow the Principle of Least Surprise and avoid these practices altogether.

He's not messing with them he's extending them for Arrays.

Their hope by announcing so loudly what they have accomplished, is that others in the Android modder/hacker scene will step up and help them turn this root exploit into something useful for users by deploying features that are not currently available through the Google controlled Chromecast experience.

This issue is already known to us since yesterday. Our engineers are now working diligently to fix this behavior. I'd recommend you contact our Customer Care team and let them know that you're one of the affected users of INV36818. That way, they will link your company to the case. You will then receive a notification via email for its updates. 

Robert Sedlack, my professor for Visual Communication Design I (who also happened to be my advisor and the driving reason why I decided to join the design program) banned two phrases during critiques in his class: “I like” and “I don’t like.”

In Chrome browser, open Developer Tools and select Elements tab, then open the contextual menu of the parent node of the element you want to inspect, in the contextual menu click on Break on > Subtree modifications. Afterwards you just need to click on the page and you'll get on the inspector without losing focus or losing the element you want to inspect.

(() => { debugger; }, 5000)

However, if more control is needed, you can pass any of these pieces of state as a prop (as indicated above) and that state becomes controlled. As soon as this.props[statePropKey] !== undefined, internally, downshift will determine its state based on your prop's value rather than its own internal state.

refKey: if you're rendering a composite component, that component will need to accept a prop which it forwards to the root DOM element. Commonly, folks call this innerRef. So you'd call: getRootProps({refKey: 'innerRef'}) and your composite component would forward like: <div ref={props.innerRef} />

setState({isOpen: true}

Inner RefSome components are passed an innerRef property to facilitate for internally managed behaviour within the base select. This should be assigned to the ref property of the relevant dom element. i.e.const CustomOptionComponent = ({ innerProps, innerRef }) => (<div ref={innerRef} {...innerProps} />) Inner PropsAll functional properties that the component needs are provided in innerProps which you must spread.

The equivalent ways in functional components using Hooks:In a state variable: useState or useReducer. Updates in state variables will cause a re-render of the component.In a ref: Equivalent to instance variables in class components. Mutating the .current property won’t cause a re-render.

I just don't feel like doing the change.

const forceUpdate = () => useState(0)[1];

const [, updateState] = React.useState(); const forceUpdate = React.useCallback(() => updateState({}), []);

const [value, set] = useState(true); //boolean state return () => set(!value); // toggle the state to force render

What is the average cost to build a website?

move away from identifying correlative relationships between characteristics of the microbiome and system-level processes, and towards identifying more causative and mechanistic relationships

For every question you might have, please create a discussion thread, not a single comment. This makes it a bit easier to see and reply to the question, instead of questions and answers getting mixed together:

const list = [].concat(x);

Which brings me back to 1984.  Also in that year, Michael Piore and Charles Sabel published The Second Industrial Divide: Possibilities for Prosperity (Basic). They found their new highly flexible manufacturing firms in northwestern and central Italy instead of Silicon Valley.  Their entrepreneurs had ties to communist parties and the Catholic Church instead of liberation sympathies. But the idea was much the same: computers would be the key to flexible specialization. For all the talk since about economic complexity, that is the book about the changing division of labor worth re-reading.

But what about useState? it used whenever we have some variable that whenever it changes, we want to re-render our component and show some new contents.

I've forked the project and made a substantial extension. I think is ready to merge back. But (appropriately) its the project owner who gets to make that call not me. And it's now been several weeks without reply.

No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.

I'm working full time on Material-UI since 2019. I was working on it during my free time before that. I hope that I can leverage my full-time involvement in the library to make it really awesome. You are right, the project is well-funded. We hope we can fund the time of more than 1 person full time in the future, with the current growth rate, it should soon be possible. We have 3 people working part-time on the project (Matt, Sebastian and Josh), plus the community behind us (+1,000 code contributors).

Although such encapsulation is desirable for application-level components like FeedStory or Comment, it can be inconvenient for highly reusable “leaf” components like FancyButton or MyTextInput. These components tend to be used throughout the application in a similar manner as a regular DOM button and input, and accessing their DOM nodes may be unavoidable for managing focus, selection, or animations.

I am an avid reader, but I’m always struggling to memorize my learnings. I guess, that's why I started to write down my notes of books I enjoyed to read.

relationships between characteristics of microbiomes and the system-level processes that they influence are often evaluated in the absence of a robust conceptual framework and reported without elucidating the underlying causal mechanisms. The reliance on correlative approaches limits the potential to expand the inference of a single relationship to additional systems and advance the field