The Angular framework has been one of the most popular choices for web developers over the years. Angular brings exciting updates and improvements to enhance developer productivity and user experience with the latest update. In this post, we will briefly explore the new features and improvements introduced in Angular 16.
Software development is an ever-evolving space where languages, tools, and best practices can rapidly change based on the market. Yet there is always a race to do things faster and better than before.
Today, I will be introducing you to Turborepo, a tool that helps manage JavaScript and TypeScript monorepos by leveraging build techniques to avoid duplicate work and maximize multitasking at scale. But first, there may be a couple of questions you’re asking yourself. What is a monorepo, and why use Turborepo?
This blog is a brief overview of CesiumJS, a cool JavaScript client library for visualizing a geospatial Earth map, including artifacts (both real and generated). They eat their own dog food, so their homepage has a declaratively-rendered spinning globe by Cesium.
CesiumJS has a higher-level Entity API as well as a lower-level Primitive API. The API doc can be found here. I’ll point out a couple of interactive source examples that use the entity API; most Cesium apps use it. Cesium also provides open specification 3D Tiles to load, render, and cache on-demand terrain features, artifacts, and building renditions for surface viewing.
There is no IDE or download needed to interact with the material mentioned in this overview. You can interact with the material mentioned with your browser.
Over the years, we’ve seen many approaches to HTTP API design. While REST APIs are still very popular throughout the industry, they offer no inherent guarantees that the client’s assumptions about the response structures will be valid.
GraphQL fills this gap to an extent by allowing client-side code greater control over the resulting structures but at the cost of added complexity. RPC (remote procedure call) frameworks attempt a different solution by sharing generated type definitions between the client and server implementations. What if there was a way to achieve the type safety of RPC by simply inferring the type definitions from the server’s code?
Enter tRPC. Since JavaScript (and specifically TypeScript) can already span across client and server implementations, tRPC allows a client to directly consume structures defined by the server’s exposed procedures. Essentially, you import your dependencies from the server to access these procedures, their return types are inferred and checked at build time, and your client code can confidently consume the returned data.
In this post, we’ll look at how it achieves these goals and what limitations it places on your project stack.
In this blog, I’ll be introducing Vite, a JavaScript build tool that strives to be a faster and leaner development experience for modern web projects.
I found Vite while browsing a Reddit thread and saw several users that were very happy with the technology, so I decided to give it a try myself. I’ve found Vite to be extremely fast, which lends well to making little tweaks and adjustments to the code (even in large applications) and seeing those changes very quickly. But be forewarned, Vite is relatively new and can be temperamental.
