I read complicated and dry books as that helps me. I’m reading a Roman history book and an old philosophy book at the moment that I barely make it through a handful or two of pages of either before I’m drowsy. But if I pick up a brilliant piece of literature, I’ll read until dawn with zero issue.

I like to imagine there was a parade of ghosts but they’re all too skeptical to see them.

Reference for the admission?

Spot on. Another thing to consider is weather. EVs perform worse in cold weather - lower ranger and slower charging. Some manufacturers are worse than others. Preconditioning while plugged in is super helpful in below freezing temperatures and use the heated seats and heated steering wheel instead of climate control if you can.

Just needs some research if you live somewhere where below freezing temperatures occur at times in a year. Absolutely not a reason to avoid EVs altogether, just know the limitations, what to expect, and how to best mitigate some of the limitations.

And it’s made by a Bitwarden developer.

They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS” flag still and you can build the clients with the bitwarden_license folder deleted again (now they’ve fixed it).

I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.

This has been the way for years.

Cool. They got that sorted nice and quickly.

Edit:

I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.

SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.

Truth right here. I’ve been privileged to travel the world and curries are hands down the most flavourful dishes this planet has to offer.

Technically they thought they might have introduced a bug that caused the delay / a regression and set about investigating it. Pretty sure it was a Microsoft developer too.

Sadly people seem to be misunderstanding your sarcasm. /s became a thing on Reddit for this reason.

Nonsense. If they were perfect, wouldn’t they have used a question mark? Your judgement of character is laughable. What empirical evidence is there that they are perfect?

(How was that?)

Give it to meee

I’m not insisting anything; stating C is not a memory-safe language isn’t a subjective opinion.

Note I’m not even a Rust fan; I still prefer C because it’s what I know. But the kernel isn’t written by a bunch of Lewis Hamiltons; so many patches are from one-time contributors and the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching. Linux is written by monkeys with a few Hamiltons doing their best to review everything before merging.

Linus has talked about this repeatedly over the past few years at numerous conferences and there’s a reason he’s integrating Rust drivers and subsystems (and not asking them to fork as you are suggesting) to stop the kernel stagnating and to begin to address the issues like one-off patches that aren’t maintained by their original author and to start squashing the volume of memory corruption bugs that are causing 2/3rds of the kernel’s vulnerabilities.

No idea what you’re being downvoted. Just take a look at all the critical CVSS scored vulnerabilities in the Linux kernel over the past decade. They’re all overwhelmingly due to pitfalls of the C language - they’re rarely architectural issues but instead because some extra fluff wasn’t added to double check the size of an int or a struct etc resulting in memory corruption. Use after frees, out of bounds reads, etc.

These are pretty much wiped out entirely by Rust and caught at compile time (or at runtime with a panic).

The cognitive load of writing safe C, and the volume of extra code it requires, is the problem of C.

You can write safe C, if you know what you’re doing (but as shown by the volume of vulns, even the world’s best C programmers still make slip ups).

Rust forces safe® code without any of the cognitive load of C and without having to go out of your way to learn it and religiously implement it.

Having a dog helped me really get to know lots of people in the area when I moved home to somewhere totally new to me. Having a really friendly and safe dog breed makes you immediately so much more approachable, an ice breaker conversation (the dog), and a regular opportunity to meet the same people out and about.

If you’re in a situation where a dog is a good choice, I’d really recommend it.

You can just move the modifier keys around. I have Caps Lock as Ctrl and Ctrl as CMD.

If you just want geo coordinates, you could use any open source app and copy+paste them into a note or something.

Gosh that’s awful and I’m so sorry for you.

If you’re into gaming, this entire channel is full of hilarity.

Conway’s Law applies in this respect; the mess in governance of Nix has produced a product that reflects that mess. Nix started a beautiful movement but like many first movers, they rarely reap long-term rewards.

He’s been here the whole time!