In on of the recent projects I had a requirement to do integration with Microsoft Office365 Calendar Api and for that I needed to implement Microsoft login in a react.js app. I tried to search for a readily available
npm package which I could consume easily and which fits nicely in the react ecosystem, but unfortunately I couldn't find any so I decided to write my own.
Hoping that this might be useful to someone else as well, I also published it react-ms-login on
npm. Read on to know how to use it.
The idea of having a bot, who listens, understands and responds to your commands, is very intriguing. How about creating one yourself? It might sound daunting at first but it's not that difficult in reality.
In this post we will create a bot for Google Assistant which powers
Google Now and probably some other google products. To keep this post really short and easy to follow, I will not plug the NLP piece in our bot, which you might have to in case you decide to build a really intelligent bot. Our bot will do a simple thing, when asked for a movie suggestion, it will suggest a movie.
In the previous post I tried to draw a comparison between HTTP/1.1 and HTTP/2, and based on that we set the premise that we should move to HTTP/2 for good.
With that settled, let's see how we can make express.js server run on HTTP/2.
Just by simply looking at the title, an obvious question might come up in your mind, life is so beautiful with REST over HTTP/1.1, why are we even talking about changing it? In order to address this question, let's take a step back to see how things have changed over the years in the software world.
The original design goal of HTTP was to be a protocol which can facilitate a document retrieval system for the web. The widely deployed and most prevalent HTTP version (i.e. HTTP/1.1), came to life in 1997, that was 20 years back. So much has changed on the web since then and it's very far from what it used to be at that time. Average page size has quadrupled in these year and we have started building all sorts of crazy things using web, REST and HTTP.
Google App Engine is a PAAS offering from Google Cloud Platform, which enables you to build complex web solutions with significant ease without worrying too much about the scalability or infrastructure management. If you want to develop GAE applications using python and looking for a way to setup your development environment then this post is for you.
PyCharm community edition does not come with GAE support out of the box, so you need to make changes here and there to make it work for you. Keep reading to know how to configure PyCharm to enable debugging and autocomplete for GAE applications.
If you are like me then you might be following several interesting websites and smart folks on their blogs. With so much content to read everyday, we start running out of time to consume all this information and it becomes important to know what to omit while deciding what you will be reading. Of course we certainly do not have time to visit all these websites frequently just to know whether there is a new info available, here come all these RSS reader apps which give all this information in one place.
You can see if you have your own blog and do not have RSS feed in your website then you are not thinking about such users and inadvertently sending them off resulting in low traffic to your website.
So If you have a website running on Node.js, and you are looking for a way to add RSS feed endpoint, then this post is for you, it's very easy, keep reading.
AngularJS is an undisputed champion among all the front end web development frameworks, well I am no expert to say that since honestly I have not worked much with other popular libraries like Knockout, backbone, amberJS etc. but for last few months I have been exploring the AngularJS and I am loving it.
AngularJS brings several goodies to the table, it's very well designed, robust and well thought framework. In my opinion if you are a web developer, it’s totally worth it to invest your time learning angularJS even if you do not work much on the front end and do not plan to use it in your project in near future.