Linking against an older glibc means setting up an older distribution and accepting all the outdated toolchains and libraries that come with it. Need to upgrade? Get ready to compile everything from source and possibly bootstrap a toolchain. I wouldn't call this trivial.
The fact that you need to use a container/chroot on Linux in the first place makes the process non trivial, when all you have to do on Windows is click a button or two.
Wouldn't you target whatever is the minimum "supported" glibc you want to run in the first place?
What is that you need to recompile?
Chroot _is_ trivial. I actually use it for convenience, as I could also as well install the older toolchains directly on the newer system, but chroot is just plain easier. Maybe VS has a button where you can target whatever version MS fancies today ("for a limited time offer"), but what about _any other_ windows toolchain?
Only because of the enormous efforts put in by debian package maintainers and it's infrastructure.
If you're a an indie developer wanting your application to run on various debian based distros but the debian maintainers won't package your application, that's when you'd see why it's called DLL hell, how horribly fragmented the Linux packaging is and why even steam ships their whole run time.
Everything inside Debian is fine. That's most of the ecosystem apart from the very new stuff that isn't mature enough yet. Usually the reason something notable stays out if Debian long term is when that thing has such bad dependency hygiene that it cannot easily be brought up to standard.
I've encountered a few artists who partially used AI in their music making process and the results have been incredible, I would hate to see them banned when grouped with people making completely AI-generated slop... Perhaps a middle ground could be reached? Allow AI generated audio as long as it undergoes significant processing by humans, for example.
"Your band was formed after 2023, we will ignore you even if you aren't AI"
By the end of 2026 the AI/no-AI thing is debate is going to be dead because there will be no way to know the difference. This is almost true right now, it just is going to take the general public a while to catch up.
One distinction which could be made: I would like to see bands that are humans because I want to physically attend and enjoy concerts. If the "artist" has never played a concert I don't want to listen to them. Which expands a whole new grey area..
It should be a choice, not a requirement. With Windows you can get your work done without knowing much about Windows itself, but with Linux you're forced to understand every level of the entire OS so you can debug it first and then maybe get your work done. For an OS built around user freedom Linux sure doesn't give its users much choice on how to use it.
That's quite an authentic looking effect! Using it for charts is definitely not the first thing that comes to mind, but it does make them more appealing in a way.
I'm guessing it could be even smaller if it was designed as a SVG file. Although the glow effect with the fading colors would probably need to be simplified.
It's amazing to see the incredible effort it takes to reverse engineer a synth. While much of the process described in the video went over my head I still found it very interesting to watch. Kudos to the Usual Suspects for not only putting in all that effort but also releasing their findings completely for free.
Side note: does anyone know what the song played at 4:30 is called? It sounds very familiar but I can't remember its name at all.
Edit: I found it, it's "Barthezz - On The Move" but played at a slower BPM.
Offering a plain text version of your website may seem like a novel idea nowadays but I remember a time when pretty much every web page had a printer-friendly version with little to no formatting. I suppose printing web pages has become passé, that is unless you're printing a food recipe.
Thanks for putting together this list, it would be nice to add a short summary next to each link.
I recall on the morning of September 11, 2001, CNN had to completely redesign their site into a text-only version (no images or videos) just to keep up with the strain. Slashdot.org was the only site I went to that was able to keep functioning as-is.
I have to wonder if printing has gone down in popularity, in part, because so many websites handle it so poorly these days. I will sometimes "print" to PDF to save an article I want to read or reference, so I don't have to worry about the site disappearing on me. The quality of these PDFs has dropped dramatically over the years. With some sites it's almost not even worth it.
On several of my previous projects I've been tasked with making the print broken, not just "disabled", to try and force people into the "happy path" where there's a download button. Despite the beforeprint event that would let me trigger the same process.
(I've argued and lost that fight, more often than won it.)
In these fights, did they give the justification for the download button? I'm continuously frustrated by these types of things that go out of their way to break native functionality. Is there a way where they can get extra information and tracking on the user; is that the goal?
To me the "happy path" is the one the user would naturally take, without needing to learn the quirks of each site.
Well, not to entirely leak what I do but the justification is... Salesforce. [0] Omni-anything is a painful, overcomplicated, JS and DB intense process. Generating some PDFs can take in excess of thirty seconds, just because it hits five different objects. And can only be triggered by JS.
reply