I don't know where you get "really difficult" and "fighting against macOS" from. You only have to hit the disclosure arrow next to "Where" in the save dialog one time and it remembers it and shows it by default from then on. (Okay, maybe it's once per app? I don't remember for sure, but I can't remember the last time the save panel didn't show me the folder browser by default.)
If you read the article, it talks from the perspective of "I help lots of friends and family with IT stuff". For most users, they wouldn't know how to get to the larger menu or that Cmd+Shft+G lets them type in a path.
That's progressive disclosure, and it's usually considered to be a good thing for usability.
Let's be clear: if you save something in macOS, by default you get:
1. a text field with something like "Untitled" already selected, but not the extension, so if you just start typing, the extension isn't replaced.
2. a text field for tags to make organization easier
3. a Where drop-down with recent locations, favorites, drives, etc.
4. a button with an arrow pointing down next to the "where" list.
5. depending on the app, probably a format drop-down.
Friends and family who depend on "you're good with computers, right?" people like us, they get overwhelmed by too many choices. Here, macOS gives them five, only five, and the complaint is that most people ignore four of them!
Give them the larger menu by default, and it's more options to ignore. If someone is saving every single file to their Desktop (/me shudders), then they are ignoring every bit of even a small, simple UI, so giving them a more complicated UI accomplishes nothing good.
I said they're ignoring four of the five UI elements, but now I wonder how many of the files on the desktop are named "Untitled (38).pdf" or whatever. They could be ignoring all five!
Like others here, the content is something that I'm interested in, but I too have a reaction to the LLM-isms. I think part of it is that, once I recognize I'm reading LLM output, I have no way of knowing if it wrote the whole post based on a one-or-two sentence prompt or not, and if it did, how much can I really trust the output to not be hallucinated. If I'm going to read LLM output, I'd rather do so in the context of my own chat with it so I can understand the inputs to it and ask follow-up questions.
Can you put the pre-LLM version of your post on your site somewhere? I (and presumably many others) would be much more interested in reading that, even if the English is a bit awkward.
It's much worse than it used to be. Before it was only really a problem with apps with a lot of menus, and you could access the items by switching to an app with fewer of them. Now, the notch takes up a lot of space, and you hit it really soon on a 14" display—I can only have maybe three third party menu applets on top of my collection of built-in ones before they disappear into the notch.
I think it's not just the notch, but that menu bar icons are more widely spaced than they used to be. I want to say it happened around Sonoma (10.14)? I was working on a Mac app at the time. Icon styles went from dense with a generally square clickable area to widely spaced, wide rectangular clickable area, and a highlight with rounded corners when clicked.
I have a 16 inch and even I moved to the “no notch” resolution last year because a ton of apps don’t let you choose whether to have a menu icon, and many of them are required corporate crapware. Apple should have bought Bartender and made it part of the OS 10 years ago, or at least before shipping this stupid notch. Apple’s “we know what you need better than you do” approach is so exhausting.
(Real examples, with "phish" replacing a string of 3-4 random letters)
In some ways, it's a more convincing fake URL, since even if you're used to reading the domain right-to-left, your brain wants to start from the hyphen since it's a different character following a familiar TLD. But that type of domain also seems a lot easier for spam detection rules to catch.
I think you have it the other way, the hyphen should be in a place where it can be confused with a period. E.g. foo-example.com, which at first glance mentally parses similarly to foo.example.com
This is how the scam page in OPs article is formatted, and I think it could easily fool a technical person who's tired. Precisely for the reason you touched on that when you're used to working with reverse DNS notation your eye is drawn to the last period. But hyphen and period are both used as "separators" in different contexts, so you have to be vigilant enough to override the natural instinct to chunk based on any separator.
Not too sure of the utility of this. It's not an easy sentence to remember, because while grammatical, it's nonsense—it would take some effort. So if I'm trying to memorize a static IP, setting up a DNS name is likely to be easier. And also if I'm going to be using this to memorize IPs I'd like the algorithm to be open source.
All that being said, I think it's a neat idea and a cool tool!
I didn't get that sense from the prose; it didn't have the usual LLM hallmarks to me, though I'm not enough of an expert in the space to pick up on inaccuracies/hallucinations.
The "TRAINING" visualization does seem synthetic though, the graph is a bit too "perfect" and it's odd that the generated names don't update for every step.
For me it was the prose that alarmed me. Short sentences, aggressive punctuation, desperately trying to keep you engaged. It is totally possible to ask the model to choose a different style - I think that's either the default or corresponds to tastes of the content creators
> it really makes me doubt that what is written there is actually true at all
Indeed, the whole "Ironically, switching from Apache 2.0 to AGPL irrevocably makes the project forkable" section seems misguided. Apache 2.0-licensed software is just as forkable.
The point being we can simply tell our agents to start at the rug pull point and implement the same features and bug fixes on the Apache fork referring to the AGPL implementation.
reply