For when you need just a bunch of code on the server, why hire an entire machine?

Have you ever used a browser event such as onscroll or onresize in a web app? If you did, you certainly would have noticed how the app heavily slows down if you call anything that requires even a little bit of extra processing juice.

When vanilla JS beginners start to feel that they have become mature enough to play with some serious code now, they usually head to frameworks. I've seen newbies use as heavy scaffolds as Angular to create basic forms.

A user-friendly guide to the world's largest free static web hosting. Configuring a website on GitHub Pages is one of the easiest things to do. I'm gonna chart the process out in simple words -

GitHub Pages is a web hosting service offered by GitHub, which allows you to host your websites on a github.io subdomain. The coolest thing about this service is that it integrates directly with your codebase, ie. your code's repository, so deploying a site on GitHub Pages means simply pushing your files onto your GitHub Repository, and the GitHub Pages system then takes your bunch of files, optionally passes them through a build sequence and then deploys it to the github.io subdomain assigned to your repo.

I’ve decided to create a detailed guide on GitHub Pages, a platform used by over 40 million developers to host their projects as well as static webpages. I see a lot of beginners struggling to configure the service correctly on their projects, and more often than not risk themselves towards alarming issues such as domain takeover, security key exposure etc.

One of the most amazing recent experiences I had with a popular third-party SDK was with the PayTM payment gateway Android SDK. The task was to integrate the SDK into a project to facilitate the acceptance of in-app payments through PayTM.