Open-source project
Schneegans/Burn-My-Windows avatar
Schneegans/Burn-My-Windows

burn-my-windows: three licences in one repository and an effect table with no previews

🔥 Disintegrate your windows with style.

3,107 stars115 forksJavaScriptGPL-3.0

At a glance

What is it?
Burn-My-Windows is a desktop extension that animates windows away, with an effect named after a fiery one, built for two desktop shells from one repository. Its release numbers are bare integers and its readme carries a different licence from its metadata, and the table that sells the effects has an empty column where the pictures should be.
Who is it for?
Burn-My-Windows suits someone who has decided they would rather watch their windows burn than close them, and who is on one of the two shells it targets, since the extension is per-shell and the default branch has a hard floor on the newer one. It is a poor fit if you want a feature request answered quickly, since the effect list is long and the author's own framing is that he expects bugs.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 14 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Schneegans/Burn-My-Windows3,107 ★ · +27
Star history
Repository2026-09-242026-11-13
Schneegans/Burn-My-Windows3.1k3.1k

27 Stars in the last 50 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three licences in one repository and a per-file licensing setup

Four different licensing signals appear in this repository and none of them is the whole story. The repository's own metadata names version 3 of the GNU General Public License. The readme file carries a Creative Commons attribution header, which is the licence you would expect on prose and is not what the metadata says. The build file carries an MIT header over its source. And the tree contains a licence file, a separate directory of licence files, and a configuration file for the REUSE specification, whose badge is in the readme's link row. That combination is the per-file licensing convention: instead of one licence for the repository, each file declares its own, and the configuration file covers the ones that cannot. So the accurate description is a repository whose metadata reports a single licence and whose files declare three.

The effect list has twenty two entries and an empty preview column

The readme's main content is a two-column table. The left column names an effect and describes it in one sentence; the right column is headed preview and is empty for every row in the visible portion. The names run alphabetically and the list is cut off partway through, so there are at least twenty two and the reader is shown none of them. The descriptions are where the personality is. One dissolves windows into a cloud of dust, one paints or erases them with a thick brush, one hides pixels randomly until the window is gone, and one is described as a ridiculous effect that teleports windows between dimensions. One references a cartoon series, one references a plumber from an Italian game, and one is a set of green letters whose colour is described as actually configurable. Whatever else this page is doing, it is selling twenty two named effects with adjectives rather than with pictures.

The fire effect is a shader now and not the particle system it was

The effect the project is named after is described in a sentence that explains a redesign. It is called the classic effect inspired by a compositing tool, and then it says the implementation is not what it used to be: it is done with a shader written in a shading language rather than with a particle system like in the old days. That matters for anyone deciding whether to expect the original look, because a shader and a particle system are different techniques with different performance profiles and different failure modes on a machine without hardware acceleration. The readme gives a second account of the same lineage near the top, where the author says that when he released a cube effect for GNOME, people asked him to revive the burning windows feature from compositing-tool history, and that this version is both less useful and more hacky than the cube, with bugs expected.

One entry in the table says the effect is less snappy

Most of the effect descriptions are one sentence of pure advocacy. One is not. The second fire effect is described as a less snappy but definitely more fancy take on the fire effect, which is the table conceding a performance difference against its own sibling. Two other entries concede things of a different kind: one says the effects that beam windows away use different transporter technology to produce an alternative visual, and the one that materialises windows says it uses the system accent colour by default, which makes it the only effect in the visible list that inherits a colour from the desktop theme rather than carrying its own. Those three admissions are the most useful lines in the table, because they are the only places where the page tells you what choosing one effect costs over another.

The default branch needs GNOME Shell 45 and older versions live elsewhere

The first callout on the page is a version constraint, and it is stated as a hard rule rather than a recommendation. The code in the default branch is for one shell generation and later, and anyone on an older version is directed to a separate branch named for the range of versions it serves. Since the extension also supports a second desktop shell, a reader has to work out which of the two they are running before they work out which branch they want, and the page does not order those two questions for them. The extensions listing in the link row is the GNOME extension directory entry, which is where the packaged version lives, so there is a third path again: install from the directory rather than build from source at all.

The build file is written to be copied into another extension

