I don't agree go is simpler to read. It is simpler to learn the syntax but the syntax is only part of what makes a language. Having learnt both, and having spent more time actually writing go I still prefer writing rust and finding it far easier to work with then go. Go has too many hidden gotchas that you need to trip up on to learn and then remember forever or else trip up on them again.

SIGINT is sent when you press Ctrl+C. SIGTERM is sent in just about every other situation - basically when the system wants the program to end. For instance when systemd wants to stop the service or the default signal with programs like kill pkill htop etc. You should catch both of these signals.

Or refactored at a later date.

GUIs tend to only cover the common/basic usage. Which is easy to remember without a cheat sheet. When you need more advanced stuff then GUIs tend to become more of a sticking point I find. And with common workflows it is far easier to automate with the CLI then with a GUI.

Would it even need to pretend it is open? If it can fake a port being open then it can tell when a close port is being pinged. So can outright block connections from those IPs without ever pretending it is open?

A new diffraction-gated real-time ultra-speed mapping technology threatens to undercut cameras costing $100,000 with off-the-shelf parts.

The threatens to undercut part. Rather than talking about how it is going to make things more affordable, it talks about how it is going to ruin the exiting markets pricing. At least that is how that reads to me. Note, I am not talking about the whole article - just that one abstract, which is what is shown here and leads a completely different tone to how the article is actually worded.

I dont think so. Both UFW and firewalld are just frontends - they don't actually do any work themselves. That is all handled by the iptables or the newer nftables kernel modules inside the kernel itself, the major difference will be in what rules they create but both should be able to create the same rules for either of these kernel APIs. UFW is what ubuntu uses by default I believe and firewalld what a lot of other distros use by default.

Avoiding unity games hurts the game Devs far more then unity. Even if they move away from it for their next game they might not be able to for currently released ones.

The teams behind the DART mission are tracking it, and will continue to track it into the future. There is even a new mission set to launch to send another craft to the asteroid to gather more information. So, yeah lots of follow up to come over the next year. It is just far more likely that they don't really have much to say ATM aside from well, that is not acting as predicted, we need more evidence/data to figure out what exactly is going on. Which is what this students paper basically concluded.

https://phys.org/news/2023-09-dart-impact.html gives a far better overview of the situation than the BBC article linked above.

What do you mean separate them from each other?

There are quite a few web frontend frameworks for rust now that are reasonably mature. Though you might still find a few rough edges they are usable for projects now.

• https://www.leptos.dev/
• https://dioxuslabs.com/
• https://yew.rs/

All of these can work without you needing to write any JS code. Though there is JS glue code involved, it is generated and you don't need to worry about it.

But the JS eco system is still quite large and hard to completely avoid.

Canonical, the creator and main contributor of the LXD project has decided that after over 8 years as part of the Linux Containers community, the project would now be better served directly under Canonical’s own set of projects.

Or does Canonical think Canonical is better served if LXD is directly under its control 🤔