Bamboo is a renewable material that when microwaved becomes stronger by weight than steel or concrete – which could make it ideal for constructing buildings, cars and planes

Black paint usually absorbs heat, but a new two-layer polymer paint reflects infrared light and keeps objects 16°C cooler, which could help make buildings more energy efficient

The UK government has set a new target of recruiting an army of 18,000 coronavirus contact tracers by the middle of May, to be in place for the launch of the NHS contact tracing app

We are already seeing the pandemic's effects on mental health, and we need to act urgently to avoid a full-blown crisis, says Sam Howells  

Over half the world’s wild tigers now live 5 kilometres from a road, and infrastructure projects planned in Asia could fragment their habitat further

Stars that are similar to the sun in every way we can measure are mostly more active than the sun, which hints that the sun’s activity may ramp up someday, risking solar eruptions

The former cabinet minister says he cannot ask campaign volunteers to work for another year.

How closely have you been paying attention to what's been going on during the past seven days?

If universities are teaching online next term students will still have to pay full tuition fees.

Some of the stories from around the world that you may have missed this week.

At React Conf 2019 we announced an experimental release of React that supports Concurrent Mode and Suspense. In this post we’ll introduce best practices for using them that we’ve identified through the process of building the new facebook.com.

This post will be most relevant to people working on data fetching libraries for React.

It shows how to best integrate them with Concurrent Mode and Suspense. The patterns introduced here are based on Relay — our library for building data-driven UIs with GraphQL. However, the ideas in this post apply to other GraphQL clients as well as libraries using REST or other approaches.

This post is aimed at library authors. If you’re primarily an application developer, you might still find some interesting ideas here, but don’t feel like you have to read it in its entirety.

Talk Videos

If you prefer to watch videos, some of the ideas from this blog post have been referenced in several React Conf 2019 presentations:

• Data Fetching with Suspense in Relay by Joe Savona
• Building the New Facebook with React and Relay by Ashley Watkins
• React Conf Keynote by Yuzhi Zheng

This post presents a deeper dive on implementing a data fetching library with Suspense.

Putting User Experience First

The React team and community has long placed a deserved emphasis on developer experience: ensuring that React has good error messages, focusing on components as a way to reason locally about app behavior, crafting APIs that are predictable and encourage correct usage by design, etc. But we haven’t provided enough guidance on the best ways to achieve a great user experience in large apps.

For example, the React team has focused on framework performance and providing tools for developers to debug and tune application performance (e.g. React.memo). But we haven’t been as opinionated about the high-level patterns that make the difference between fast, fluid apps and slow, janky ones. We always want to ensure that React remains approachable to new users and supports a variety of use-cases — not every app has to be “blazing” fast. But as a community we can and should aim high. We should make it as easy as possible to build apps that start fast and stay fast, even as they grow in complexity, for users on varying devices and networks around the world.

Concurrent Mode and Suspense are experimental features that can help developers achieve this goal. We first introduced them at JSConf Iceland in 2018, intentionally sharing details very early to give the community time to digest the new concepts and to set the stage for subsequent changes. Since then we’ve completed related work, such as the new Context API and the introduction of Hooks, which are designed in part to help developers naturally write code that is more compatible with Concurrent Mode. But we didn’t want to implement these features and release them without validating that they work. So over the past year, the React, Relay, web infrastructure, and product teams at Facebook have all collaborated closely to build a new version of facebook.com that deeply integrates Concurrent Mode and Suspense to create an experience with a more fluid and app-like feel.

Thanks to this project, we’re more confident than ever that Concurrent Mode and Suspense can make it easier to deliver great, fast user experiences. But doing so requires rethinking how we approach loading code and data for our apps. Effectively all of the data-fetching on the new facebook.com is powered by Relay Hooks — new Hooks-based Relay APIs that integrate with Concurrent Mode and Suspense out of the box.

Relay Hooks — and GraphQL — won’t be for everyone, and that’s ok! Through our work on these APIs we’ve identified a set of more general patterns for using Suspense. Even if Relay isn’t the right fit for you, we think the key patterns we’ve introduced with Relay Hooks can be adapted to other frameworks.

Best Practices for Suspense

