Microsoft Introduced 'Magic Mirror' in the InnovFest Unbound conference . This Device is Useful for People With Time Crunch in Morning . Most of People have Shortage of Time in Morning To Get Ready to Get out of Door for work .
Magic Mirrror is Connected To Internet . Magic Mirror will Recognize their Face in Morning and Welcoming them with Personalized Hello Message . It uses Windows Hello Technology For Facial Recognition. It will also show More Daily updates Like Weather Conditions , Personalized Latest News Updates that will be shown on Upper Portion of Mirror . It Can also record you commute to office and Can also Tell whether there is less Traffic or Traffic Jam on that Way .
Main Highlights or Magic Mirror Are -
1. Magic Mirror is 23.6 inch LCD screen
2. It's having black background with White UI Elements
3. It is Powered By Rasberry PI and Windows Hello for Facial Recognition
4. It Can show Weather Conditions Today
5. It Can also Show Latest News Updates
6. It Can also Show Feeds From Facebook and Twitter
7. It uses Windows Hello Technology For Facial Recognition.
“Imagine when you wake up in the morning, you’re able to use the mirror to style your hair, do your makeup, and while doing that, you can also view the weather,” explained Izzat Khair of Microsoft's developer experience team.
Magic Mirror Can also be used for Direct Advertisements to Person. The facial recognition feature could also provide real-time information to advertisers on how people are reacting to an advertisement displayed on the smart mirror.
The Magic Mirror’s facial recognition system can recognize eight different emotions, including anger, happiness and surprise. Microsoft’s Cognitive Services Face API matches a person’s face to their profile, and allows the mirror to display information relevant to that person’s mood.
Magic Mirror is powered with low-cost and readily-available Raspberry Pi running Windows 10 IoT Core. To provide the interface and basic functionality, Microsoft decided to use a simple Hosted Web App. In fact, the company has open-sourced the application source code and bill of materials on GitHub for you to give it a go yourself.
The web app is created in HTML, CSS, and JavaScript and served from a Node instance hosted on Azure. Using the Hosted Web apps bridge, Microsoft converted their web app into a Universal Windows App which provided access to Windows Native APIs and enabled it to run across Windows-powered devices, such as the Raspberry Pi 3.
Magic Mirror is still in development stage and no commercial release date is announced
Gulp and Grunt are both Automated Task Runner . Major Difference Between Gulp and Grunt Lies in How They Deal With Automation of Tasks Internally .
Gulp Uses Node Streams For running different tasks and Grunt use temp files for the same work .
Grunt runns tasks using Temporary files which are disk I/O operations. Your SASS file is compiled and then written to a temporary file. The temporary file is used by the autoprefixer and then the final product is written to the destination file.
Gulp runs task all in main memory. Your SASS file is compiled in main memory, then the result is passed to the autoprefixer without being written to a file and the destination file is then written out.
Front-End Developers Tend To Deal with many things that include : -
Decrease http request by concatinating CSS FIles and JS Files Together for showing on website
Compressing and Minifying CSS and JS Files
Optimizing Image to reduce their size by maintaining Quality of image
Saas authoring
Rendering DOM
This is just an overview of task that needs to be run there is large list of tasks needs to be done . Grunt and Gulp are tools that does these tasks for us and don't bother us to do them . After setting up Grunt or Gulp all these list of tasks can be done automatically without bothering you about any of them and everything managed automatically and efficiently
Why Do I Need Gulp Or Grunt
Things that gulp and grunt do are not that you can't do without gulp and grunt . There are number of tasks you need to do you can also manually do all of them manually using number of availale tools But Gulp and Grunt Has kept them all under one roof and you manually need not to do anything it automatically do all these tasks and manages everything
Do I Need To Learn NODE For Using Gulp / Grunt
You just need to install node and not need to do anything more . Like we use mailing platform gmail or We use wordpress for blogging but don't do coding in that on non-developer part
Working of GRUNT
Grunt runns tasks using Temporary files which are disk I/O operations. Your SASS file is compiled and then written to a temporary file. The temporary file is used by the autoprefixer and then the final product is written to the destination file.
Working of Gulp
Gulp runs task all in main memory. Your SASS file is compiled in main memory, then the result is passed to the autoprefixer without being written to a file and the destination file is then written out.
Npm and Bower are both Project dependency management tools. But the main difference between both is npm is used for installing Node js modules but bower js is used for managing front end components like html,css,js etc.
npm is most commonly used for managing Node.js modules, but it works for the front-end too when combined with Browserify etc
Bower is front-end Package Manager. The biggest difference is that npm does nested dependency tree that increases its size eventually while Bower requires a flat dependency tree No nested versioning of Packages
NESTED DEPENDENCY TREE A nested dependency tree means the dependencies or Packages we added in our project can also be dependent on other dependencies and those can further have more dependencies and so on. This is not a problem for a website where you does not care about space and performance of application . It tells you need to care about dependency conflicts as all your dependencies use their own version of Underscore.This increases size and make heavy load for pages. Imagine a site having to download three copies of jQuery as due to different packages require different version of jquery
The reason many projects use both is that they use Bower for front-end packages and npm for developer tools like Yeoman, Grunt, Gulp, JSHint, CoffeeScript, etc.
SEPARATE PACKAGE DEPENDENCY APPROACH
The main difference between npm and Bower is the approach for installing package dependencies. npm installs dependencies for each package separately, and as a result makes a big package dependency tree (node_modules/grunt/node_modules/glob/node_modules/...), where there could be several version of the same package. For client-side JavaScript this is unacceptable: you can't add two different version for jQuery or any other library to a page. With Bower each package is installed once (jQuery will always be in the bower_components/jquery folder, regardless of how many packages depend on it) and in the case of a dependency conflict, Bower simply won't install the package incompatible with one that's already installed.
