changing my password to 2048 char

Will always prefer Baskerville.

Dunning-Kruger ensures that there will be countless people who suddenly have a background in macroeconomics and public finance.

Windows11 anecdotally has some distinct glitches on systems that run multiples of certain types of pro audio devices. Because pro audio is the single application for which I use Windows, and in fact the only reason I've *ever* used Windows at all, this is of enormous concern for me. The only truly annoying thing I've noticed is that as a side-docker, I can't handle the fixed location of the taskbar. But as strictly a single application user I really don't want a desktop environment at all, just a host OS for my application and maybe a terminal console for file management and administration.

I've never run Windows for anything else real. Linux was either my 4th or 5th Unix, depending on whether Coherent counts. I went straight from the minicomputer world of the 80s to the Unixes of the 90s and was an early adopter of Linux, which works for absolutely everything I do except pro audio. I know Apple is a thing. I know Linux audio is a thing, I've had a hand in developing it. I don't even hate Windows, but I dislike forced platform changes.

We hate Angular more than we hate Drupal. Survey results seem accurate based on that alone.

The first cannabis prohibition in the US was a law passed in 1910.

Stories like these remind me that marijuana is still illegal in some places.

You're saying that they shouldn't report on election results? Or are you wishing they would use some other source of information other than the actual election results?

"The CRA" didn't take a side. You had a court judgment? Or a civil court declined to grant you a hearing?

Our solar system has a foot in the grave anyway. Why should we care about anything?

Many situations require the encryption of SSL without necessarily requiring the authentication of SSL. This is the case when the risk is more from something like accidentally or casually disclosing sensitive information and there is little or no risk of intentional attack, but where there are liabilities for routine exposure. This scenario isn't really a job for SSL, but what else do we have to work with?

It would not surprise me to learn that in some form, software developed in the 1960s is still in use today.
This is coming from someone who had to hack Fortran code as recently as 2009.
Wouldn't surprise me one bit.