These are good in a more hands on way, but it is hard there to understand the conceptual difference between MIT and EUPL. So, I deliberately didn’t go in to the details, since there are a lot of tools for that. I aimed for a higher level, since I find people often have missed that.
For that you need to ask the author, and the discussion page in github is a good place to ask.
Well, I get you are trying to state that MAGA people are pedofiles, and I am not here to stop you from that. But you also assume they catch actual pedofiles. However, there are cases where they have contacted people with an intellectual disability, and then you cannot be really sure the person really is sexually in to children, since with enough pushing you can get such persons to agree to a meeting anyway… just because you pushed. Regardless of how awful the crime is, we cannot accept vigilantes.
atuin is really great for command history completion
Ahhh… Sorry, of course there was the 2021 edition in between… Ignore me… 🤣
That refers to the Edition, and all development up to January 2024 (rust 1.84) was edition 2018. With rust 1.85, Edition 2024 came out. Here is the news in Rust Edition 2024 https://doc.rust-lang.org/edition-guide/rust-2024/index.html , mostly details, so for effective rust everything for Rust 2018 should still be relevant.
Hey, there is a long tradition of banning evil math… even Pythagoras did it… But, I guess he at least had good reasons, irrational numbers are super creepy and deserved to be banned.
Yes, but then you wouldn’t find the comment section there to read all the insightful comments… /s
The response by Greg KH is also well worth reading:
https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/
And yes, date time handling is one of the most confusing areas on computer science. https://xkcd.com/2867/
I personally think Jiff is based on a very solid design, as it is inspired by Temporal, which is a TC39 proposal to improve datetime handling in JavaScript. I have done some date time handling with chrono, but I find jiff much easier to work with. So, I can recommend you take a serious look, and see if it makes your life easier for your use case. Now, it is only version 0.2, so the API might change before 1.0, but it seems to respect semver, so there shouldn’t be any surprise breakage at least.
When I was in my 20:ies, I had my alarm clock at the other side of the room and still managed to oversleep. I ended up having it under my bed close to the wall, so I had to crawl in under my bed (quite narrow space) pressing my body to the cold floor to turn off the alarm… and I never managed to turn that off in my sleep. But I would have preferred a wake up call… so, even though I have never used the service when staying at a hotel, I can see why some people use it.
Not the creator, just posting
I think this would be a nice improvement to reduce boiler plate.
On an unrelated note, don’t forget to sanitize your input.
This is why Bobby Tables mom needs her Github account suspended…
It remove the central server, which is often the single point of failure. So even if it doesn’t add more security than signal, it adds resilience. And this is not Tor in the way that its not a proxy, its a framework to build secure peer to peer applications.
That requires a complete picture and all possible use cases from the start. Initially when a language is new and hardly used there are much to benefit from flexibility and trying new concepts. Then as the language matures, a more formal process is needed to ensure stability. There is a reason these discussions comes now, since rust is in a very stable phase.
As someone that have worked in software for 30 years, and deplying complicated software, shared libraries is a misstake. You think you get the benefit of size and easy security upgrades, but due to deployment hell you end up using docker and now your deployment actually added a whole OS in size and you need to do security upgrades for this OS instead of just your application. I use rust for some software now, and I build it with musl, and is struck by how small things get in relation to the regular deployment, and it feels like magic that I no longer get glibc incompatibility issues.
Well, for specific licenses there are use cases for MPL, which is weak copy left. LGPL is trying to state that statical linking is not allowed, while MPL does. Also, EUPL have simmilar advantages over AGPL, plus that it have very clear defined legal juristiction. So, when it comes to specific licenses there are many reasons to use whatever licence you use. Just make sure you use a license that reflects your expectations.