royalty report
The Worst Things For Sale is Drew's blog. It updates every day. Subscribe to the Worst Things For Sale RSS!
An essential part of the recruitment process for any new teacher is meeting the pupils: but how do you do that under lockdown regulations?
If you are a teacher looking to move between schools during the coronavirus lockdown, how can you make the most of the online education experience with your new class? This is interesting new territory for many teachers. But there are thousands and thousands of teachers and pupils already learning remotely, in virtual schools – can they offer insights?
At a virtual school, lessons are delivered in line with each person’s personalised curriculum. Exactly as you would expect in a physical school space, pupils are taught how to interact with teachers, their peers and lesson content using whiteboard technology, quizzes, voice and video as well as receiving and sending assignment tasks. How should you introduce yourself to a new class, if you are meeting them online for the first time? If we consider how teachers deliver excellent classroom teaching practice in a physical space, how they prepare should not be approached any differently in an online environment.
Continue reading...Mike Pence’s press secretary tests positive to coronavirus; China reports one new case; Russia reports 10,000 new cases for sixth day in a row
Donald Trump has said coronavirus will “go away without a vaccine” and is expecting 95,000 or more deaths in the US, as Mike Pence’s press secretary tested positive for coronavirus.
The president’s comments, at an event with Republican lawmakers, capped a horror week in the US, in which it was revealed unemployment had risen to 14.7%, up from 3.5% in February, with 20 million people losing their jobs in April.
Continue reading...While an alarming 9 per cent of insects on land are being lost each decade, the state of the world’s insects is much more nuanced than warnings of an insect apocalypse
Hundreds of Pakistanis who were repatriated from the Middle East -- where many lost jobs amid coronavirus shutdowns and were living in cramped conditions -- have tested positive for COVID-19, officials said Friday. Pakistan has so far brought about 20,000 nationals home, among them a large number of unskilled workers who had been labouring in Gulf nations only to see their jobs disappear as lockdowns slowed economic activity. Of the 2,069 Pakistanis returning from the Middle East to the southern province of Sindh, more than 500 tested positive for the coronavirus, Murad Ali Shah, Sindh's chief minister, told a press conference.
Fan clubs, players from all over the world and a former Spain international in charge, Atletico Madrid's Canadian venture is currently on pause.
Two decades after the world's first major computer virus, an author finds the perpetrator in Manila.
To share upcoming changes with our partners in the React ecosystem, we’re establishing official prerelease channels. We hope this process will help us make changes to React with confidence, and give developers the opportunity to try out experimental features.
This post will be most relevant to developers who work on frameworks, libraries, or developer tooling. Developers who use React primarily to build user-facing applications should not need to worry about our prerelease channels.
React relies on a thriving open source community to file bug reports, open pull requests, and submit RFCs. To encourage feedback, we sometimes share special builds of React that include unreleased features.
Because the source of truth for React is our public GitHub repository, it’s always been possible to build a copy of React that includes the latest changes. However it’s much easier for developers to install React from npm, so we occasionally publish prerelease builds to the npm registry. A recent example is the 16.7 alpha, which included an early version of the Hooks API.
We would like to make it even easier for developers to test prerelease builds of React, so we’re formalizing our process with three separate release channels.
The information in this post is also available on our Release Channels page. We will update that document whenever there are changes to our release process.
Each of React’s release channels is designed for a distinct use case:
All releases are published to npm, but only Latest uses semantic versioning. Prereleases (those in the Next and Experimental channels) have versions generated from a hash of their contents, e.g. 0.0.0-1022ee0ec
for Next and 0.0.0-experimental-1022ee0ec
for Experimental.
The only officially supported release channel for user-facing applications is Latest. Next and Experimental releases are provided for testing purposes only, and we provide no guarantees that behavior won’t change between releases. They do not follow the semver protocol that we use for releases from Latest.
By publishing prereleases to the same registry that we use for stable releases, we are able to take advantage of the many tools that support the npm workflow, like unpkg and CodeSandbox.
Latest is the channel used for stable React releases. It corresponds to the latest
tag on npm. It is the recommended channel for all React apps that are shipped to real users.
If you’re not sure which channel you should use, it’s Latest. If you’re a React developer, this is what you’re already using.
You can expect updates to Latest to be extremely stable. Versions follow the semantic versioning scheme. Learn more about our commitment to stability and incremental migration in our versioning policy.
The Next channel is a prerelease channel that tracks the master branch of the React repository. We use prereleases in the Next channel as release candidates for the Latest channel. You can think of Next as a superset of Latest that is updated more frequently.
The degree of change between the most recent Next release and the most recent Latest release is approximately the same as you would find between two minor semver releases. However, the Next channel does not conform to semantic versioning. You should expect occasional breaking changes between successive releases in the Next channel.
Do not use prereleases in user-facing applications.
Releases in Next are published with the next
tag on npm. Versions are generated from a hash of the build’s contents, e.g. 0.0.0-1022ee0ec
.
The Next channel is designed to support integration testing between React and other projects.
All changes to React go through extensive internal testing before they are released to the public. However, there are myriad environments and configurations used throughout the React ecosystem, and it’s not possible for us to test against every single one.
If you’re the author of a third party React framework, library, developer tool, or similar infrastructure-type project, you can help us keep React stable for your users and the entire React community by periodically running your test suite against the most recent changes. If you’re interested, follow these steps:
In the cron job, update your React packages to the most recent React release in the Next channel, using next
tag on npm. Using the npm cli:
npm update react@next react-dom@next
Or yarn:
yarn upgrade react@next react-dom@next
A project that uses this workflow is Next.js. (No pun intended! Seriously!) You can refer to their CircleCI configuration as an example.
Like Next, the Experimental channel is a prerelease channel that tracks the master branch of the React repository. Unlike Next, Experimental releases include additional features and APIs that are not ready for wider release.
Usually, an update to Next is accompanied by a corresponding update to Experimental. They are based on the same source revision, but are built using a different set of feature flags.
Experimental releases may be significantly different than releases to Next and Latest. Do not use Experimental releases in user-facing applications. You should expect frequent breaking changes between releases in the Experimental channel.
Releases in Experimental are published with the experimental
tag on npm. Versions are generated from a hash of the build’s contents, e.g. 0.0.0-experimental-1022ee0ec
.
Experimental features are ones that are not ready to be released to the wider public, and may change drastically before they are finalized. Some experiments may never be finalized — the reason we have experiments is to test the viability of proposed changes.
For example, if the Experimental channel had existed when we announced Hooks, we would have released Hooks to the Experimental channel weeks before they were available in Latest.
You may find it valuable to run integration tests against Experimental. This is up to you. However, be advised that Experimental is even less stable than Next. We do not guarantee any stability between Experimental releases.
Experimental features may or may not be documented. Usually, experiments aren’t documented until they are close to shipping in Next or Stable.
If a feature is not documented, they may be accompanied by an RFC.
We will post to the React blog when we’re ready to announce new experiments, but that doesn’t mean we will publicize every experiment.
You can always refer to our public GitHub repository’s history for a comprehensive list of changes.
The military is preparing to deploy to the region to try to stop illegal logging and mining.
Representational picture
The Navi Mumbai Municipal corporation (NMMC) has offered cash reward to those people, who report about illegal dumping of debris or garbage within the city limits, especially in mangrove areas. This announcement was made yesterday by municipal commissioner N Ramaswamy, an official said today.
The move is aimed at ensuring that debris is not dumped illegally or in a haphazard manner, the official said adding that the NMMC wants people to send pictures of illegal debris or garbage dumping. "The civic body has offered cash reward of Rs 1,000 to those who expose the people or vehicles dumping debris or garbage illegally in the city, especially in the mangrove areas, " an NMMC spokesperson said.
"The corporation wants people to take photographs of the vehicles dumping debris and send it to us. We will not only act against the vehicle owners or the persons who dump it, but will ensure that they clear the dumped debris from the spot," the spokesperson added. In order to implement this scheme, civic ward officers have been appointed as the nodal officers, he said.
Citizens can share the pictures of illegal dumping of debris on the WhatsApp number- 8422955912. They can also register complaints on the NMMC website- /www.nmmc.gov.in/. In the recent past, illegal dumping of debris in mangroves has been reported widely from the several sections of the society at several places, including Palm Beach Road and Ghansoli. "Names of those who report about debris dumping will not be disclosed," he said.