It’s tempting to focus only on the total startup time for an app — but it turns out that users’ perception of performance is determined by more than the absolute loading time. For example, when comparing two apps with the same absolute startup time, our research shows that users will generally perceive the one with fewer intermediate loading states and fewer layout changes as having loaded faster. Suspense is a powerful tool for carefully orchestrating an elegant loading sequence with a few, well-defined states that progressively reveal content. But improving perceived performance only goes so far — our apps still shouldn’t take forever to fetch all of their code, data, images, and other assets.

The traditional approach to loading data in React apps involves what we refer to as “fetch-on-render”. First we render a component with a spinner, then fetch data on mount (componentDidMount or useEffect), and finally update to render the resulting data. It’s certainly possible to use this pattern with Suspense: instead of initially rendering a placeholder itself, a component can “suspend” — indicate to React that it isn’t ready yet. This will tell React to find the nearest ancestor <Suspense fallback={<Placeholder/>}>, and render its fallback instead. If you watched earlier Suspense demos this example may feel familiar — it’s how we originally imagined using Suspense for data-fetching.

It turns out that this approach has some limitations. Consider a page that shows a social media post by a user, along with comments on that post. That might be structured as a <Post> component that renders both the post body and a <CommentList> to show the comments. Using the fetch-on-render approach described above to implement this could cause sequential round trips (sometimes referred to as a “waterfall”). First the data for the <Post> component would be fetched and then the data for <CommentList> would be fetched, increasing the time it takes to show the full page.

There’s also another often-overlooked downside to this approach. If <Post> eagerly requires (or imports) the <CommentList> component, our app will have to wait to show the post body while the code for the comments is downloading. We could lazily load <CommentList>, but then that would delay fetching comments data and increase the time to show the full page. How do we resolve this problem without compromising on the user experience?

Render As You Fetch

The fetch-on-render approach is widely used by React apps today and can certainly be used to create great apps. But can we do even better? Let’s step back and consider our goal.

In the above <Post> example, we’d ideally show the more important content — the post body — as early as possible, without negatively impacting the time to show the full page (including comments). Let’s consider the key constraints on any solution and look at how we can achieve them:

• Showing the more important content (the post body) as early as possible means that we need to load the code and data for the view incrementally. We don’t want to block showing the post body on the code for <CommentList> being downloaded, for example.
• At the same time we don’t want to increase the time to show the full page including comments. So we need to start loading the code and data for the comments as soon as possible, ideally in parallel with loading the post body.

This might sound difficult to achieve — but these constraints are actually incredibly helpful. They rule out a large number of approaches and spell out a solution for us. This brings us to the key patterns we’ve implemented in Relay Hooks, and that can be adapted to other data-fetching libraries. We’ll look at each one in turn and then see how they add up to achieve our goal of fast, delightful loading experiences:

1. Parallel data and view trees
2. Fetch in event handlers
3. Load data incrementally
4. Treat code like data

Parallel Data and View Trees

One of the most appealing things about the fetch-on-render pattern is that it colocates what data a component needs with how to render that data. This colocation is great — an example of how it makes sense to group code by concerns and not by technologies. All the issues we saw above were due to when we fetch data in this approach: upon rendering. We need to be able to fetch data before we’ve rendered the component. The only way to achieve that is by extracting the data dependencies into parallel data and view trees.

Here’s how that works in Relay Hooks. Continuing our example of a social media post with body and comments, here’s how we might define it with Relay Hooks:

// Post.js
function Post(props) {
  // Given a reference to some post - `props.post` - *what* data
  // do we need about that post?
  const postData = useFragment(graphql`
    fragment PostData on Post @refetchable(queryName: "PostQuery") {
      author
      title
      # ...  more fields ...
    }
  `, props.post);

  // Now that we have the data, how do we render it?
  return (
    <div>
      <h1>{postData.title}</h1>
      <h2>by {postData.author}</h2>
      {/* more fields  */}
    </div>
  );
}

Although the GraphQL is written within the component, Relay has a build step (Relay Compiler) that extracts these data-dependencies into separate files and aggregates the GraphQL for each view into a single query. So we get the benefit of colocating concerns, while at runtime having parallel data and view trees. Other frameworks could achieve a similar effect by allowing developers to define data-fetching logic in a sibling file (maybe Post.data.js), or perhaps integrate with a bundler to allow defining data dependencies with UI code and automatically extracting it, similar to Relay Compiler.

