DEV Community: IroncladDev

How NOT to behave in Open Source

IroncladDev — Sat, 28 Feb 2026 15:12:35 +0000

A Vegan walks into a smokehouse,
walks up to the counter,
asks to see the manager,
demands that the restaurant offer vegan-friendly options,
hands the manager a cookbook full of vegan-friendly recipes,
gets rejected,
walks out of the restaurant,
and leaves a 1-star review.

To the average human being, appeasing the specific demands of an individual who has no regard for your time, work, or budget sounds ridiculous. On the other hand, the average human being does not take into consideration someone else's time, work, or budget.

As an open source maintainer myself, I have come to appreciate the strenuous work of the giants whose shoulders I stand on. I want to surface how much these people are doing, and I want to help you appreciate and contribute in as frictionless a way as possible.

Who is this article for?

Whether you are getting started in Open Source, a vibe coder, or an opencl*w instance, hopefully this article will do you some good.

This article assumes you have a basic understanding of a version control system like git, and that you have some familiarity with a git hosting provider like Github or Gitlab.

How to be a headache for Maintainers

Let's talk about some ways you can be an absolute pain to open source maintainers.

Side effects may include getting bad publicity on social media, getting banned from the project, or just getting butthurt after your issue or pull request was rejected.

How to get your Issue rejected

Submit an extremely vague bug report

Request a port to a different language/framework/operating system

Pitch a large-scope feature request

Open a vague PR for the sole purpose of trolling

How to get your Pull Request rejected

Vibe code a massive feature implementation

Open a Pull Request that adds your name to README.md

Being a Civilized Contributor

Now that you have a general idea of what not to do, let's go over some ways that will help you work more seamlessly with open source maintainers and contributors.

General Etiquette

Applies to both issues and pull requests.

Express your Gratitude - Open Source Software may be free to use, but time isn't. If a project is important to you or has helped you, express your gratitude to the maintainers, because that's what keeps them going. If you can spare a few dollars, consider sponsoring the project.

Search and Read - Are there any duplicate issues similar to yours? Are there any workarounds? Has someone written a blog post to fix the exact issue you're dealing with? Finding an existing solution or a workaround is more valuable than getting a delayed response.

Be Verbose - Provide as much information as possible. Cross-reference relevant issues and Pull Requests. Make it easier for the maintainer(s) to help you.

Issues

Issues count as contributions on your github graph for a reason. Stop thinking of issues as customer support. Start thinking of issues as a way to positively contribute to the project.

Before you open an issue, take into consideration how much engineering effort is available. How many active maintainers are there? When was the project owner last active? How many open issues are there?

Avoid introducing unnecessary overhead - Will your issue provide a solution if completed, or just introduce more problems and overhead? For example, requesting Windows support for a Mac and Linux-only application will come with its own set of problems.

Estimate the impact - Does your issue describe something with a large impact that affects the majority of the consumer base, or is it very specific to you? Maybe a workaround, forking the repository, or a dependency patch will work better than waiting a few months for the next version to be released.

Pull Requests

When opening a pull request, it is important that you adhere to the style guides and conventions specified in the project as much as possible.

Throwing code at a repository and hoping it gets accepted usually doesn't work. Taking the time to make a clean and beautiful Pull Request shows the maintainers that you really want it.

Retain clean commit history - Take 30 minutes to learn how to squash, describe, reorder, and rebase commits. Split your changes into small, very verbose commits that cross-reference other related issues and pull requests. Explain why changes are being made, not just what they do.

Automated Testing - If there is a testing environment in the project you're contributing to, it doesn't hurt to write a unit/integration test to ensure correct behavior.

You as a Maintainer

Being a maintainer or project owner comes with a set of responsibilities. If you want to build a reliable piece of software for people to use, you should dedicate the time and effort to keeping it that way.

Accepting Contributions - You as a maintainer should not blindly accept contributions from external contributors without testing and thorough review.

Be Transparent - When accepting, rejecting, or commenting on contributions, let the contributor know why you came to your decision.

Be Organized - It is extremely important that you as a maintainer are organized in how you manage issues, pull requests, and write commits. Break changes into PRs and commits and describe them in detail. Cross-reference issues and pull requests. Don't close an issue as "completed" if it isn't completed.

