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.

Australian public schools are funded by state and federal governments, not local. So all public schools tend to be pretty similar. On the flip side the government also partially funds private schools, which is an issue at the moment.

https://www.dese.gov.au/quality-schools-package/fact-sheets/...

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.

How do you define "fluff"? If you think design (how the story is told) or quality (how easy it is to understand) doesn't matter, then I strongly disagree.

I feel like I need to point out that in my experience demographic personas like this aren't used by product designers. I've seen marketing use them. Not designers.

Designers often get associated with fluffy exercises so I want to kill that stereotype. I don't think I've ever worked on a product team that used demographic personas like these.

I don't think it's trying to be a definitive reference. It seems more like those posters you put around the office to remind you of things you value or you think are important.

Everyone is taking this fairly seriously. I doubt HN is the target demographic for this sort of thing though.

That's not really the point we were making and I'm not sure you have a correct understanding of UX, as you're conflating UX and visual design.

There's no pressure in the market to not value UX. Everyone wants and needs that. If anything there are pressures to only value efficiency rather than delight. Sometimes "fun" isn't efficient.

The reaction on Hacker News compared to the reaction on Designer News is great.

I think the problem people are struggling with is that it's a site created mostly for fun and delight, but the message is about "UX", which people generally think of as a way to maximize efficiency.

Products don't always need to be relentlessly efficient to be considered useful or "good". Some products are created for you to just enjoy.

All it does it transform into a tree of objects, https://gist.github.com/anthonyshort/5e9112a9ded7c8fc0f20, which is annoying to write out by hand and HTML is familiar.

I hated it (a lot) before I tried it out. You could just put the render function in a separate file since it's just a function and then it's basically the same as a template anyway

We're still using it on some of our projects, but we've found that no matter how simple we make data-binding it still leads to a mess of event bindings and state management.

The original plan was to make a virtual dom plugin for ripple but it wasn't really possible with the way the worked behind the scenes.

You could also just export from each of the requires in that manifest.js file you have there.

Although there's no real benefit of doing that over using the manifest other than it's kinda cool :)

You'd use a component.json to lock it down for an app. The inline versioning is really just a way to quickly write code and get something up and running. Manifests are just a pain when you're just getting started with a project or a small script.

If a component.json is present, it'll use that to get the versions and you just require('emberjs/ember-component')

But if you're at that point you probably have your own private git hosting somewhere too (or just private repos somewhere else). When there is support added for different remotes you could just require from there instead of Github.

Point is, just use the git repos instead of needing that registry at all.

For private packages, you'd just make the repo private on Github and make sure you have auth details in your .netrc file. So you don't really need your own "registry". There is talk about supporting more than just Github too.

index.js as the entry point for a module is pretty standard with projects built around Component and npm. It's bower and the lack of the standard there that creates the issue.

gzips down to 8kb though, and that's the standalone version. Using it with component it will usually share dependencies with other components.

Nope, no virtual DOM. I like that concept, but I wanted to keep it simple. I'd like to make a virtual DOM plugin but it's a non-trivial task.

It still batches all changes using requestAnimationFrame and it'll support Object.observe when that's ready.

https://github.com/ripplejs/ripple/tree/master/docs/composin...

Yep, you can nest views in a similar way to React. It's not exactly the same, but it's similar. Data is kept in sync and components are re-usable.

Communication between views is either through events, passing in callbacks, the dispatch plugin (uses custom DOM events and bubbling like Flight). There are a few ways to do it depending on the problem. Views have references to their children and the owner too.

Probably worth mentioning that the hula hoop dancing happened at a Github party with a lot of people not from Github. It was also super badass hula hooping, not just regular dancing. Everyone was looking, men and women, because it was pretty awesome.