I had one of those to charge a bicycle headlight. I gave it away with the bicycle, but in the span of time I had it, one visiting guest borrowed it to recharge a portable generic USB battery pack. So there you go, two product categories known to use that sort of cable!
“Terrible inefficient workflows”, like having to prompt Claude to change one or two words in a file rather than just manually editing it, because it gets confused when the file changes out from under it and will later overwrite the changes?
No, but some are retrocomputing enthusiasts who might occasionally run vintage browsers on non-Y2K compliant systems. The cert in question has a "not before" date in 1998, and Netscape 4.51 hails from around same time.
Probably zero doing anything worth MitMing, though.
Technically, “unified memory” is where both the GPU and CPU have access to the RAM over the same bus, which is different from the older, reviled “shared memory”, where the RAM was always at least one bus hop away from the GPU. But yes, there is a certain amount of spin to it, isn't there? (“You have less total memory now, and that's a Good Thing!”)
For those who haven't made the connection, Cockos, the company who make REAPER, is run by Justin Frankel, previously the founder of Nullsoft, the company who made Winamp. REAPER very much carries the Winamp torch of robust, resource-efficient software, and in the 15 or so years I've used it as a hobbyist, I don't think I've ever lost any work due to the software's fault.
My understanding is that the Qt 6 build system is vastly easier to work with.
Also, Audacity is not the first major FOSS project to successfully migrate from wxWidgets to Qt: Dolphin, the GameCube/Wii emulator, made a similar migration several years ago[0][1][2][3].
The Audacity team imported their existing Qt interface code from a previous project. Depending on the design, the code smell could have a lot of vestigial parts unrelated to the new project.
I have always seen FOSS as the last stop for public domain software. It is supposed to become the stable road future kids walk down to become professionals. The Qt framework is often antithetical to that goal in my opinion. =3
Rule #3: popularity is not an indication of utility.
Kobo devices ship two different rendering engines: the obsolete, appallingly bad Adobe Reader Mobile SDK (RMSDK), and their own, bespoke, WebKit-based renderer. By default, files with an .epub extension are rendered with RMSDK. Consequently, you'll get all sorts of weird issues. Some of the ones I've encountered: I've had cover images not displaying in the library, misbehaving internal links (footnotes), inability to override typefaces/text size.
Easy fix: rename the file to .kepub.epub[0].
Slightly more involved fix: run the file through Kepubify[1] first. This tool makes further tweaks to the books to enable a few other features, like remaining read time estimation.
As a broke teenager, I came to have a G400 much later on in its lifecycle (c. 2007-2008). It did indeed have amazing analogue output quality (kids these days think VGA is inherently blurry, but it can be pretty much indistinguishable from DVI/HDMI if your graphics adapter has a good RAMDAC and you connect the monitor with a high-quality cable). However, my experience with the 3D drivers was pretty consistently terrible. I suspect the card was getting much less QA attention by that point, because one driver release would have broken OpenGL support, the next would break Direct3D, and so on. Very obviously not consumer-focused cards. I remember it extremely fondly nonetheless! Multi-monitor support was not common then, and that card was extremely formative to my lifelong thirst for desktop real estate.
reply