Being "nice" is not your focus - It's okay to be blunt as long as you are verbose. Don't give external contributors the impression that you're going to accept their every contribution. Rejecting a contribution might hurt someone's feelings but won't hurt your project. It's okay to say "no".

Delegate work when necessary - It is unlikely that you can work on your project full-time, because OSS usually doesn't pay the bills. If a past contributor or someone who opened an issue expresses interest in your project, ask them to make a PR which you can later review.

Archiving - if you can no longer work on an open source project of yours due to personal reasons, archive it to let people know that development has ceased.

Conclusion

This article just scratches the surface of what all is in being an open source contributor and maintainer.

If you got something out of the article, I hope you take the time to apply it and make the lives of open source contributors and maintainers easier.

We're all in this together. Let's share the load.

A Stalemate Between Software Jobs VS AI

IroncladDev — Fri, 30 Jan 2026 19:07:34 +0000

AI innovation - an unstoppable force, meets an immmovable object - software jobs. So many arguments. Endless predictions. Countless hours wasted. Neither side is winning.

If you've read my previous articles and some of my tweets, I am very skeptical to AI and do not hold to the belief that software jobs will be replaced by it.

However, the goal of this article is not to win an argument, prove a point, or filter through the noise. I want to listen to the noise, find where it's coming from, and study why the noise is being made.

Idle Observers

I will start out by locating where the noise is coming from.

The majority of people who take part in the argument about AI and Software Jobs are what I refer to as idle observers - people who cheer for their side without taking any course of action to back their beliefs.

Those who hold to the belief that software will not be replaced by AI are just sitting ducks, waiting for the so-called "AI Bubble" to pop. Sitting idle and hoping to outlast the enemy without taking any course of action whatsoever is not winning. The AI hype train has dragged on long enough to safely assume that there will be no rapture for those who think they know how to code.

On the other side, people who heavily use vibe coding tools as a means to acquire dopamine and clout while boldly making a claim backed by nothing isn't doing much either.

Binding Factors

Now that we know where the noise is coming from, let's talk about why the noise is being made.

In the ocean of opinions on this topic, I've found that the two primary factors in this argument are Value and Risk.

Value

Many people don't realize that the term "value" is subjective. In the same sense that a diamond offers little to no value to a starving animal (eating a diamond may provide little relief to a very unintelligent organism), the best sorting algorithm implementation offers little to no value to the average end user.

Since the argument of AI potentially replacing jobs revolves around the rapid generation of software projects, I will take a moment to cover the value of software.

The Value of Software

In software, there are incompatibilities across operating systems, CPU architecture, and web browsers. A Windows-only application won't be of any value to a Mac user, and vice-versa.

A content creator may find specific video editing software valuable enough to (God forbid) pay Adobe for it, while others look for alternatives or don't edit videos at all.

If a software engineer finds a tool that drastically improves his workflow, chances are he probably won't tell his grandmother about it (or any non-technical people for that matter) because he knows it will be of no value to her.

AI tools are extremely versatile and can provide immediate value to most individuals, espicially when it comes to generating code. Since AI tools can fit the needs of most individuals very closely, people who use them are more likely to share them with others.

Sharing things that can potentially help others is an act of kindness, and is not necessarily a bad thing. Unless that thing is an AI slop video generator.

In conclusion, the reason why there is so much hype around AI is because people find value in it.

Risk

Risk pulls in the opposite direction of Value when it comes to AI-generated code and is primarily what's keeping software jobs rooted in place.

Both humans and AI are unpredictable. An employee could randomly choose to steal workplace equipment or commit fraud on the job. Likewise, an LLM may choose to make up something or refuse to tell you something it deems harmful.

Most people would agree that hiring an experienced worker will result in less risk than hiring an intern. In fact, experienced workers are paid more than their inferior counterparts because of their ability and the lower chance of risk.

Risk cannot be measured, but it can be reduced with incentives.

Incentives

A soldier defending his country from the enemy is more likely to fight harder because he has something to fight for.

Likewise, employees are willing to work because of the incentive to get paid.

The reason why most people don't play life-threatening practical jokes in the workplace or steal workplace equipment is because they want to continue to get paid.