The key is that regardless of the technology we’re using to load our data — GraphQL, REST, etc — we can separate what data to load from how and when to actually load it. But once we do that, how and when do we fetch our data?

Fetch in Event Handlers

Imagine that we’re about to navigate from a list of a user’s posts to the page for a specific post. We’ll need to download the code for that page — Post.js — and also fetch its data.

Waiting until we render the component has problems as we saw above. The key is to start fetching code and data for a new view in the same event handler that triggers showing that view. We can either fetch the data within our router — if our router supports preloading data for routes — or in the click event on the link that triggered the navigation. It turns out that the React Router folks are already hard at work on building APIs to support preloading data for routes. But other routing frameworks can implement this idea too.

Conceptually, we want every route definition to include two things: what component to render and what data to preload, as a function of the route/url params. Here’s what such a route definition might look like. This example is loosely inspired by React Router’s route definitions and is primarily intended to demonstrate the concept, not a specific API:

// PostRoute.js (GraphQL version)

// Relay generated query for loading Post data
import PostQuery from './__generated__/PostQuery.graphql';

const PostRoute = {
  // a matching expression for which paths to handle
  path: '/post/:id',

  // what component to render for this route
  component: React.lazy(() => import('./Post')),

  // data to load for this route, as function of the route
  // parameters
  prepare: routeParams => {
    // Relay extracts queries from components, allowing us to reference
    // the data dependencies -- data tree -- from outside.
    const postData = preloadQuery(PostQuery, {
      postId: routeParams.id,
    });

    return { postData };
  },
};

export default PostRoute;

Given such a definition, a router can:

• Match a URL to a route definition.
• Call the prepare() function to start loading that route’s data. Note that prepare() is synchronous — we don’t wait for the data to be ready, since we want to start rendering more important parts of the view (like the post body) as quickly as possible.
• Pass the preloaded data to the component. If the component is ready — the React.lazy dynamic import has completed — the component will render and try to access its data. If not, React.lazy will suspend until the code is ready.

This approach can be generalized to other data-fetching solutions. An app that uses REST might define a route like this:

// PostRoute.js (REST version)

// Manually written logic for loading the data for the component
import PostData from './Post.data';

const PostRoute = {
  // a matching expression for which paths to handle
  path: '/post/:id',

  // what component to render for this route
  component: React.lazy(() => import('./Post')),

  // data to load for this route, as function of the route
  // parameters
  prepare: routeParams => {
    const postData = preloadRestEndpoint(
      PostData.endpointUrl, 
      {
        postId: routeParams.id,
      },
    );
    return { postData };
  },
};

export default PostRoute;

This same approach can be employed not just for routing, but in other places where we show content lazily or based on user interaction. For example, a tab component could eagerly load the first tab’s code and data, and then use the same pattern as above to load the code and data for other tabs in the tab-change event handler. A component that displays a modal could preload the code and data for the modal in the click handler that triggers opening the modal, and so on.

Once we’ve implemented the ability to start loading code and data for a view independently, we have the option to go one step further. Consider a <Link to={path} /> component that links to a route. If the user hovers over that link, there’s a reasonable chance they’ll click it. And if they press the mouse down, there’s an even better chance that they’ll complete the click. If we can load code and data for a view after the user clicks, we can also start that work before they click, getting a head start on preparing the view.

Best of all, we can centralize that logic in a few key places — a router or core UI components — and get any performance benefits automatically throughout our app. Of course preloading isn’t always beneficial. It’s something an application would tune based on the user’s device or network speed to avoid eating up user’s data plans. But the pattern here makes it easier to centralize the implementation of preloading and the decision of whether to enable it or not.

Load Data Incrementally

The above patterns — parallel data/view trees and fetching in event handlers — let us start loading all the data for a view earlier. But we still want to be able to show more important parts of the view without waiting for all of our data. At Facebook we’ve implemented support for this in GraphQL and Relay in the form of some new GraphQL directives (annotations that affect how/when data is delivered, but not what data). These new directives, called @defer and @stream, allow us to retrieve data incrementally. For example, consider our <Post> component from above. We want to show the body without waiting for the comments to be ready. We can achieve this with @defer and <Suspense>:

