ipacialsection

While this new display certainly seems better (in terms of being able to use 2x scaling instead of my current 1.25x), I'd honestly prefer to have a cheaper option that's just 1920x1280, so I don't have to use scaling at all. I don't care that much how "crisp" text looks.

Not sure why, but a lot of other distros did something just like this in the past (see the comments about WUBI) and no longer do. Q4OS still has a .exe installer though.

I've had great experience with QKSMS on GrapheneOS. Thanks for directing me to the fork, I'm switching to it right away.

Elisa is just the latest (and most actively developed) addition to the long list of music players developed under the KDE umbrella.

It's like an avant-garde version of Turn Left, with the concept taken so much further, it reaches the edge of the universe, loops around, and comes all the way back down to Earth.

Did the episode ever explain why everyone runs away in horror, quits their job, and starts avoiding Ruby when they talk to that old woman, including trained UNIT agents? Maybe we weren't meant to know.

I also found it amusing to think about how little happens in the prime timeline. The ultimate result of this entire alternate life is that Ruby has a weird, but brief, supernatural experience, the Doctor narrowly stops himself from breaking a fairy circle, and they both have a normal day in Wales.

Right now I'd say the best open-source DAW for Linux is LMMS if you want to do everything just on your laptop, or Ardour if you want to use external instruments.

LMMS has some shockingly versatile built in synths, including a port of ZynAddSubFX, supports LADSPA/LV2 plugins, and supports using Wine to run 32-bit Windows VSTs. I'm unsure of Ardour's VST support, but it at least supports LV2 plugins. Either of those, if you install them through your distro, will likely include Calf Studio Gear, an extensive collection of LV2 effects and a couple synths. As for ones that run natively on Linux, there's synthv1, samplv1, drumkv1, and padthv1, though I've had trouble getting them working myself.

I've found some good stuff on the Linux Audio Wiki but IDK how up to date most of it is.

Almost all distros can dual boot, so there's little reason to highlight one as being the best for it. Dual booting is a bit messy and risky no matter what you do, so back up your data first and, if you're new to Linux, look up instructions for dual booting Windows 11 and your chosen distro.

Only one I can think of that does anything special with dual boot, off the top of my head, is Q4OS, which offers a way to install it from within Windows using an app. (It also happens to be tailored towards people familiar with Windows XP or 7, so it should be a somewhat smooth transition for a first time Linux user.) I haven't tried this myself, but I imagine it just expedites the usual steps of dual booting: shrink the Windows partition, then install into the resulting free space (or to an unused disk).

If that doesn't sound appealing, just try any distro recommended as "beginner friendly", like Linux Mint. Tutorials should be easy to find.

1. Create a source control repository containing all your code, and publish it to an online code forge. GitHub's docs might help with this: https://docs.github.com/en/get-started/start-your-journey
2. Choose an open-source license and add it to the repository as a LICENSE file. If you want to require any projects that build upon yours to be open-source too, the GNU GPL is a good choice. If you want to allow proprietary programs to include your library without releasing any source code other than that which is directly based on yours, the GNU LGPL is good for that. If you want to allow people to do whatever they want, even use all your code as the basis of a proprietary program without credit, the Unlicense is a good choice. There are a lot of licenses with different degrees of "copyleft" and attribution requirements in between. Technically publishing with a license file is all you need to do, but there are more things you should do.
3. Create a README text file describing what your program does, and instructing users on how to compile and run it. Consider including more detailed documentation on how to use it, as well.
4. Clean up your code and file layout so that it's as easy as is feasible for other programmers to understand.
5. Promote your project to whoever you think might find it useful!

There's Bodhi Linux, which is basically Ubuntu+Enlightenment.

Lighter, I think. About on par with LXQt or Trinity (KDE 3).

I loved the default theme, the splash screen, all of the customization options, and how lightweight it was, but it's missing some of the conveniences and polish of GNOME, KDE, or even LXQt and Xfce. Using an independent toolkit meant that none of my apps looked consistent, even after trying my best to find a theme that supported everything, and if I explored the settings beyond a surface level things started looking ancient and clunky.

Definitely underrated, and really impressive for how much they could pack into a desktop targeted at older PCs, but still missing quite a bit.

A collection of poker scenes filmed from different camera angles.