As I heard the tale, on the Standard Missile, they don't recirculate the hydraulic fluid, they just spit out as the missile flies. It's a wonderful engineering solution.
Read the original Inside Macintosh, since that's about as fundamental and basic as it gets. See how they did the API for the Event, Window, and Control Mangers.
Something akin to: "Right now, you're carrying more computing power than what's on Voyager. And I'm not talking about your phone, I'm talking about your keyfob."
Also, just so I'm clear, there's no requirement to share passkeys. Or even have passkeys enabled on all devices, right?
If I log in to a site from my machine, and set up a passkey, but then log into that site from another machine, it'll just see no passkey present and ask for my password, yes?
A passkey is a local password on a device that could be shared through all the password manager gymnastics, but its not required as I understand it.
That’s true for all accounts that i’ve been using (Google, Apple, Microsoft).
Passkey generated on a device can only change login flow for this one specific device. If you don’t synchronize passkey to other devices or if you do not generate passkey on other device, then login flow is different for other device. You need to enter password.
Imo it would not make any sense if it was different.
I think there are passkeys that can be migrated/synced between devices, and device-bound passkeys that can't. I do save passkeys on my password manager and use them across devices, but I am pretty sure I have had passkeys that I could only use from a specific device. Not sure though, it feels a bit confusing.
Yes, that's right. It might also make sense to generate multiple passkeys for an account. For example, a separate one for logging in from Apple devices.
As someone who has found themselves in a situation out in the wild with a fire and a fire extinguisher (neither of which were mine), with no direct extinguisher experience, you can take some solace in that they work very easily. They're not some wild hose that going to send you around the room. There's very little force. And you can simply fire it in bursts. It takes no time to get a feel for it and use it with precision.
If you find yourself with a fire and an extinguisher, do not hesitate to pull the pin, and go to it. You'll figure it out. In the end, you can't really make the situation worse.
To be fair, I have a 2014 Jeep Grand Cherokee. It was the first year of their then new model rollout for the GC. It was (as I understand it) the last of the Mercedes JGCs.
I love this thing, it's a "cold dead hands" kind of car for me. Only has 120k-ish miles on it.
I won't say it's my last car ever, I just have a hard time visualizing swapping it out for anything.
It starts, all the buttons work, it's cosmetically 95%. The single biggest issue is that last year it was down for a couple of months simply because of parts availability. It's not unreliable, but it's swapped a few things (water pump, radiator, A/C has had work twice, guess it's a bit notorious in the community). Purchased in 2013, it's a 12 year old car.
But waiting months for suspension components (air suspension, which I adore) was a real drag. Even with a dealer supplied rental.
That would be the thing that sends me over the edge long term, I think.
It'll be a shame when it happens, I love the car.
The dealer wants to buy it every time I take it in for routine maintenance.
You don’t know much about cars. All the work they had done on their vehicle was typical for that model generation. Air suspensions are generally problematic because of constant wear mixed with parts issues, and A/C problems are common in that model generation. This is all normal stuff to fix over twelve years.
I do most of the maintenance of cars in our garage, and I would never accept double AC repair, suspension and radiator replacement to be "normal" around 120k.
The thing is, modern jeeps are a joke even compared to this "reliable" example.
There was a post recently about over-the-air update bricking Jeeps WHILE DRIVING ON THE FUCKING HIGHWAY. And no one cares. People keep buying this trash and defend double AC repairs. ¯ \ _ ( ツ ) _ / ¯
They sell luxury goods, which people know to avoid when they care about reliability
The thing is, jeeps are even beating the BMWs when it comes to unreliability.
Yes Mercedes built that garbage for the US market because US market eats that crap. Then stellantis took it a step up and removed reliability from their vocabulary entirely - more profitable that way. I'd pick a modern VW over American garbage all day any day.
But sure, keep yourself convinced about exceptionalism of American SUVs.
It's not like stickers are particularly difficult to make, or Watterson had an army of auditors combing every gas station or car meet looking for sticker makers.
They have (as I understand it) challenged and stopped some folks from doing things, but something like the Calvin sticker was pretty ubiquitous. Even then, some later ones were particularly bad Calvins.
I had a vinyl sticker of Spaceman Spiff on the back of my motorcycle helmet. I bought it at a motorcycle race back in the 90s.
But that said, it would be interesting to see the different systems after a tuning pass. Both as an example of capability, but also as an mechanic to discuss tuning options available to the users.
Mind, the whole "its slow get new hardware" comes from the fact that getting another 10% by tuning "won't fix the problem". By the time folks feel the sluggish performance, you're probably not looking for another 10 points. The 10 points matter at scale to lower overall hardware costs. 10% less hardware with a 1000 servers is a different problem with 10% less hardware with just one.
But, still, a tuning blog would be interesting, at least to me.
We used to travel with folks in the back bed in beach chairs. It was quite comfortable, and you could fit four in a small Toyota truck bed. We would face each other, and talk, and it's was a fun and social way to travel. Six adults in a short bed Toyota, with 2 in the cab.
With just two of us in the back, we'd have the chairs against the cab (like the Brat did). Riding backwards in a vehicle is surprisingly relaxing. You can't see the traffic ahead, so you have absolutely zero interest in where the car is going, how fast, how close, missing exits, etc. You're just cognitively out of that loop. Even as a normal passenger, even if we stay silent, we're all firing off those "back seat driver" neurons a bit.
But riding backwards, where it's all out of sight and out of mind, it's a noticeable reduction in that. On one trip, we're heading to the mountains, my friend and I in back of the truck. Suddenly, the truck is braking very hard. We, of course, have no idea what's happening. I said "Well, this is it, good knowing you." "Yup! You too!".
Obviously nothing happened, but it was a curious incident to say the least.
Definitely not a place to be during a rollover. Same reason they don’t have seats at the rear of cars facing back. Not best place to be when getting rear-ended even though it’s a great place to be as a kid watching traffic and making faces to passers by…
When I first read this, I read it like "Here's 50 problems that have standard web APIs"...that solve the problems!
As in, "here's problem 27, and here's the API to solve it".
Mind, I haven't read that article, and that's not what it's about.
Just how I read the headline. Just interesting how the language center can work.
reply