In this post, we’ll discuss the concept of types, compare static and dynamic types, and show an unobtrusive type inference package provided by Flow.org.
Facebook developed and maintains Flow. The package provides static typing to normally late-bound JavaScript code, including React code. It provides this analysis to a JavaScript application, even if it is an existing application. Flow operates by carrying out a static abstract syntax tree (AST) analysis of type flows at build time.
Blockchain is all the buzz now. And for good reason! A distributed public ledger that is extremely secure through encryption?! Imagine the millions of applicable use cases. A blockchain can be created and maintained using any modern language.
For the purpose of this blog, let’s dive into a blockchain written in JavaScript. Hopefully, this doesn’t just serve as a simple code example but also gives a very basic understanding of how a blockchain actually works.
Do keep in mind this will be very simplist…
The React Native framework supports an installable mobile application created from JavaScript source code. It is not a React-based web app wrapper. It isn’t a code generator. There is no required application source code in Java, Objective-C, Swift, or Kotlin. Moreover, a single React Native application targets both iOS and Android devices.
In this blog, we show a quick-start that results in an executing application on a phone, within five minutes. That application is live-reloadable, native cross-platform, and written in JavaScript. It is not a web application.
As Keyhole consultants, we are exposed to a plethora of technology stacks and implementations from client project to client project. Particularly with our enterprise clients, great care must go into selecting the best technologies for the company’s technical needs and current landscape. After all, they don’t want to be re-writing the same application in just a couple of years due to lackluster choices and shortage of developers to add functionality.
In this post, we present an open source reference application developed three times using three different frameworks, React, Vue & Angular.
Let’s say you’ve stepped into a React application to make some updates or been involved in building one yourself. You have been at it a while, and feel somewhat comfortable using React, you understand React’s lifecycle and you may be using React libraries like Redux or MobX to some extent.
As with any technology, you start to notice that a few of the pages are looking a little slow. You know performance tuning too early is often a bad idea, but you feel like you might be at that point. After all, in your experience, end users notice even small lags and no one wants that. So what do you do now?
In this blog, I introduce six tips for improving performance and design in your React application.