// Post.js
function Post(props) {
  const postData = useFragment(graphql`
    fragment PostData on Post {
      author
      title

      # fetch data for the comments, but don't block on it being ready
      ...CommentList @defer
    }
  `, props.post);

  return (
    <div>
      <h1>{postData.title}</h1>
      <h2>by {postData.author}</h2>
      {/* @defer pairs naturally with <Suspense> to make the UI non-blocking too */}
      <Suspense fallback={<Spinner/>}>
        <CommentList post={postData} />
      </Suspense>
    </div>
  );
}

Here, our GraphQL server will stream back the results, first returning the author and title fields and then returning the comment data when it’s ready. We wrap <CommentList> in a <Suspense> boundary so that we can render the post body before <CommentList> and its data are ready. This same pattern can be applied to other frameworks as well. For example, apps that call a REST API might make parallel requests to fetch the body and comments data for a post to avoid blocking on all the data being ready.

Treat Code Like Data

But there’s one thing that’s still missing. We’ve shown how to preload data for a route — but what about code? The example above cheated a bit and used React.lazy. However, React.lazy is, as the name implies, lazy. It won’t start downloading code until the lazy component is actually rendered — it’s “fetch-on-render” for code!

To solve this, the React team is considering APIs that would allow bundle splitting and eager preloading for code as well. That would allow a user to pass some form of lazy component to a router, and for the router to trigger loading the code alongside its data as early as possible.

Putting It All Together

To recap, achieving a great loading experience means that we need to start loading code and data as early as possible, but without waiting for all of it to be ready. Parallel data and view trees allow us to load the data for a view in parallel with loading the view (code) itself. Fetching in an event handler means we can start loading data as early as possible, and even optimistically preload a view when we have enough confidence that a user will navigate to it. Loading data incrementally allows us to load important data earlier without delaying the fetching of less important data. And treating code as data — and preloading it with similar APIs — allows us to load it earlier too.

Using These Patterns

These patterns aren’t just ideas — we’ve implemented them in Relay Hooks and are using them in production throughout the new facebook.com (which is currently in beta testing). If you’re interested in using or learning more about these patterns, here are some resources:

• The React Concurrent docs explore how to use Concurrent Mode and Suspense and go into more detail about many of these patterns. It’s a great resource to learn more about the APIs and use-cases they support.
• The experimental release of Relay Hooks implements the patterns described here.

• We’ve implemented two similar example apps that demonstrate these concepts:

  • The Relay Hooks example app uses GitHub’s public GraphQL API to implement a simple issue tracker app. It includes nested route support with code and data preloading. The code is fully commented — we encourage cloning the repo, running the app locally, and exploring how it works.
  • We also have a non-GraphQL version of the app that demonstrates how these concepts can be applied to other data-fetching libraries.

While the APIs around Concurrent Mode and Suspense are still experimental, we’re confident that the ideas in this post are proven by practice. However, we understand that Relay and GraphQL aren’t the right fit for everyone. That’s ok! We’re actively exploring how to generalize these patterns to approaches such as REST, and are exploring ideas for a more generic (ie non-GraphQL) API for composing a tree of data dependencies. In the meantime, we’re excited to see what new libraries will emerge that implement the patterns described in this post to make it easier to build great, fast user experiences.

The CEO of a social care firm says there is a surge in demand for live-in carers due to coronavirus.

After writing my post a few months ago on building your own redux app, I have been asked a couple times to write a guide on creating redux middleware and how it works. This will be a quick post on how you can acheive anything with your own middleware!

##Basic middleware

const customMiddleware = store => next => action => {
  if(action.type !== 'custom') return next(action)
  //do stuff!
}

Applying it:

import { createStore, applyMiddleware, } from 'redux'
import reducer from './reducer'
import customMiddleware from './customMiddleware'

const store = createStore(
  reducer,
  applyMiddleware(customMiddleware)
)

Whaaa? store => next => action => I know that looks confusing. Essentially you are building a chain of functions, it will look like this when it gets called:

