With iOS 11.3, Apple has silently added support for the basic set of new technologies behind the idea of “Progressive Web Apps” (PWAs). It’s time to see how they work, what are their abilities and challenges, and what do you need to know if you already have a published PWA.
A self-study guide for aspiring machine learning practitioners
A year back while describing the differences between setImmediate & process.nextTick, I wrote a bit on the low level architecture of node’s event-loop.
Surprisingly, the readers of that post became more interested about the event-loop part, than the rest of the parts and I have received a lot of responses and queries on the same.
That’s why I’ve decided to come up with a big picture of the low level work flow of node.js event loop.
I recommend you to read the entire article and not just bullet points as there are some great infos inside the paragraphs!
Why am I writing this?
Well, if I google about
node.js event loop, majority of the articles out there does not describe the big picture (they try to describe with a very high level abstraction).
Everyone, the day has come.
AWS Lambda is finally. Compatible. With Golang. 🖖
Here’s how you can start using Go with the Serverless Framework RIGHT NOW and deploy Lambdas to your heart’s content.
A little over a year ago, I joined Cloud Foundry to work on Loggregator, Cloud Foundry’s application logging component. Its core concern is best-effort log delivery without pushing back on upstream writers. Loggregator is written entirely in Go.
After spending more than a thousand hours working with Go in a non-trivial code base, I still admire the language and enjoy using it. Nonetheless, our team struggled with a number of problems, many of which seem unique to Go. What follows is a list of the most salient problems.
Over the years, we have noticed a few issues in React Native apps that make us want for “something more”.
Our search for this “something more” has led us to Google’s Flutter!
It’s no surprise that cloud computing has literally taken the world by storm. For most businesses and enterprises, gone are the days of struggling with complicated on-premise server rooms and complicated networking. Over the past decade, cloud computing has become more cost-efficient, secure, and reliable. The major providers in the industry are now investing heavily in their hardware, software, and global networking infrastructure to obtain more market share, which has resulted in unparalleled performance. Healthy competition is always a win for consumers and partners as this drives costs down and requires them to constantly innovate to stay ahead.
Typically when we think of cloud computing providers we are referring to the three giants in the industry: Azure, Google Cloud, and AWS. Today we’re going to compare just two of them, Google Cloud vs AWS. We exclusively utilize Google Cloud Platform here at Kinsta, but we’ll try to keep this article as unbiased as possible and explain everything in layman’s terms. There are definitely some advantages and disadvantages to both providers. Trust us, we’ve had our own share of challenges! No matter which provider you choose, you’ll always encounter issues at some point along the way.