Oh no, what bullshit is it this time?

Because after moving very slowly and steadily for just about forever, the other galaxies will suddenly make a jump of like ten thousandth of a degree.

Imagine the following:

You actually can stop the time by snapping you fingers, but it stops time for the entire universe, including yourself, with the exception of one single observer on some unimportant planet in the Andromeda galaxy. After 100 years from the POV of that observer, time resumes again.

Would you even be able to tell?

Is OpenBSD seriously still using CVS for development?

And “nothing” does not fit, either.

Attempted electrical substation sabotage is an easy way to fix your loneliness forever. And also all of your other problems.

The sentences are 5 years in one case and 4 in the others.

Anyone got a non-paywalled version?

What episode is this from?

After googling around for a bit, and then switching to duckduckgo instead (Google becomes aggressively unhelpful as soon as you have words like “ejaculated” in your query. Duckduckgo does the same thing, just not quite so much.), it seems the book in question might be “The tenant of Wildfell Hall” by Emily Brontë.

Going by what OP thinks “Chaotic Evil” means for sysadmins, they have clearly never heard of BOFH.

Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.

Later on, programmers will need to learn a few rules about comments, like:

• Assume that whoever reads your code knows the programming language, the platform and the problem domain at least in general terms. You are not writing a teaching aid, you are writing presumably useful software.
• Don’t comment the obvious. (Aside from documentation comments for function/method/class signatures)
• Don’t comment what a line is doing. Instead, write your code, especially names for variables, constants, classes, functions, methods and so on, so that they produce talking code that needs no comments. Reserve the “what” style comments for where that just isn’t possible.
• Do comment the why. Tell the reader about your intentions and about big-picture issues. If an if-statement is hard to parse, write a corresponding if clause in plain English on top of it.
• In some cases, comment the “why not”, to keep maintenance programmers from falling in the same trap you already found.

I wonder when, if ever, Warner Bros. Is going to learn that players are actively pushing back against corporate greed and live service games are already way past the limit of microtransactions that players deem acceptable.

Some time after that actually happens.

Yes, there are a lot of players in various social networks loudly complaining about the phenomenon (although I suspect many of those are not even in the target audience to begin with), and there are even some actively boycotting these games, but so long as there are enough of them left willing to play ball, and especially some with an exploitable addiction-prone personality that can be hooked on loot boxes and microtransactions until they spend more than they have, there just isn’t anything for these companies here to “learn”. Other than “hey, this is insanely profitable”.

They may get insulted on Xitter for it, but who cares, everybody gets insulted on Shitter…

Melania is a blatant gold digger. She might divorce him if he goes bankrupt, but only then.

I have been sort of following Wayland’s development for over 10 years now. I have been using Wayland for over 2 years now. I have been reading and watching various lengthy arguments online for and against it. I still don’t feel like I actually know it even is, not beyond some handwavey superficialities. Definitely not to the extent and depth I could understand what X11 was and how to actually work with it, troubleshoot it when necessary and achieve something slightly unusual with it. I feel like, these days, you are either getting superficial marketing materials, ELI5 approaches that seem to be suited at best to pacify a nosy child without giving them anything to actually work with, or reference manuals full of unexplained jargon for people who already know how it works and just need to look up some details now and then…

Maybe I’m getting old. I used to like Linux because I could actually understand what was going on…

The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:

https://bugs.kde.org/show_bug.cgi?id=481058

Just a reminder of just how many lives starfleet could have saved over the years by simply introducing seatbelts…

Aw, too bad, they were working so hard on bankrupting themselves in defiance of that endless money cheat code they’ve got…

Honestly, this should be a bigger discussion, and not limited to just games. If a software company sells a software license for perpetual use to someone, they should not be allowed to use copy protection mechanisms that prevent the licensee from using it in perpetuity.

If there’s some other technical reason why the software won’t run any more after ten or twenty years, that’s another story. But if they just can’t be bothered to keep running the licensing servers, then they need to bloody well remove the stinking copy protection.

There was like one scene with muskets in the book. Even then, I grew up with this material (in the form of several different movie and cartoon adaptations, and eventually the book, too), and it took me an embarrassingly long time to figure out that the name musketeer comes from the musket.