//next looks something like this:
let dispatched = null
let next = actionAttempt => dispatched = actionAttempt 

const dispatch = customMiddleware(store)(next)

dispatch({
  type: 'custom',
  value: 'test'
})

All you are doing is chaining function calls and passing in the neccesary data. When I first saw this I was confused a little due to the long chain, but it made perfect sense after reading the article on writing redux tests.

So now that we understand how those chained functions work, let’s explain the first line of our middleware.

if(action.type !== 'custom') return next(action)

There should be some way to tell what actions should go through your middleware. In this example, we are saying if the action’s type is not custom call next, which will pass it to any other middleware and then to the reducer.

##Doing Cool stuff

The official guide on redux middleware covers a few examples on this, I’m going to try to explain it in a more simple way.

Say we want an action like this:

dispatch({
  type: 'ajax',
  url: 'http://api.com',
  method: 'POST',
  body: state => ({
    title: state.title
    description: state.description
  }),
  cb: response => console.log('finished!', response)
})

We want this to do a post request, and then call the cb function. It would look something like this:

import fetch from 'isomorphic-fetch'

const ajaxMiddleware = store => next => action => {
  if(action.type !== 'ajax') return next(action)
  
  fetch(action.url, {
    method: action.method,
    body: JSON.stringify(action.body(store.getState()))
  })
  .then(response => response.json())
  .then(json => action.cb(json))
}

It’s pretty simple really. You have access to every method redux offers in middleware. What if we wanted the cb function to have access to dispatching more actions? We could change that last line of the fetch function to this:

.then(json => action.cb(json, store.dispatch))

Now in the callback, we can do:

  cb: (response, dispatch) => dispatch(newAction(response))

As you can see, middleware is very easy to write in redux. You can pass store state back to actions, and so much more. If you need any help or if I didn’t go into detail enough, feel free to leave a comment below!

You cannot blame Chennai Super Kings (CSK) for missing their favourite son in action during what would have been the 13th edition of the Indian Premier League (IPL).

Had COVID-19 not wreaked havoc, the cash-rich T20 league would have been in full swing and all eyes would have been trained on Mahendra Singh Dhoni, returning to cricket after a sabbatical.

 

 

 

View this post on Instagram

#WhistlePodu ðŸ¦ÂðŸ’› VC: @sakshisingh_r @mahi7781

A post shared by Chennai Super Kings (@chennaiipl) onMay 5, 2020 at 6:04am PDT

Dhoni, CSK's decorated captain who led India to 2007 T20 and 2011 ODI World Cup triumph besides shepherding the Yellow Brigade to three IPL crowns, has not played competitive cricket since India's 2019 World Cup semi-final loss to New Zealand.

The 38-year old was supposed to make a much-awaited comeback in the IPL and had also attended CSK's camp before the deadly virus forced sport across the world to come to a grinding halt.

CSK, on Tuesday, shared a video where Dhoni is seen spending time with daughter Ziva and his dog at his lawn in Ranchi with his back towards the camera.

"#Thala @msdhoni's back...quite literally so! Smiling face with smiling eyes #WhistlePodu," CSK captioned the tweet, crediting Dhoni's wife Sakshi for capturing the video.

The veteran wicketkeeper batsman is also seen giving the dog some catches with the ball with Ziva for company.

Meanwhile, dashing England wicket-keeper batsman Jos Buttler has said that Dhoni has always been a big idol and while playing in the IPL one lesson for him has been how the former India skipper manages all the fanfare and still performs in crunch situations.

"MS Dhoni has always been a big idol of mine and chaos is always going around him, people wanting a bit of him, the cricket and the noise.

"....it is such a great lesson to just watch him and see first hand how to manage all that thing if you have to perform at the top level and perform in those crunch moment, that certainly has been one of the massive pluses," Buttler said in an interview to Lancashire Cricket with Warren Hegg.

Catch up on all the latest sports news and updates here. Also download the new mid-day Android and iOS apps to get latest updates.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

Anirban Blah, co-founder of talent agency Kwan Entertainment, was rescued by the traffic police on Friday while attempting suicide on old Vashi bridge. On October 16, four anonymous women had levelled allegations of sexual harassment against Das, speaking exclusively to mid-day. Following this paper’s report, Blah was asked by Kwan’s management to "step aside" from his position on Tuesday afternoon.

