makeitdouble

> Why not, still pretty useful

Stumbling on names is fine, name litteraly have no logic, there is no system that will get them 100% correct by definition.

Screwing meaning is on a whole different level and Google Translate or even the built in screen reader of your OS will do an extremely good job given enough context (a whole phrase).

In real world use there is little space for sloppy hacks IMHO.

I'd see it as totally fair.

We also weren't discussing GoDaddy as a registrar without mentioning it's CEO killing elephants and being an all around douchebag. Or Oracle without the lawnmower.

It's tough to ask people to dissociate the CEO from the company, especially when he's doing all the PR by himself.

On counterfeit, seeking known brands or products that are thought to be reputable can be a tough strategy.

Same as parent, I'm amazed by the quality I get, but I'm also not looking for brands or vendors that try to piggy back on some halo effect.

That means choosing carefully what to buy from where, pouring over the specs and reviews for every purchase, but as I'm getting products that just don't exist elsewhere, that's a mental burden I'm fine with.

Not the op, but there are services (looking at you mercari) which will force passkeys when accessing specific functionalities. This is part of their security requirements, and it is directly linked to the money you have within their system.

To note you can still just give up your account and money, technically you're not _forced_. But that's a trend that will go on IMHO.

> This cannot happen with passkeys at all because crypto magic.

That's way too optimistic.

The core reason people enter the password in different domains is because most services suck at keeping a canonical login page. That forces users to register multiple URLs for a single credential. And from times to times, they hit a page not within their registered urls, will login and just add the new url to the pool.

Will these services magically become super competent because of passkey ? I'll respectfully doubt it.

They might not screw this specific aspect, but they'll screw enough other things that users will need to keep injecting password somewhere from times to times.

> And seriously way more convenient as well.

A point I don't see mentionned: switching accounts with passkeys is a PITA. Yes it's an implementation issue, there is no technical reason for sites to auto-log you with a passkey when you have one.

But as you point out it will be more convenient for a majority of people, so right now switching between multiple accounts when any of them has a passkey is a hell of itself.

Some password managers might handle it well now, I'd be curious to know as I'm won't be doing these kind of experiments again until there is a reasonable chance to go well.

You still need a password to exist, so while the passkey won't activate the user can still leak the account's credentials.

To cover that gap, you get rid of passwords altogether, and now users lose access if the passkey fails to sync or isn't available on one of their devices (let's say a Kindle Fire tablet)

Passkeys being bound to the domain is neat, but not without tradeoffs and practical workarounds. At least that can't be the only aspect to look at when making a choice.

