So you're saying Rust is the TOOL of programming languages.
Point of clarification: DAC is copper, AOC is fiber.
A lot of 10G equipment will support 5G/2.5G SFPs as well, so it can still be beneficial to go 10G on the core equipment.
There's that awful dad joke that foggy was talking about; Use it as inspiration for your exasperated sigh.
Not for the same cost per gram as good ol' Horse Electrolyte™! Talk to your Ivermectin dealer today!
Signing every message should have zero effect for people who don't use PGP; they'll just have a cryptic block of text at the bottom of the message you sent.
It's overkill to ship your pubkey with every email. Most people just publish to a trusted keyserver and call it a day since pretty much every client worth its salt can look up your pubkey directly.
One way they could increase the housing supply is by severely taxing corporate ownership of single-family homes (and possibly low-occupancy multi-family homes like duplexes).
Give it a grace period, say... 3 months (to cover the cases where a bank forecloses and is sole owner while the house is auctioned), then charge like 95% tax on market value every quarter.
Ted Ts'o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.
I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.
The hardline C devs that don't want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.
The Rust devs that are getting upset because people are "attacking" their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it's a matter of momentum and greybeard stubbornness.
In fairness, "I don't want to maintain bindings for a language I never intend to use" is a perfectly reasonable position.
The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).
omg dude you can't just ask about white collards
alternate joke: I guess you could say it's a white collard crime?
This is not always true. Some tablets are extended release and if you break them apart the timing is thrown off. You get a higher dose initially, and the dose doesn't last the intended period.
A family friend learned this the hard way when they were breaking a seizure preventive tablet in half to make it easier to swallow; they'd often have a recurrent seizure about an hour or two before their next dose time.
I agree with you completely, and I'm glad the game exists. It's just objectively the worst game I've ever played.
The problem with this take is the assertion that LLMs are going to take the place of secretaries in your analogy. The reality is that replacing junior devs with LLMs is like replacing secretaries with a network of typewriter monkeys who throw sheets of paper at a drunk MBA who decides what gets faxed.
I think the usual recommendation these days is get the highest rated corexy in your price range.
I've heard mixed reviews about Bambu AMS; seems cool enough, not quite the same as a true dual extruder, has some quirks and annoyances.
Maximum length is the biggest red flag to me and was the catalyst for me making the effort to switch to unique passwords per-account years ago. There's just so, so many shitty homerolled security systems out there... and data breaches seem to be a perennial problem these days.
There's just no excuse for limiting the length if you're doing security correctly (other than perhaps a large upper limit just to protect against someone DOSing the backend with a bunch of 100MB strings; 512 characters seems reasonable).
By setting an upper limit, you're basically saying one or more of these things:
- We store your password in plaintext
- We store a hash but our hashing function has an unnecessarily arbitrarily limited input size
- The person/team implementing the backend has no idea what they're doing and/or just copy pasted login code from stack overflow
- We tried to get away with minimal password requirements but some middle manager wouldn't rubber stamp it without
arbitrary_list_of_bs
"asked to resign as part of layoffs"
The sheer audacity. "Please quit so we don't have to pay you severance or unemployment." It boils the blood.