Unlike employed humans, LLMs have nothing to lose. No matter how aggressively you form its instructions, it has no real incentives to perform better.

This is the same reason why communism doesn't work. If someone has all their basic needs met regardless of their contribution to society, there is no real motivation to contribute.

Conclusion

I hope this article gives you a better understanding of both sides and gives you a topological view of how silly we are butting heads against each other whilst accomplishing nothing.

I want to stop fighting about AI and software jobs. Let's be at peace with each other while we build great things.

(This does not apply to Communists. I will not be at peace with Communists)

Original Article Link: https://x.com/IroncladDev/status/2017006861300494603

It's hard to make money from software alone

IroncladDev — Thu, 29 Jan 2026 23:03:36 +0000

There is more money to be made in the real, physical world than in the Software Industry. This is an undeniable fact that will remain true until the end of time. I say this with confidence because you can't eat a computer program.

In 2020, I had dreams of owning a successful software business while working at a relaxed desk job. Fast-forward to the present day, and I'm having my doubts.

Software as a Product

Video games, desktop apps, mobile apps, streaming services, SaaS products, and Enterprise Software are some of the more prominent digital products we are familiar with.

Unlike physical products, software is easy to clone and distribute. In order to make a profit, software companies gate certain features of their software by using a paywall and a database to track customers.

Failure to implement the necessary paywall measures usually results in piracy and exploitation. Piracy itself does not cost the company anything since the cost to create and distribute a new copy of a program is virtually nothing for both parties. Exploitation, in terms of bypassing a paywall, can be different if paying users are permitted to use services that are more expensive to maintain. Both piracy and exploitation can result in a loss of sales and customers.

The majority of software companies are usually closed-source to prevent people from cloning, running, re-distributing, or exploiting their software.

Indie Hacking

Indie Hacking, also known as "Independent Hacking" or "Indian(s) Hacking", refers to selling a digital product as an individual without relying on VC funding. I will never understand how the word "Hacking" got into the term, but it is what it is.

To begin Indie Hacking, you must start a new side project. To start a side project, you must first have time. Mentioning that you are "working on a side project" implies that you either have an existing project or are employed.

Most indie products end up in abandonment due to lack of sales, or lack of time to maintain it. A lot of people blame this outcome on "Marketing".

In reality, the success of an indie product is affected by a variety of factors such as marketing, etc.

Ideas

The average person formulates more ideas than he implements, which is arguably a good thing.

Sellers and builders in the software market tend to highlight that "the idea is what matters most". This is sadly true due to the fact that most end users simply hold to the excpectation that a digital product should work.

The market for physical products is different, as most people would choose to buy goods from a brand renowned for its exceptional quality rather than a brand with mediocre quality.

Ideas and AI Agents

Thanks to AI Agents, non-technical people are now able to bring their ideas to life. This creates an uptick in the overall supply of digital products, saturating the overall market as well as your search results.

Selling a digital product without putting in the effort to build it sounds great to most people. Combine that with the average end user who doesn't care about the quality of software, and you get """products""" and """businesses""" built for end users, by end users.

Marketing

Marketing independently is hard, especially if you're starting out. A lot of indie hackers think of marketing as advertising their products on social media in hopes of gathering interest and gaining a few potential customers.

To understand marketing, you must first understand the market. I would recommend reading Basic Economics by Thomas Sowell before trying to seduce someone to enter their credit card details with fancy screen.

As I mentioned earlier, the supply of digital products has been increasing at a rapid rate, partially due to Vibe Coding. Your best luck is probably in meeting demand instead of creating non-existent demand or further saturating the market.

I am not a marketer, and at the time of publishing this article, I am less than halfway through the largely thiccc book of Basic Economics. I will refrain from giving any (poor) advice on marketing to avoid embarassing myself.

Hosting

Hosting is not a new challenge in indie hacking.

It's surprising how many people don't realize that hosting costs money. Regardless of whether you are hosting a web application or hosting your app on an app store of some kind, you'll probably end up paying something.

Larger companies such as Cloudflare, Vercel, and GitHub can afford to use their profits to host projects on a free plan to a certain extent. Even if you manage to make a profit off of your digital product on a free tier, the pain of migrating to another service will usually keep you as a customer.

