https://www.bleepingcomputer.com/news/security/microsoft-sup...
Back in the late aughts, there was an article from someone at Microsoft talking about how they weren't that interested in going after people pirating Windows in the developing world, because they saw it as an opportunity for turning them into paying customers. Really - that piracy is expanding the Microsoft ecosystem, which back then was important because they viewed Linux on the desktop as a huge threat. (Is it the year of Desktop Linux yet?)
The ease with which Windows is cracked still is probably no accident, but nobody's talking about it. If you're running a business at some point your security folks are going to point out that using cracked software is how you invite attackers inside your security perimeter. (Seriously, down that path lies losing all of your bank accounts)
I know this is a bit of a tongue-in-cheek comment but I would argue that the year of the Linux desktop was in 2022 when the Steam deck, albeit a non-desktop machine, was released. It's a pretty popular console and really forwarded the idea of playing video games on Linux being seamless. The state of gaming on Linux is/was one of the main reason why so many people are/were holding out on Windows, and with a few exceptions of massive games like Fortnite, it's basically here. Adoption, however, is a different story.
https://twiecki.io/blog/2015/11/10/mcmc-sampling/
Note that the point of the markov chain is it's possible to compute relative probabilities between two given points in the posterior even when you don't have a closed form expression for the posterior.
Also, the reason behind separating the proposal distribution and the acceptance probability is that it's a convenient method to make the Markov process stationary, which isn't true in general. (Wikipedia page on MCMC is also useful here).
(This is a massive pet peeve of mine - if you are going to call something "X for dummies", don't bury the lede! Tell me what "X" is as soon as possible, especially if it's an acronym!)
Once you've been using the language for awhile, you begin to dislike the elaborate system of rugs other languages have to sweep errors under. Errors in Go are right there, in your face, and undeniable that the operation you are doing can be faulty somehow. With good error wrapping, you can trace down exactly which of these `if err != nil` blocks generated the error without a stack trace. If it bothers you that much, you can always make a snippet / macro for it in your editor.
my IRC network in the past has had issues with script kiddies disrupting us and causing drama and claiming that our IRC server was insecure (it wasn't), and we figured out that they had found us through another IRC indexing site - one which we weren't aware were indexing us. another problem was someone adding a "partyline" bot to our server, which opened a channel to all other "partyline" channels that the bot had been added to. cute idea, but we did not ask for this, someone just plunked it in our server and left.
I wish there was a robots.txt for IRC, or at the very least for the indexers to tell one of the admins, "hey, we're indexing your server, please let us know if you don't want us to do that". we want to be left alone.
But for anything where the numbers, dates, and facts matter, why even bother?