Maximizing Microservice Databases with Kubernetes, Postgres, and CloudNativePG
Explore the transformative synergy of CloudNativePG, an operator bridging PostgreSQL and Kubernetes. This article reveals how this open-source stack liberates organizations from vendor lock-in, fostering a seamless microservice database environment and elevating innovation, operational efficiency, and velocity.
SpeedCurve | How to use Server Timing to get backend transparency from your CDN
Backend time can have a big impact on Largest Contentful Paint and other metrics. Here's how to use server-timing headers to find out what's happening inside the black box of Time to First Byte.
A manifesto for small, static, web apps - Ross Wintle
I’m having a lot of fun building small, static web apps. And there are certain principles I’m trying to stick to as I do it. Let’s see what they are… What is a manifesto anyway? As I started writing this, I asked myself: “Is this actually a manifesto? What is a manifesto?” But the definition […]
How to add Monaco to a Next.js app to enable custom user workflows
Allowing your users to create custom workflows increases your platform's value. Here's a simple guide to enable user-created workflows via a browser IDE with Monaco, Next.js, and Subhosting.
Modern CSS Tooltips And Speech Bubbles (Part 1) — Smashing Magazine
Tooltips are a very common pattern used in CSS for years. There are a lot of ways to approach tooltips in CSS, though some evoke headaches with all the magic numbers they require. In this article, Temani Afif presents modern techniques to create tooltips with the smallest amount of markup and the greatest amount of flexibility.
Both Next.js and Remix are highly sought-after frameworks for constructing contemporary web applications using React, yet they diverge in their methodologies and principles. This article aims to assist developers in selecting the optimal framework by comparing various aspects such as routing, data flow, and data mutation strategies.
Why Does 'is-number' Package Have 59M Weekly Downloads?
Why does this simple one-line package have [so many downloads](https://www.npmjs.com/package/is-number)? Is the JS community filled with folks who can't do this simple task without relying on a library? Are they rightfully the butt of all jokes? Have they learned nothing from the `left-pad` fiasco that [broke the internet](https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code)? The answer is more nuanced than that. 'npm' methodology of counting downloads is [admittedly naive](https://blog.npmjs.org/post/92574016600/numeric-precision-matters-how-npm-download-counts-work.html). npm’s download stats are naïve by design: they are simply a count of the number of HTTP 200 responses we served that were tarball files, i.e. packages. This means the number **includes**: - automated build servers - downloads by mirrors - robots that download every package for analysis This has led to some programmers pumping up their download numbers by creating simple packages, and using them in their own packages, and using those packages to create more packages. As a result, these silly utility packages hide beneath multiple layers. Any successful package in the upper layers creates a cascade of increasing download numbers. I don't believe many programmers are using `is-number` knowingly. It just gets included when you use a popular package. In fact, it's there even in my `node_modules` folder. I figured out the chain that led to its inclusion: tailwindcss - chokidar - braces - fill-range - to-regex-range - is-number The last four packages in the chain have been written by the same author. --- Nonetheless, this kind of dependency hell is ridiculous and something should be done about it. Too many packages are getting downloaded, consuming disk space and download time, that should ideally only be a single function or a part of a bigger lodash-like package. There are thirty-seven "is-*" packages in my node_modules folder. That's just bonkers! There are three solutions I can think of: 1. npm should differentiate between direct and indirect downloads. I am not certain if it's possible with how npm works, but downloads triggered by a dependency don't accurately reflect the popularity of the package. People who visit the npm page are usually unaware of how the numbers work. 2. There should be a concentrated effort to replace the packages causing this mess with packages that inline their dependencies. 3. Like [Bundlephobia](https://bundlephobia.com/), there should be a website that lists the total number of packages you'll end up downloading when you include the dependency. Hopefully, it will encourage the community to seek packages with fewer indirect dependencies. Tons of hidden costs come with having hundreds of dependencies, but the JS community has largely ignored them. It's time we made some effort to address the issue.