The incident happened around 12.30 am when the traffic police received a tip-off about a man trying to jump off Vashi bridge. During counselling by the police, Blah said that was depressed after losing his job.

An actress shared her two-year-long ordeal which started with Blah bumping into her at a meeting and later asking her to participate in an ‘unnatural sex set-up’. Another model told mid-day that Blah had asked her to strip when she visited his home for a professional meeting.

With the accounts of harassment going viral following mid-day’s report, Blah was relieved of his position and his stake was transferred to the remaining 10 partners. A statement from Kwan dated October 17 read, "The other 10 partners have taken over the entire stake of Anirban Blah in KWAN to ensure his exit. In this regard, the partners and Anirban will enter into the necessary legal documentation to ensure the exit is in accordance with the law."

Also Read: Kwan's Anirban Das Blah loses stake in his company

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

Technology avoids obstacles by sensing air flow disruptions

T - Demte pursuing European challenge and Ethiopian dream

When normalcy returns, Varun Dhawan may well host a glitzy bash that mentor Karan Johar would approve of. For now though, an intimate celebration is on the cards for the star who turns 33 today. The actor plans to spend the big day with dad David, mother Lali, brother Rohit and family, who stay a few floors above him in a Juhu highrise.

It was originally supposed to be a working birthday for the actor as Coolie No 1 was slated to release on May 1. "The family had considered formally announcing Varun's engagement to long-time girlfriend Natasha Dalal on the occasion. However, given the current scenario, they have decided to do it at an appropriate time," says a source.

David Dhawan

Though tight-lipped on the subject of Varun-Natasha's engagement, filmmaker David says he is glad the family is together on the star's big day. "It will be a quiet family affair. Over the past few weeks, Varun has been with us, and has been taking care of Lali and me. He is especially concerned about me as I am diabetic," he says. Ask him about the fate of Coolie No 1, and the filmmaker says, "It's my 45th film as a director. I think people will want to watch comedy [post the crisis]. Work on the film is underway."

Catch up on all the latest entertainment news and gossip here. Also, download the new mid-day Android and iOS apps.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

Actor Taapsee Pannu who is on a photo-sharing spree these days on Saturday shared an exquisite throwback picture from her trip to Rome. Just like many others who are dreaming of vacations during the lockdown, the 'Pink' actor is also seen reminiscing about her vacation in her latest throwback post on social media.

 

 

 

View this post on Instagram

One of those trips I just decided to take very impulsively. Rome. Was in my list since long time. I love seeing places which should either have beach, crystal blue water n good restaurants or should have a lot of history to know n study about and have a lot of good restaurants. Basically good restaurants is the basic common key here. I loved using all the local apps to find me local transport n restaurants to dine in. Quaint cafes which make u pause. I think it will be some till I experience the thrill of travelling again. But until then, we can make a list of all places in the world we want to see coz life is too short and we all have witnessed that it’s quite possible that things won’t be the same tomorrow 🤷🏻‍♀ï¸Â #Throwback #Archives #QuarantinePost

A post shared by Taapsee Pannu (@taapsee) onApr 24, 2020 at 9:57pm PDT

Alongside a picturesque picture shared on Instagram, the actor wrote: "One of those trips I just decided to take very impulsively. Rome. Was in my list since long time... "

Taking it to the captions, the 'Mulk' actor also pinpointed the key factors she seeks while travelling. "I love seeing places which should either have a beach, crystal blue water n good restaurants or should have a lot of history to know n study about and have a lot of good restaurants," the caption read.

"Basically good restaurants are the basic common key here," the 32-year-old wrote. She also mentioned her interest in using the "local apps" to find her "local transports and restaurants to dine in." "Quaint cafes which make u pause," she added.

Referring to the current lockdown and unpredictable situation the life has been thrown into in the wake of coronavirus crisis, Taapsee also added that one can "experience the thrill of traveling again.. until then, we can make a list of all places in the world we want to see coz life is too short and we all have witnessed that it's quite possible that things won't be the same tomorrow."

Lately, the 'Manmarziyaan' actor has been sharing many throwback pictures as she earlier announced on Instagram that she will be posting a series to refresh some memories amid the coronavirus lockdown.

