anthonyshort

Then the hallucinated research is published in an article which is then cited by other AI research, continuing the push the false information until it’s hard to know where the lie started.

We also have more staggered school breaks throughout the year. With two weeks off after every term, many more public holidays, and the ~2 month summer break there are a lot more opportunities to go on holiday. As an Aussie dad in the US, I'm struggling to think how I'm possibly going to get them back to Australia when they're at school throughout the entire year.

I wonder if this difference is always why Americans don't put butter on sandwiches or consider just bread and butter a completely normal snack. If it doesn't taste like anything I can see why it wouldn't make sense.

I believe it was saying that Qantas was the only Australian-owned airline operating long haul flights during the pandemic.

In my experience, other countries don't view themselves that way, and it's mostly seen as an Americanism (I'm not American)

I think it was the sunsetting of Google Reader that triggered the downfall. I don’t think I ever cared about push notifications for feeds. When you have your morning coffee, open up Reeder, refresh the feeds and read through a few articles.

The US is the only country that uses F. It has nothing to do with speaking English. Every other English speaking country uses celsius.

Weekly or fortnightly pay is common in Australia, so talking about it as weeks of pay made sense to me. I don't think they really even use the term "fortnight" in the US. Every tech company I've worked at here seems to do the 15th and 30th which is still strange to me.

Design systems alone don't really solve for this. Design would need to look at the experience across the entire app.

A simplified example of how the UX can break down if frontend teams are too isolated is notifications. If every team triggers a bunch of their own notifications the user might be getting slammed with notifications.

Sure the pieces might look cohesive, but it might suck for the user if the teams aren't thinking about it from the perspective of a user.

Every design is meant to be used. The amount of space needed is relative to the problem.

I can imagine a world where this would be useful, being able to drop something in as easy as a <select/> element seems fine.

It seems useful for UI primitives, like a dialog, tooltip etc, that the browsers might not implement as native elements themselves. But as a building block for creating entire applications? I don’t think so.

Which means they’re always going to need to hook into the framework that’s rendering them, either to connect state, managing effects, or for styling.

I just don’t see sharing a component regardless of framework as a major problem worth solving right now. Buy into a framework and community like React and you can just drop components into your app. It’s not framework-agnostic but it works.

I don’t understand the push to make userland component abstractions into native primitives. It’s perfectly fine for the browser to just implement low level primitives for frameworks like React to build on top of. It allows the framework to develop much faster.

Web components kind of miss a lot of the reasons why React has taken off. Encapsulation is one thing but it’s the declarative way of handling state, effects, and the DOM that make it powerful. Web components would need a framework on top of it to make it usable by developers building anything significant.

They never said that all 1.0 use cases were covered now. They promised that eventually they will have use case parity and then they’ll deprecate 1.0.