Although you may get the impression that your code is living rent-free on a vercel subdomain, it is quite the opposite.

You could go for the alternative of hosting your code on your own machine, but that leaves you vulnerable to spam attacks as well as a single point of failure.

Actually you should just use Hetzner. I also recommend Heckler & Koch, another great german business like Hetzner.

Freelancing

Freelancers include developers, designers, artists, and other people who produce digital products. Freelancing takes more work because each customer usually has a unique request.

Freelancing guarantees some amount of profit as opposed to a standalone indie product because customers bring their demands directly to the supplier/producer. The cost per unit of output is usually higher than software that can be cloned and supplied with little effort.

Freelancing & AI

Vibe Coding tools, image generation models, and video generation models have gotten good enough to satisfy most people. Compute is cheap compared to human labor. As a result, the market for freelancing has probably been affected in a similar manner to that of the Indie software market in terms of high supply and low demand.

The only upside I see from this is that furry artists have probably experienced a loss in customers and sales. Unless AI somehow manages to drive them to extinction, I will hold to my opinion that AI is generally a bad thing for humanity as a whole.

Open Source

The terms "Open Source" and "Money" don't really fit together. Most open sourcs projects are free to use.

I will not be covering public repositories that use a license preventing the unauthorized distribution of modified copies because they are weird, cringe, and shouldn't be public in the first place.

Sponsorships

Most actively-maintained open source projects are upheld by sponsorships, which are donations from individuals and/or companies. Sponsorships, unlike contracts, can be cancelled at any time. Nobody is obligated to sponsor an open source project even if they use it.

As we have seen with Tailwind CSS, Adam Wathan (the creator of tailwind) realized that sponsorships were not enough to support the development of the project at its current state. This resulted in a layoff of 75% of the engineering team. Thankfully, other tech companies flocked to support it with donations.

Very few open source projects have a large enough rate of adoption to even get sponsored.

Sponsorships are not a stable source of income and should not be treated as such.

Employmment

The job market is a steaming pile of garbage. The demand for junior and entry-level roles is drastically decreasing, and keeping your job is a challenge. Big tech companies perform layoffs on a regular basis, and everyone else usually avoids hiring for new roles.

Having a full-time role as a software engineer is probably the most stable form of income out of the above. If you have time to spare, you can leverage that time to build a side hustle at the cost of burnout.

I don't have too much to cover on this particular topic. For those who manage to get hired, just try to stay where you are or move up the ladder.

Final Thoughts

I don't mean to be pessimistic, and I certainly don't want to give the impression that I'm jealous/coping about the success of people like LevelsIO or the owners of successful tech companies. In fact, I'm happy for their success and I would be happy for yours too. The cold, hard truth is that most of the success stories you see are outliers that offset the average.

I love programming and I hope it's something I can continue to do for the rest of my life. I would eventually like to start and run a business while doing what I love best, but the current state of things doesn't look very promising.

Maybe I'll pivot to work for a company whose primary source of revenue comes from physical products.

Or I could just become a gunsmith who does farming and MMA on the side.

Original Article URL: https://x.com/IroncladDev/status/2011542744989077863

The AI Movement is a Parasitic Cancer to the Software Industry

IroncladDev — Tue, 27 Jan 2026 20:14:50 +0000

It's been almost five years since I've posted on this site. I thought I'd start again by cross-posting my newer articles from my Twitter

Original article link: https://x.com/IroncladDev/status/1997120236777013271

Hopefully you'll get something out of this one. Enjoy.

Three years I've waited for AI to show its potential and practicality. Today, I watch in horror as it consumes and lays waste to the industry I know and love.

With great compute comes great responsibility, and the people with the most compute are anything but responsible.

An infection, not a bubble

Some people refer to the AI hype as the "AI Bubble" due to its rapid rate of expansion. I instead prefer to describe it as an infection.

If you paid attention during biology class, you will remember that parasites, viruses, and bacteria need a host to feed on before reproducing and spreading. The term "Bubble" seems inaccurate, because most bubbles are inflated with a single, external source.

Pictured: the AI bubble conspiracy theory illustrated by a flat earther

Despite being a major cornerstone of the industry, NVIDIA itself isn't largely responsible for aggresively shoving AI into both consumer and developer software.

