license VS React

I'm working on a clause for my business that would restrict the use of my software by entities that directly or indirectly support or promote fossil fuel usage, and I would love to get some input from HN community on how to draft it effectively.

Here's the draft clause:

“The use of the software is strictly prohibited by any company or entity whose primary or significant activity contributes directly or indirectly to the exploration, production, expansion, or support of fossil fuel resources —explicitly including oil, natural gas, and coal— and related infrastructure.”

A second part could be added to explicit the prohibited activities:

“This includes, but is not limited to, companies engaged in oil and gas exploration, logistical support for fossil fuel extraction, management and operational services for existing fossil fuel production facilities, and initiatives aimed at increasing the output of fossil fuel resources. The prohibition extends to the marketing, promotion, or advertising of such activities, provision of services, technical support, or resources to directly involved entities in the fossil fuel sector, financial organizations funding or investing in related projects or infrastructures. Further, it encompasses entities that consume substantial quantities of fossil fuels and do not exhibit a verifiable commitment to significantly reduce such consumption within an established timeframe.”

The inspiration partly comes from the Climate Strike Software License[1], but I'm aiming for something more encompassing.

I've written more about this on my blog[2], but here, I'm specifically looking for your expertise on the legal and practical aspects of such a clause.

What are your thoughts? How could this be improved?

[1] https://climatestrike.software/

[2] https://jereze.com/blog/no-fossil-fuel-clause/

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Go to https://react.dev/?uwu=true for a surprise.

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Oddly, no info on changelog: https://github.com/facebook/react/blob/main/CHANGELOG.md

In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.

Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.

Basic knowledge of ReactJs

Google Translate and many other libraries break React based sites if they are using refs.

I don't think that point it falls under "written on naive assumptions"

https://github.com/facebook/react/issues/11538

the issue says closed but you can easily catch it in various sites and use cases.

This article serves as your comprehensive guide to mastering the art of combining Bootstrap and React seamlessly. Dive in to uncover the tips, tricks, and best practices to elevate your UI design game effortlessly.

This isn’t an accident; when Meta introduced React Server Components, Dan Abramov explicitly stated that they collaborated with the Next.js team to develop the RSC webpack plugin.