Man... I stand by it being an interesting idea that they fumbled by not following their own HIG.

Even if it is a bit of a silly line of reasoning, there was (at least originally) a purpose to the brushed metal UI. Anything that was capable of external IO (quicktime for ingesting firewire feed from camera, itunes for syncing with an iPod, finder for disks) was supposed to have a brushed metal interface. There's a world where 2 different classes of windows stuck around (one for things INSIDE the computer, one for things OUTSIDE of the computer) and I bet we would've gotten a lot more afforadances for real-life devices. Maybe a predictable device status UI in those sorts of windows or something. Maybe they'd just be those white panes with fancy animated product shots that show up when you get an Apple-blessed bluetooth device near an iPhone. There's at least some reasoning to treat external IO windows as sharing some sort of common UX. (Answering pretty common gadget questions like: is it connected, is it charging, is it lost, etc etc etc)

But then the waters get muddied with the calculator being brushed metal because it's trying to look like a calculator. And safari... because I guess the network is external but...?

I think a little after John wrote this blog post I'm using to jog my memory, all pinstripe windows were gone except maybe the preferences panes... so it was definitely arbitrary form over function at that point.

(Jogging my memory from: https://daringfireball.net/2004/10/brushed-metal)

People aren't trying to communicate accurately if their first priority is getting you excited about the thing!

    > The goal wasn't to build another social network.
    > It was to bring back a small feeling that the web used to have: the sense that there are actual people on the other side of the screen.
    > Town Square is intentionally tiny and forgetful. There are no accounts, no profiles, no follower counts, no permanent chat history. Messages exist only while people are there to read them.

[0] https://en.wikipedia.org/wiki/Greeble

I am an absolutely garbage scrabble player, but I will be keeping this gem in my back pocket… probably a rare case to play it though haha

So as I understand it, they're not suggesting that we pile many packages into 1 git repo as a sort of pseudo-crates.io, they're just promoting the fact that you can install a package directly from a git URL, rather than using a crate name on a registry.

What seems weird about that model to me is that dependancies will not sync between these individual packages. If package A chooses the canonical git URL for package C, and package B uses a self-hosted version of package C instead, you have two versions of package C.

Theres a lot of codebases out there that are at odds with my own opinions about syntax/structure/purpose, but there’s evidence of “taste” that I absolutely respect. I can look at a couple modules, and have a good idea what the other modules are going to be like, because the mental model of the author is clear from the code itself. Even teams with multiple authors with taste average out to one taste-profile and in a similar way, I’ve seen LLM output shaped by someone with taste and had the same feeling: “yeah I see the direction you’re going in”.

Someone without taste using an LLM writes slop. I can’t tell what you’re doing. Any question about what you’re doing results in “sorry that was Claude”. Entirely pointless that you’re even involved.

It’s a property of the author IMO. They were kind of owed an existential crisis as cruel as that is to say.

Yeah that sounds like WoW retail heh.

Kill 200 boars.

Kill 300 boars.

Kill 250 boars and use this sword.

Kill 251 boars and use this special sword.

I heard about a better sword over there. You have to get past the 200 boars.

Wow, thank you for saving me from the boars. Please take this Boar Bane sword. You should try it out on 200 boars.

> attackers gained access to its internal IT systems and data related to patients participating in some clinical trials, including their patient IDs (random alphanumeric strings) and information on trial participation, sex, year of birth, biomarkers, health/immunogenicity data, and lifestyle factors (e.g., smoking, alcohol use, BMI).

Under no circumstances do you “gotta hand it to the huge pharma company”, and maybe this is the bare minimum we should expect from trial data, but given you are a target for an attack like this… not holding onto PII data beyond what’s needed for the trial itself is good.

[0] https://triptychproject.org/

[0] https://www.youtube.com/live/hF8swzNR1-o?t=3800s

If I could make one suggestion, I really like the old MacOS "inspector" pattern. Basically a consistent way to get meta-information about any "thing" the user chooses to inspect. Your right sidebar is going towards that, but it would need some work to make it more consistent between views.

GitHub's UI has these weird meta-states/restrictions that are so badly explained in the UI they feel like bugs. Each line gets a [...] menu in github which lets you see the blame/spawn a issue linking to it/get a permalink/etc. It's a totally different UI in the diff view, and then totally different again if you're looking at a comment referencing a line in a diff AND different if it's referencing a permalink to a line in a file, even if it's the same code that would be in that diff!

I want the UI to have obvious "nouns". If the UI is showing me a line of code, even if it's in a diff view, let me "inspect" it and get the exact same meta-info + tools I get for lines of code anywhere. It's "a line", not a weird meta state of "a line, but you're in the comment of a PR linking to this line".

Same concept applies to comments/commits/authors/etc. If the UI shows me a username, I should be able to pull up a "who is that again" inspector. Going into github's commit view, clicking on a name... and being sent to a filtered list of that person's commits makes zero sense to me because this is the ONLY place where that happens. That behaviour should be a "recent commits" button inside some "user inspector".

Hopefully this thread isn't putting you down. Sorry if it's coming off like that.

I could be off base here though, I'm really channeling grade 9 bio class from decades ago!

Many of those people will speak a language that’s not English, or live in the EU or China where it’ll still be “Siri”, not “Siri AI”.

“Do you have the new Siri?”

“Yeah I updated… but she still seems so dumb”

“Oh yeah… well that’s Siri for you I guess”

Horrifying for marketing folk, I would presume. You’re just setting people up to confirm that Siri is always useless and improvements are invisible.