The first comment in the build file after the licence header explains its own shape: the name and the domain are defined in one place to make the file easier to port to another extension. Those two variables produce everything else. The name is the lower-case project identifier, the domain is the author's own hosting domain, and together they form the extension's identifier and the name of the archive that gets built:

make
NAME     := burn-my-windows
DOMAIN   := schneegans.github.com

So the same build file, with two lines changed, would package a different extension with a different identifier, which is how one maintainer ships a family of related extensions without maintaining a family of build files. The file also computes the file lists with shell wildcards and find rather than listing them, and derives the compiled translation catalogue paths from the source ones by substitution, so adding a language is a matter of dropping a file into the translations directory.

The archive is an explicit file list and the KWin backend is not in it

The build file enumerates what goes into the distributed archive rather than copying a directory, and the list is short. It contains the JavaScript sources found by wildcard, the compiled translation catalogues, one compiled resource bundle, two settings schema files whose names are interpolated with the extension identifier, the extension metadata file, and the licence. Every entry is a file or a glob, not a directory, which is what keeps the package from carrying tests, documentation, build scripts and the second shell's backend. The tree has a separate directory for the KWin implementation and it is not named in that list, so the archive this build file produces is the GNOME one. Whether a separate file is used for the other shell is not visible on this page.

Installing is one command and a manual shell restart

Two targets cover the user's whole lifecycle and they are four lines long in total. There is a target that builds the archive without installing anything, described in a comment as the only bundling step, and a second that builds the archive and then runs the shell's own extension installer against it with a flag that forces over an existing copy. It then prints a message telling you the extension installed and that you should restart the shell yourself with a specific key chord and a single letter. Uninstalling is the same tool with the uninstall subcommand and the interpolated identifier. The restart instruction is the one detail worth flagging: there is no automatic reload, so a user following the instructions has to know the chord, and the message tells them rather than the code doing it.

Editorial conclusion

Burn-My-Windows suits someone who has decided they would rather watch their windows burn than close them, and who is on one of the two shells it targets, since the extension is per-shell and the default branch has a hard floor on the newer one. It is a poor fit if you want a feature request answered quickly, since the effect list is long and the author's own framing is that he expects bugs. Before you install it, check which shell and which version you are on and take the matching branch, and read the per-file licence headers rather than the repository's licence field, because the documentation, the build file and the code are under different terms.

Frequently asked questions

what is burn my windows

It is a desktop extension that animates windows away instead of closing them, built for the GNOME shell and also for KWin. The readme's table names at least twenty two effects, from an apparition that sucks windows into a void, through a broken glass effect whose shards fly away from the pointer, to a fire effect implemented with a shader rather than a particle system, and one that dissolves windows into dust.

how to install burn my windows

The build file's install target builds the archive and runs the shell's extension installer against it with a force flag, then prints a message telling you to restart the shell using a two key chord followed by a single letter. There is also a packaging listing in the GNOME extension directory and an install path that builds the archive without installing it, for people who install by hand.

how to install burn my windows kde

The extension has a separate top level directory for its KWin implementation, and the readme heading names both shells. The archive that the build file assembles is enumerated by file and does not include that directory, so the KWin variant is packaged by a different route than the one described on the page. The page gives no separate install command for it.

Which versions of the GNOME shell does the main branch support?

The first callout on the page says the code in the main branch is for one shell generation and later, and directs users of older versions to a branch named for the range it serves. The repository is not archived and its last push is dated 2026-09-30.

What licences apply to burn my windows?

Four signals appear and they differ. The repository metadata names version 3 of the GNU General Public License, the readme file carries a Creative Commons attribution header, the build file carries an MIT header, and the tree contains a licence file, a directory of licence files and a configuration file for the per-file licensing convention, whose badge is in the readme.

Is there an alternative to burn my windows, and can I make Windows look like GNOME?

The page answers neither. It names no alternative project, and the only other thing it links is the author's own cube effect, which the readme credits for the request that led to this extension. Nothing on the page concerns making the Windows operating system look like the GNOME desktop.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. Schneegans/Burn-My-Windows on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/schneegans-burn-my-windows.svg)](https://hysenlabs.com/projects/schneegans-burn-my-windows)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/schneegans-burn-my-windows.svg)](https://hysenlabs.com/projects/schneegans-burn-my-windows)

Was this useful?