Taapsee is currently at home like many other celebrities as the country is under lockdown to prevent the spread of the coronavirus.

Catch up on all the latest entertainment news and gossip here. Also, download the new mid-day Android and iOS apps.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

Actress Bhumi Pednekar has been honing her green thumb during the COVID-19 lockdown. The actress has taken to social media to share the yield she has grown at home. The list includes feugreek (methi), mustard (sarson), amaranth (cholai), green chillies, brinjals and strawberries.

Sharing the photos of her homegrown crops on Instagram, the actress wrote: "After months of tender love & care, we present to you #PednekarKePed #homegrown #GharKiKheti #sustainableliving."

 

 

 

View this post on Instagram

After months of tender love & care,we present to you #PednekarKePed 🌱 #homegrown #GharKiKheti #sustainableliving

A post shared by Bhumi✨ (@bhumipednekar) onApr 25, 2020 at 2:56am PDT

Earlier this month, the actress had announced that she would utilise the lockdown time learning the science of hydroponics (soil-less) farming from her mother Sumitra Pednekar.

"My mom and I always wanted to have a hydroponics garden of our own where we grow our own vegetables and can have a fully sustainable lifestyle. We wanted to have a garden to table lifestyle at home and we are both happy with the progress," she had shared.

Catch up on all the latest entertainment news and gossip here. Also, download the new mid-day Android and iOS apps.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

It has been seven years since Mohit Suri's Aashiqui 2, starring Aditya Roy Kapur and Shraddha Kapoor came out. It made the actress an overnight star and sensation, and her character, Aarohi, still continues to be remembered for her piquancy and innocence, and of course, singing.

Every year, the actress does something special on this day to mark this musical blockbuster's anniversary and this year was no exception. She not only changed her Instagram name to her screen name from the film and upload a new photo from one its stills, but also uploaded a collage of some of the film's scenes to create one beautiful picture.

This is truly an innovative and imaginative way to celebrate your film, don't miss this post:

 

 

 

View this post on Instagram

7 years of Aashiqui 2 today!🥰💝 Thank you forever @mohitsuri for this gift of a lifetime @visheshfilms for believing, #ShaguftaRafique for your exquisitely beautiful writing, @adityaroykapur for being an unbelievably amazing costar and the entire team who gave their everything to this precious film. Thank you everyone who gave this film so so sooo much love. Its priceless✨ Thank you to all those who have made such beautiful edits and to the fan clubs for uniting and sharing a common dp today; this collage 🙃🥰 I’m the luckiest girl in the universe ✨💜

A post shared by Aarohi (@shraddhakapoor) onApr 25, 2020 at 11:43pm PDT

Shraddha Kapoor is well known for always delivering hits along with a new character and fresh content with every project. Shraddha being a lover of always wanting to try something new has been unstoppable ever since Aashiqui 2.

After Aashiqui 2, taking no breaks, Shraddha was seen in Ek Villain, where the character of being full of life was super fresh. Not forgetting ABCD 2 where Shraddha's dance totally stole hearts. Shraddha showed her versatility factor and the audiences were stunned on how the actress can mould herself in every way possible.

Moulding herself into another new character, Shraddha was seen doing some kicks and punches in Baaghi. The actress has given a carousel of hits and is a roll as the actress chooses quality projects over quantity and this totally sets her apart. Shraddha knows how to treat her fans with the best of characters, where fresh content always hunts Shraddha.

On the work front, Shraddha will be seen in a Luv Ranjan directorial alongside Ranbir Kapoor. The actress is basking in the success of Baaghi 3. Truly we can't wait to see what this fresh pair has brewed for us!

Catch up on all the latest entertainment news and gossip here. Also, download the new mid-day Android and iOS apps.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

 According to a recent study, the number of suicide attempts in youth has doubled since 2008.

The research looked at trends in emergency room and inpatient encounters for suicide ideation and attempts in children ages 5-17 years at U.S. children's hospitals from 2008 to 2015.

During the study period, researchers at the Vanderbilt University Medical Center identified 115,856 encounters for suicide ideation and attempts in emergency departments at 31 children's hospitals. Nearly two-thirds of those encounters were girls. While increases were seen across all age groups, they were highest among teens ages 15-17, followed by ages 12-14.