FWIW Prime also often delivers earlier than the set date (yes, even when it's set to next day...)

I assume they want to limit the amount of customer support more than advertising their logistics.

You seem to be comparing that to a full tablet running home assistant ?

That would be a whole different category of device and surely not at 300 USD.

On better solutions managed locally, yes of course. Small shop's also deal with the same requirements without keeping their stuff online.

> someone will be sent out at night

We're talking about France, so that's an even lower chance of happening for a freezer's worth of goods.

The two upsides I'd see are the ability to throw away the food next day before opening the shop, and the franchise being able to force that procedure even if the local shop would have chosen otherwise.

Local tenant are usually a lot more lenient than their franchise manager (for good reason usually, but there's always that tension)

An issue with old iPads is getting OS updates.

The last base iPad still supported on the current OS must be the 2020 version. There was a blip in the corona years, but since the iPad sales have been declining, so the amount of devices still up to date aren't that many.

> I literally just ask a frontier model : "Pull the latest log and root cause the issue.".

While this can work, you also can't rely on it to work every single time, and still need to deal with the failures.

This is the part that gives me pause with all the discourse: you can't give up on the task you describe. You can't tell your team "something failed, but even after 20 prompts the model gives nothing good so let's forget the whole thing and go on with our lives"

So you still actually need the skills for when shit hits the fan. Perhaps it can be done in a more granular fashion with the model, and spending 30~60 min on it will do, but we're pretty far from "just utter 6 words"

If we could call someone else whenever it utterly fails it would also make it a different proposition. Same way people can try to fix their plumbing themselves, and call a pro when it's just too hard.

But who will you call to find the root cause of the issue in production ?

My random guess: freezer need temperature audits and franchise supermarkets have to prove they're properly managing the food. If the central monitoring service can also alert/dispatch staff within minutes to deal with issues, it becomes a pretty attractive proposition.

Something that might not be obvious, but temporary dips in temperatures also need to be monitored as it's enough to spoil the food. Worse case scenario isn't to have to throw 50~100 kilos of food, it's to have spoiled food still looking fine and consumers ending at the ER, with the whole franchise name on the news.

> My freezer at home

That can't be your frame of reference for a business entity part of a franchise.

Agree on the tradeoffs, if a family can have a traditional car and needs to maximize the value of owning it, something like a second hand utility car (a Berlingo for instance) will the best choice.

Now lower-class people have each their own needs, you won't always have space to park a big car, or the money to get a full driver license, or deal with the maintenance and insurance, you might not need to drive the highway more that once every blue moon and can borrow or rent something for these times etc.

Many have either no motored vehicle or a scooter for these needs, I'd zee the Zoe/Ami class of vehicles as a potential step up from that, more than a downgrade from traditional car.

That class of risk was just theoretical for decades, so the price on it was basically 0.

Now that we see large scale incidents will there be an actual money value associated with upgrading systems and security for supermarket appliances.

"heritage" isn't about fashion, Citroen is signaling a specific value proposition and ethos through this choice. And also enough commitment to burn their one throw at this target.

They already went a similar direction with the Ami,it was a pretty bold move and it was met with very decent sales https://www.passionnement-citroen.com/post/citroen-ami-premi...

> answering our questions even before we asked them

That's an interesting angle, and would perfectly explain how bad they became, even before AI.

Going that route requires to make a lot of assumptions and rely on heuristics, bin users in large buckets that behave predictively.

People speaking different languages than the country they're flagged on, asking different questions than what the zeitgeist is about, searching for things outside of the consensus or switching interests too quickly would all have definitely worse experiences and become the collateral damage of that vision.

Would that be what we want for job interviews ?

Thanks a lot !

I see your angle, but would take their comments more at face value: their concern is really sync, anything privacy probably being the nice side effect.

Sync has been part of their strategy for a while now, from revamping the whole iMessage stack to allow for sync, to their work on eSim etc. so the move doesn't break with their recent trends either.

From the top of my head, try to share your Fitness data to someone on a regular basis. We bought our mother in law an Apple Watch and she asked us to remotely check her data from time to time. We gave up pretty fast.

I'm on Android and my kid got my old iPhone. Parental controls can't be set by me.

My Apple ID still tried to contact my old iPhone when logging in as a dev.

I don't need to expand on iMessage and where messages go, it's part of the lore at this point. My wife's airport auto-swirching was also a mess to the point she disabled it.

Google Maps' time line features get randomly shut off and you only know it way after the fact.

The list just goes on and on. I also have my frustrations on other platforms, I'm just pointing out Apple is far from being great. People just get used to the rough edges after a while and tout it as "good enough".

> They've also made it clear that they see attestation as a consumer privacy violation and won't support it.

I'm trying to get a source on this but failing, do you have a link or some wwwdc sessions where Apple detail their stance ?

> "it just works"

That ship has sailed a long time ago.

Most people still hanging to that part have already built a whole way of life around the Apple ecosystem and the boundaries and how to work around them have become second nature to them.

The iPhone is now near 20y old, the world also changed, most got enshitificated, and looking at kids and elderlies dealing with their iPhones and macs none of it "just works".

Looking at Japan, it was the bastion of iPhone predominance, but I'm the latest numbers 30+ yo gradually got off the train to move to android as their phone is just becoming another tool to them.

You're defining being sustainable. IMHO "successful" is a lot more relative and defined by expectations.

To jest, businesses can be successful without sustainability. Instagram definitely was.

> killed

Evaluating large scale event by body count has it's value, but there's a lot more to a nuclear accident.

Perhaps economic impact could be another angle. Some estimates put it around 300 billion USD, roughly 3 to 4% of Japan's GDP. And we can blame whoever we want, many of Japan's reactors are still frozen, the Fukushima région is still basically an economical zombie, so the impact is still ongoing.

An actual war would be at a different scale, but short of that I don't think we saw any disaster wiping 4% off a G20 country economy's GDP, while still going on.

Being successful or not depends on the scale of the company. I'd wager at Cloudflare scale, many otherwise decent businesses would have virtually no effect on their baseline and wouldn't be worth running.

This is a common advice I'm not sure I've ever seen properly explained and proven. It's mostly "we asked the experts!" kind of 3min tidbits with a guy in a corporate polo shirt talking assertively to the camera.

Most people actually measuring it come up with more savings when cutting the AC during the longer spans when nobody's there (usually during the hottest part of the day).

And how their company setup JIRA is more often than not a decent representation of the company's vision of how work should be done.

So what they really hate is their company. Which is usually fair and understandable.

”KPI based altruism" could be more accurate ?

> It is just easier to use a js framework/library and have a clean view and state.

To note, it's "easier" if you don't really care outside of your specific and limited case.

Multi select is a perfect example: if you only ever need that component to work in your language on your specific list for the browser you personally use for the screen sizes you care about, it will be pretty easy.

Hell starts when you try to think beyond that: how does the JS component work in responsive for super small screens and super big screens ? do you handle touch and mouse and stuff in-between ? what about CJK ? Right to Left ? do you care if there is any very long entries in the list ? How do you handle previous selections ?

The more you start to care about the details or expand the range of what you're doing, the more you'll be pulling hairs if you try to handle them.

The native components won't be perfect either. Native devs will also be dwelling in that same hell as you, whether or not the native state is better will depend on how much they cared on their side.

A less catchy but more pragmatic approach is to understand the reliability and/or value of what you measure and hold back from making them targets.

If you can't trust your org to properly set its targets and need to blind yourself from the metrics you really want, you're in a pretty dire place.

At first encounter as a grad student borrowing a friend's computer, I pushed the bright red button, and couldn't see anything happening. Pushed it a bit stronger, though the wobbling was manufacturing sloppiness.

Intended use is really not intuitive.