HN user

halpow

75 karma
Posts0
Comments23
View on HN
No posts found.

Hard disagree. If people cared, then all iOS apps would use standard styling, but the matter of fact is that every app has its own style, which does not stop at colors. They all share the same affordances (top left arrow to go back, bottom tab bar) but the UI is more often than not heavily customized.

Take Slack for example with its fancy menus, not even close to what Apple uses. No feelings expected there. Let's not talk about Google apps, which live in its own UI world.

The fun part is that Spotlight used to do this, but they progressively made it worse year after year. It became completely unusable for me maybe a couple of years ago and switched to Raycast, which I use exactly like I used to use Spotlight in 2010 and nothing more.

I think that once a bug has been verified and keeps getting likes, it should not be closed.

If the user never responded to further questions, then absolutely.

What I see however is that maintainers themselves fight the bot removing the label and reopening issues. Over and over. Until they miss the notification.

You can't "remove" how LLMs describe changes. I'm not talking about useless comments, I was just saying that they describe changes the same way as they comment code.

I told you how it is. Copilot writes crap descriptions that just distract from the actual code and the intention of the change. If your commit messages are in any way better than that, then please enlighten us rather than calling me a bot.

If you're lucky to work in such an environment, more power to you. A lot of people have to deal with React where you need so much glue for basic tasks, and React isn't even the worst offender. Some boilerplate you can't wrap.

I haven't written a commit summary in months

I don't know what you're posting, but if it's anything like what I see being done by GitHub copilot, your commit messages are junk. They're equivalent to this and you're wasting everyone's time:

    // Sets the value
    const value = "red"

If you want to try easy mode, check out those newfangled android-based credit card terminal. I bet they're much more rewarding, especially since you tap your pin on the screen. Juicy.

They're great at one-shotting verbose code, but if they're generate bad code the first time you're out of luck.

I don’t think I ever got to write "this api doesn't exist" and then gotten a useful alternative.

Claude is the only one that regularly tells me something isn't possible rather than making sh up.

Japan is the perfect place for this because their house numbering system already requires you to look at a map to find it.

For those unfamiliar with it, numbers are incremented progressively around a block as doors are added to it. So the door "Block SanChome 4" could be on the opposite side of the building from "Block SanChome 6"