A pretty cool episode. Top takeaways:

1. I'm going to miss Captain Ransom. I think it would have been fun to have a season or two of him. Only Discovery has had the balls to hand over the Captain's chair to another during its main run, and I think that is a good thing.
2. Starbase 80 is now set up as a new DS9-style show. A starbase guarding a dimensional portal. God I hope that happens. I just hope they pull off the ensemble cast that made DS9 such a classic.
3. I hate the tease for Rutherford x Tendi, it's so mean to tease it in the finale :'( But really it's so cute.

Plenty more I missed of course.

Rewatching in preparation for the finale, and I keep feeling that the voice of Curzon Dax sounds quite similar to the voice of Odo in DS9. I'm quite aware that Rene Auberjonois passed away not that long ago: may he rest in peace. And I guess he was voiced by Fred Tatasciore (Shaxs), which I can hear too. But I keep hearing Odo which is really nice.

I appreciate the recognition, finally!

Yeah, I get dinged if I return a gas vehicle with less than 3/4 tank, and yet Hertz is handing out EVs with under half a charge?? That's some major bullshit.

People aren't misunderstanding the issue. Third party cookie support is being dropped by all browsers. Chrome is also dropping them, but replacing them with topics. Sure, topics is less invasive than third party cookies, but it is still more invasive than the obvious user friendly approach of not having an invasive tracker built into your browser. No other major browser vendor is considering supporting topics. So they're doing an objectively user unfriendly thing here. This is the shit that happens when the world's largest internet advertising company also controls the browser.

In other news, emacs still didn't ship my init.el as part of the default configuration! Lol

The real assholes are the Bajorans, they never even erected a statue of Dukat!

I literally watched cops driving while on their phone everyday after it was made illegal. Nothing was done, Nothing changed, they hand out tickets while breaking the same rules.

I mean yeah, fuck the police :) Seems like we're in agreement here.

Might kill someone is a precrime, a issue with these tickets in this case is that without the AI camera nothing would have been seen (literally victimless). If someone crashes into anything while on their phone the chances it will be used in prosecution is low.

Using your fucking phone while driving is the crime. This isn't some "thought police" situation. Put the phone away, and you won't get the ticket. It's that simple. We don't need to wait for a person to mow down a pedestrian in order to punish them for driving irresponsibly.

In the same spirit, if a person gets drunk and drives home, and they don't kill somebody -- well that's a crime and they should be punished for it.

And if you can't handle driving responsibly, then the privilege of driving on public roads should be revoked.

I don’t think texting while driving is a good idea, like not wearing a seatbelt. However this is offloading a lot to AI, distracted driving is not well defined and considering the nuances I don’t want to leave any part to AI. Here is an example: eating a bowl of soup while operating a vehicle would be distracted right? What if the soup was in a cup? What if the soup was made of coffee beans?

This is such a weird ad absurdum argument. Nobody is telling some ML system "make a judgment call on whether the coffee bean soup is a distraction." The system is identifying people violating a cut-and-dried law: using their phone while driving, or not wearing a seatbelt. Assuming it can do it in an unbiased way (which is a huge if, to be fair), then there's no slippery slope here.

For what it's worth, I do worry about ML system bias, and I do think the seatbelt enforcement is a bit silly: I personally don't mind if a person makes a decision that will only impact their own safety. I care about the irresponsible decisions that people make affecting my safety, and I'd be glad for some unbiased enforcement of the traffic rules that protect us all.

Ah yes, the famously victimless crime of using your phone while driving. Honestly screw anybody who does that, they deserve to be ticketed each time, cause each time they might kill somebody.

It seems obvious to me. Twitter has historically been used by public figures, and especially public institutions like local governments, transit agencies, etc, to make official announcements & statements. Of course having that on a centrally owned social media site was never good, but now with Space Karen making it actively hostile to users (and trying to prevent logged out users from seeing that info), it's very bad. The sooner Twitter completes its inevitable collapse, the sooner those public figures & institutions will move to a better way to deliver those - Mastodon, RSS, webpages, whatever.

IMO it's in the public's best interest for all the holdouts to get out now so we can move on.

It's a cathartic, but not particularly productive vent.

Yes, there are stupid lines of time.sleep(1) written in some tests and codebases. But also, there are test setUp() methods which do expensive work per-test, so that the runtime grew too fast with the number of tests. There are situations where there was a smarter algorithm and the original author said "fuck it" and did the N^2 one. There are container-oriented workflows that take a long time to spin up in order to run the same tests. There are stupid DNS resolution timeouts because you didn't realize that the third-party library you used would try to connect to an API which is not reachable in your test environment... And the list goes on...

I feel like it's the "easy way out" to create some boogeyman, the stupid engineer who writes slow, shitty code. I think it's far more likely that these issues come about because a capable person wrote software under one set of assumptions, and then the assumptions changed, and now the code is slow because the assumptions were violated. There's no bad guy here, just people doing their best.

Cron may be old but I don't think it's "legacy" or invalid. There's plenty of perfectly good, modern implementations. The interface is well established, and it's quite simple to schedule something and check it. What's more, Cron works on new Linux systems, older non-systemd ones, and BSD and others. If all you need is a command run on a schedule, then Cron is a great tool for the job.

Systemd services and timers require you to read quite a bit more documentation to understand what you're doing. But of course you get more power and flexibility as a result.