The Toll on the Software Industry

You all have seen enough people glazing and sugar-coating AI, so I will not be taking a moment to do so.

Note that I use the term "Software Industry" instead of "Tech Industry". This is because I do not build rockets, solder electronic components, or work as a slave in a bauxite mine.

The Job Market & Workplace

Disclaimer: the following is my observation of people who work in software-related companies that advocate for and heavily use AI. This is not financial advice

The most obvious and undeniable side effect of AI being made publicly available is the declining job market and workplace.

Recruiters have started to leverage AI for filtering out candidates with boring resume pages. To combat this, job applicants started using AI to build their resumes. This back-and-forth quickly devolves into a tiresome battle of prompting on both ends. As a result, the bar for entry level software-related roles rises significantly higher.

Lazy Employees who try to divert their workload to LLMs eventually end up de-valuing and ousting themselves as a leech on a salary. In the eyes of the average corporate overseer, the only difference between a local prompter and a foreign bangladeshi prompter is that one costs 1/4th as much.

When a Non-technical Manager is paired with vibe coding tools, the result is usually a violent chemical reaction (dopamine overdose) that ends up with heavier workloads, people getting fired, and higher expectations.

In the end, managers are essentially end users with elevated context and permissions.

Marketers have become addicted to using the term "AI". Failing to mention the term gives them the impression that their social media post or campaign won't appeal to the masses. It seems that most of them put more trust in a two-letter abbreviation they don't understand than their own marketing skills.

You can also thank marketers for the increased number of advertisements crammed into every possible area in consumer software.

The Decline in Software Quality

The average quality of software is declining. The tools you once knew and loved reward you with ads and AI features you never asked for.

"Software Quality" is subjective. Multiple factors such as implementation, code cleanliness, and ease of use come into play. There are also different kinds of software which I will try to cover here.

Mainstream Consumer Software is not by definition "good software" and will never be. The average consumer cares only that the software gets the job done. An intrusive AI banner is just another thing to complain about.

There's no point in having hope for mainstream consumer software. No matter how advanced AI gets, I say with confidence that there will never be a version of Windows that is considerably fast and doesn't crash all the time.

Buckle up, it's only going to get worse.

Enterprise Software is a dumpster fire that is usually beyond saving. By the time a company starts offering services to businesses and organizations, it means that they weren't profitable from individual customers alone.

After switching to a more profitable customer base (primarily consisting of micromanagers), enterprise software companies begin to taylor to them by adding a bunch of unnecessary low-impact features.

One thing enterprise companies are very good at is adopting AI, which is not a good thing. People who work in enterprise companies are probably being bombarded by AI workflows, AI-generated demos, AI internal tools, and forced to work on AI features targeted to the customer base.

Once an enterprise company pivots and makes AI a cornerstone of their service(s), it usually means they are about to do a round of layoffs and slowly die out.

An example of this is JetBrains, a company that started out with a mission to build a good IDE. They pivoted to enterprise and ultimately ended up breeding AI Agents with the descendents of IntelliJ Idea. The only legacy they left behind is JetBrains Mono; the best font for programming in Neovim.

The Software Market is completely saturated with vibe-coded slop. You can't scroll Hacker News, Product Hunt, or pretty much anything for that matter without running into something related to AI. Search engines are clogged to the brim with AI-generated websites gaming SEO. A lot of investors won't take interest in a project if "AI" or "Agents" doesn't appear in the landing page header.

Large companies like Github and Vercel sort of fall in between consumer, developer, and enterprise software. They are very centralized, and try to use vendor lock-in techniques to keep you hooked.

After the word "copilot" was trademarked by Microsoft, Github seems to have taken up the side gig of shoving it down peoples' throats via ad banners and inserting it into commonly-used UI elements. The team behind the Zig Programming Language got fed up with all this tomfoolery and migrated to Codeberg for good

The Vercel platform itself isn't as aggressive when it comes to ad banners, probably because they realize the obvious fact that it turns people off. However, they are definitely leveraging their monopoly on Next.js and other open source projects towards vibe coding.

A Parasitic Cancer

Everyone hears about how AI can be used for empowering humanity, automation, and replacing difficult jobs. All I've seen is talk, hype, and big corporations taking interest without any promises kept.