Just over half of the encounters were children ages 15-17; another 37 percent were children ages 12-14; and 12.8 percent were children ages 5-11. Seasonal variation was also seen consistently across the period, with October accounting for nearly twice as many encounters as reported in July.

Using data from the Pediatric Health Information System (PHIS), the researchers used billing codes to identify emergency department encounters, observation stays and inpatient hospitalizations tied to suicide ideation and attempts. In addition to looking at overall suicide ideation and attempt rates in school-age children and adolescents, the researchers analyzed the data month-by-month and found seasonal trends in the encounters. Peaks for encounters among the groups were highest in the fall and spring, and lowest in the summer.

"To our knowledge, this is one of only a few studies to report higher rates of hospitalization for suicide during the academic school year," said study lead author Greg Plemmons.

Rates were lowest in summer, a season which has historically seen the highest numbers in adults, suggesting that youth may face increased stress and mental health challenges when school is in session.

"The growing impact of mental health issues in pediatrics on hospitals and clinics can longer be ignored," said Plemmons.

The study has been published in the journal Pediatrics

Representational Image

Components in the mosquito saliva can trigger an unexpected and long-lasting immune responses -- up to seven days post-bite, say scientists.

The researchers found that more than 100 proteins in mosquito saliva are mediating the effects on the immune system, or may help the virus become more infectious.

Identifying these proteins could help design strategies to fight transmission of dengue fever as well as other diseases caused by viruses also transmitted by Aedes aegypti, such as Zika virus, chikungunya virus and yellow fever virus, the researchers said.

"We found that mosquito-delivered saliva induced a varied and complex immune response we were not anticipating," said Silke Paust, Assistant Professor at Baylor and Texas Children's Hospital.

"Billions of people worldwide are exposed to diseases transmitted by mosquitoes, and many of these conditions do not have effective treatments," added Rebecca Rico-Hesse, Professor at the Baylor College of Medicine in Texas, US.

For the study, appearing in the journal PLOS Neglected Tropical Diseases, the team worked with a mouse model of the human immune system.

Previously, the team demonstrated that mosquito-bite delivery and needle-injection delivery of dengue virus in these "humanised mice" led to significantly different disease developments

They found that mosquitoes are not just acting like "syringes" to merely inject viruses, but their saliva seems to contribute significantly to the development of the disease.

In the new study, the team tested the effect of virus-free mosquito saliva on humanised mice and compared the results with those obtained from humanised mice that had not been bitten by mosquitoes.

Evidence to immune responses -- up to seven days post-bite -- was found in multiple tissue types, including blood, skin and bone marrow, the researchers said.

"For instance, both the immune cell responses and the cytokine levels were affected. We saw activation of T helper cells 1, which generally contribute to antiviral immunity, as well as activation of T helper cells 2, which have been linked to allergic responses," Paust said.

"The diversity of the immune response was most striking to me. This is surprising given that no actual infection with any type of infectious agent occurred," he noted.

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

Representation pic

A massive fire broke out in a three-storey building in the Kasa area here in the wee hours today, the district rural police said. One person was feared dead, but there was no official confirmation yet, they said. The police received a call around 3.30 am about the blaze in the residential-cum-commercial building, located near a temple in the Kasa area of the Dahanu taluka.

The building's ground floor and the first floor, which housed a provisions store and its godown, were completely gutted in the fire, the police said in a release issued here. However, residents of the four apartments on the building's second floor were evacuated, the police said, adding that one person was feared killed in the fire, but there was no official confirmation yet. Three fire engines were rushed to the spot. The flames were doused but the cooling work was still on, the police added.

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

Representational Image

A 28-year-old labourer died after he fell off the 20th floor of an under-construction building in suburban Malad, police said on Tuesday. The incident occurred when Abu Tahir was doing a plastering work on the 20th floor of the high-rise in a Malwani area, said a police official.

Tahir was rushed to a hospital by locals where doctors declared him brought dead. A case was registered under section 304 (A) (causing death due to negligence) against two persons for not ensuring the safety of the labourer, he said, adding that further investigation is on.

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates