Not really fixable, unfortunately. The API requires an network call for each comment:
> The v0 API is essentially a dump of our in-memory data structures. We know, what works great locally in memory isn't so hot over the network.
When I played around with making a client, I found the best approach was to only load the first level of comments, and asynchronously fetch children inside DisclosureGroups on appear.
Then I realized the only reason I was making an HN app was so it didn’t blind me at night, and then I realized Lobsters has all the same stories as this place but lets me filter out vibe coding articles, and I just gave up.
> It's the same thing. In the latter case, something has validated that your NonEmpty has a first and a last element.
No, it has parsed it into a structure that structurally has at least one element, not just the promise that there ought to be one. From the original “Parse, don’t validate” article:
data NonEmpty a = a :| [a]
> your type still permits {name: "\0\0\0\0\0\0", host: "!"}
I actually originally wrote it with an array of EmailNameCharacters, etc but didn’t want to overcomplicate the example.
This is just validation that is using the type system to indicate the validation has already occurred. I think the real point of “parse, don’t validate” is to make the type system give you structural guarantees that couldn’t exist otherwise (e.g. always having a first/last element in the NonEmpty example from the original article). If you’re just branding the types as “parsed” (in reality, simply validated) you still have to know that the invariants you care about hold when using the “parsed” type (e.g. splitting the email type using “@“ will always yield 2 elements), instead of the structure of the type holding that info inherently (e.g. struct Email { name: String, host: String }).
guard has two advantages: the compiler ensures that you exit the current scope if the condition does not hold (via return, break, continue, etc), and bindings established in the guard clause (e.g. let foo = optionalBar) remaining in scope after the guard block, rather than inside it like an if block.
You can configure macOS to switch between languages by pressing the globe key, but it’s a far cry from letting you type in any of your languages without it autocorrecting/red-underlining.
> In addition, every software company seems to go their own way and have their own “style”
Hence Apple using the same set of SF Symbols across all their platforms. And I don't think icons are intended to be used to initially identify the purpose of a button, but instead to provide a quick visual anchor once you are already familiar. Sure, there are some buttons that everyone will use more (like Save or Open), but I don't think there's anything wrong with allowing every button to have this sort of quick visual lookup. Predicting user behavior is hard.
I strongly dislike Ive's influence overall, but skeuomorphism made it incredibly difficult and cost-prohibitive for a single indie developer to make an app that felt like a polished first-party experience for iOS. I'm glad it's gone. You're still welcome to do it if you want and you have the whimsy and artistic talent (or design team) for it.
Yes, I have been listening to Gruber complain about them for a year now. His critique is that "Apple's HIG used to say not to," not anything about what actually makes them bad.
Curiously, I haven't heard him talk about Apple Intelligence in Shortcuts, or any of the cool new features in Tahoe. Design is how it looks, I guess.
> This is about setting keyboard shortcuts for custom actions for applications, not window traversal on the desktop.
The "All Applications" section lets you define global shortcuts. As long as there is a menu bar item for it (in this case, one from the Window menu) you can define a shortcut for it.
Thank you very much for this recommendation! Most of my work is in Xcode, and in an ideal world Xcode would just support third-party syntax highlighting (or LSP), and I've been looking for a Mac-assed simple editor for those scenarios where I just want basic syntax support for a random text file. CotEditor is perfect!
> The v0 API is essentially a dump of our in-memory data structures. We know, what works great locally in memory isn't so hot over the network.
When I played around with making a client, I found the best approach was to only load the first level of comments, and asynchronously fetch children inside DisclosureGroups on appear.
Then I realized the only reason I was making an HN app was so it didn’t blind me at night, and then I realized Lobsters has all the same stories as this place but lets me filter out vibe coding articles, and I just gave up.