The entire existence of the AI movement revolves around mass adoption and money. The movement is exploiting the Software Industry for every last penny, and it will stop at nothing.

The people pushing for AI do not strive to make better software.
They do not care about the software engineers that they depend on.
They even have the audacity to compare programmers to an LLM with write access and a shell, and are actively trying to replace them.

Vibe Coding

Vibe Coding has spread across the entirety of tech like a wildfire and continues to assist humans spit out the most horrific code known to man.

Chances are, if you're using an AI agent to scaffold something, you probably don't have the intention of building good software in mind.

I don't really concern myself with programmers who do vibe code. I just won't review their code.

I use the term Vibe Coders to describe non-technical people who refuse to learn how to code and use vibe coding tools to derive dopamine and clout. People who refuse to put in the blood, sweat, and tears it takes to do something really shows how dedicated they aren't.

If you task someone who doesn't code with vibe coding their dream SaaS startup, you will only ever see them request new features, request UI changes, and fix bugs. The end result will be a bloated application that does a lot of different things poorly.

Lastly, I am a strong believer that new programmers should not use vibe coding tools. I would encourage new programmers to read the manual, write down the examples, run them, and experiment with them. I also encourage using an AI chat to ask questions about how things work along the way if it's unclear.

What can you do?

I want to conclude this article with a call to action instead of just dumping my thoughts out and calling it a day. Just by changing your mindset a bit, you can make a difference.

Make it a goal to write good software that lasts for years to come
Find a skill you're good at, refine it, and shoot to become the best. The backbone of software is upheld by people who do one thing well
Share good software with others
God gave you a unique mind that nobody can replicate. Use it.

Unfortunately, the AI slop will continue

But well-written and well-maintained software will prevail

And you. So will you.

Smooth Scrolling with React & Framer Motion

IroncladDev — Mon, 14 Aug 2023 20:57:34 +0000

Scrolling through a website especially with a notched mouse wheel is typically jumpy and harder to navigate.

Smooth Scrolling, or spring scrolling adds an animated touch to the traditional mouse scroll.

If you've never experienced smooth scrolling before, try out the Live Demo.

Concept

Consider the viewport window. When a bunch of HTML elements combine to a size taller than the window, it overflows and can be accessed when you scroll down.

To override the default scroll, we need to wrap the content in a fixed element we can control.

Finally, we will create an invisible spacer (div) equal to the scroll height of the content. This will trigger the browser's default scroll bar.

Setup

Create a React Typescript Repl on Replit to get started.

Install Framer Motion with npm install framer-motion.

The Component

The <SmoothScroll/> Component will wrap all the HTML elements we want to incorporate in the Smooth Scrolling effect.

export default function SmoothScroll({
  children
}: {
  children: React.ReactNode;
}) {
  return <></>;
}

Scroll & Spring Values

Import the following hooks from framer-motion.

import { useScroll, useSpring, useTransform } from 'framer-motion';

In the SmoothScroll component, destructure scrollYProgress from the useScroll hook.

const { scrollYProgress } = useScroll();

Next, use the useSpring hook to apply the smooth effect to the scrollYProgress value.

const smoothProgress = useSpring(scrollYProgress, { mass: 0.1 })

Content & Spacer

Add the motion component to the existing import from framer-motion.

- import { useScroll, useSpring } from 'framer-motion';
+ import { motion, useScroll, useSpring } from 'framer-motion';

Skip down to the component's return statement. Return an empty <div> element and a <motion.div> element which renders the children prop as a child.

return <>
  <div style={{ height: contentHeight }} />

  <motion.div
    className="scrollBody"
  >
    {children}
  </motion.div>
</>

Create a contentRef react reference via the useRef hook and a contentHeight state with useState.

import { useState, useRef } from 'react';

...

const contentRef = useRef<HTMLDivElement>(null);
const [contentHeight, setContentHeight] = useState(0);

Assign the content wrapper the contentRef.

<motion.div
  className="scrollBody"
  ref={contentRef}
>
  {children}
</motion.div>

Use the style prop to make the spacer have a height of contentHeight.

<div style={{ height: contentHeight }} />

Resize Handler

When the window gets resized, the height of the content content is likely to change. Since the contentHeight value is a state, we will need to update it whenever the window resizes, and when the contentRef reference updates.

Start by importing the useEffect hook from react.

- import { useState, useRef } from 'react';
+ import { useEffect, useState, useRef } from 'react';

Within the useEffect hook, create and call a handler to set the contentHeight value to contentRef.current.scrollHeight.

Add contentRef to the dependency array.

useEffect(() => {
  const handleResize = () => {
    if (contentRef.current) {
      setContentHeight(contentRef.current.scrollHeight)
    }
  }

  handleResize();
}, [contentRef]);

Finally, add a resize event listener to window in the useEffect hook, and return a disposer function.

useEffect(() => {
  ...

  window.addEventListener("resize", handleResize);

  return () => {
    window.removeEventListener("resize", handleResize);
  }
}, [contentRef, children]);

Put it all together

Import the useTransform hook from framer-motion.

- import { motion, useScroll, useSpring } from 'framer-motion';
+ import { useTransform, motion, useScroll, useSpring } from 'framer-motion';

Create a constant y and set it to the useTransform hook with smoothProgress as the initial value.

const y = useTransform(smoothProgress, value => {
  return value;
});

Visualizing how to calculate the scroll, we will be subtracting the viewport height from the content container's scroll height, multiplying it by -1, and then by value.

const y = useTransform(smoothProgress, value => {
  return value * -(contentHeight - window.innerHeight);
});

Use the y transformed value in the content container.

<motion.div
  className="scrollBody"
  style={{ y }}
  ref={contentRef}
>
  {children}
</motion.div>

Styles

I already fought CSS so you won't have to. Simply copy and paste the bare minimum CSS over and the scroll component will be ready to roll.

.scrollBody {
  width: 100vw;
  position: fixed;
  top: 0;

  display: flex;
  flex-direction: column;
}

Complete 🎉

That's it! All you have to do is add a bunch of HTML elements within the <SmoothScroll /> component.

Nothing better than fifty <h1>Lorem Ipsum</h1>s in your codebase.

Source Code: https://replit.com/@IroncladDev/FramerSmoothScroll?v=1
Live Demo: https://framersmoothscroll.ironcladdev.repl.co

Thanks for reading. If you have any feedback or recommendations for this article, I'd love to hear it in the comments.

Let's get in touch 🤝

🐱 Github
🦜 Twitter
⠕ Replit
🌐 Website

How to send Chrome / Browser Notifications

IroncladDev — Tue, 16 Nov 2021 12:34:51 +0000

It took me a while of looking around StackOverflow and such to find out how to send browser notifications, but it turns out to be really simple. What I'm going to do here is walk you through a tutorial on making a simple notification-sending function.

At first, when the function is called, it will have to ask for permission first, but after that, it will be able to send all sorts of notifications.

Let's get started!!

First, let's create the function. It'll have three parameters. One for the title, next for the message, and the last for the icon.

function sendNotif(title, text, icon){

}

Next, just to be safe, let's make sure the browser supports notifications.

if (!("Notification" in window)) {
  console.warn("Your Browser does not support Chrome Notifications :(")
}

Let's chain onto the if statement with an else if. This statement tests if the notification status is granted or not. If it is granted, it will send a notification.

else if (Notification.permission === "granted") {
  // If it's okay let's create a notification
  let notif = new Notification(title, {
    icon: icon,
    body: text
  });
}

Still, we'll chain onto the else-if statement. Let's add another one. This statement will request permission if it isn't granted or denied.

else if (Notification.permission !== 'denied') {
  //request notification permission
  Notification.requestPermission((perm) => {
    //save permission status
    if (!('permission' in Notification)) {
      Notification.permission = perm;
    }

    //if granted, send a notification immediately
    if (perm === "granted") {
      let notif = new Notification(title, {
        icon: icon,
        body: text
      });
    }
  });
}

And that should be it. Your function should be working well. Let's, for extra error handling, add an else statement at the end of the chain and log the current notification to the console if it isn't denied or allowed.

else {
  console.warn(`Failed, Notification Permission is ${Notification.permission}`);
}

Have fun and don't spam websites or users with notifications.
Happy Coding.