Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple. Apple Please

digipres.club

Post reply on HN
Print view View original

21–30 of 64 posts

Re: Apple. Apple Please

#21

Post by godelski »

I hate Apple products, but I just hate Windows more and am willing to give Linux a pass more.

  Why are core util programs different?
Seriously! I know it's BSD based, but let's be real, you _should_ be able to use a command one-to-one from linux to OSX. That should be the goal. These are __core utils__! And you're gonna tell me that flags are different?

  Brittle AI features with obviously insufficient testing
I'll be fair, Apple isn't alone in this. But have you all heard about augmentations? Do you all dogfood? Seriously, I'll consult because when my partner is on the train I don't want her voice suppressed and the train sounds amplified, I want the opposite. This is a solvable issue... But your features are doing the opposite of what they are intended to. To all AI production people: augment the shit out of your data, scrutinize the shit out of your data, don't throw it at the wall and see what sticks.

Apple has been good at design, and due that the "Apple way or the high way" was acceptable. Because at least the "Apple way" made some sense. But now the Apple way isn't about making the product better, it is about making it thinner. I know that's easier, but that's the cost at being on top. Don't abandon what got you there.

Re: Apple. Apple Please

#22

Post by LoganDark »

Flop7331 wrote: post #11
MOARDONGZPLZ wrote: post #4

Earlier quoted context omitted.

As a user, I don’t want to have to type the full option name every time I use it.

Your shell should be smart enough autocomplete it anyway.

Who autocompletes flags? Even as a Fish user, I'm stuck with not-Fish often enough that I can't afford to let it become part of my muscle memory.

Before you say "Bash can autocomplete flags" I don't think I've ever encountered a single third-party shell command that actually packages proper completions.

(Some Rust commands that use `clap` for argument parsing do something to install completions after the first run, but in my experience this is not particularly reliable)

Re: Apple. Apple Please

#23

Post by amelius »

zombiwoof wrote: post #20
kevingadd wrote: post #2

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

Apple engineers know they are the best and don’t care what anyone else says

If they know they are the best, then why do they keep doing slavishly what management tells them instead of building the best products?

Re: Apple. Apple Please

#24

Post by TheCleric »

LoganDark wrote: post #22
Flop7331 wrote: post #11

Earlier quoted context omitted.

Your shell should be smart enough autocomplete it anyway.

Who autocompletes flags? Even as a Fish user, I'm stuck with not-Fish often enough that I can't afford to let it become part of my muscle memory. Before you say "Bash can autocomplete flags" I don't think I've ever encountered a single third-party shell command that actually packages proper completions. (Some Rust commands that use `clap` for argument parsing do something to install completions after the first run, b…

Plus while it’s very convenient for tools that support autocomplete of their parameters, but not all do. So sometimes you just fall in the habit of assuming they don’t.

Re: Apple. Apple Please

#25

Post by smt88 »

zombiwoof wrote: post #20
kevingadd wrote: post #2

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

Apple engineers know they are the best and don’t care what anyone else says

Apple may have the best hardware engineers, but Apple software is absolute garbage and I miss Android and/or Windows whenever I have to use it. It is astonishing how buggy and bad iOS is.

Re: Apple. Apple Please

#26

Post by judofyr »

ahoka wrote: post #18
judofyr wrote: post #12

It's a bit of a strange choice, but if you read the full documentation (man codesign) it's not too confusing actually: NAME codesign — Create and manipulate code signatures SYNOPSIS codesign -s identity [-i identifier] [-r requirements] [-fv] path ... codesign -v [-R requirement] [-v] [path|pid ...] codesign -d [-v] [path|pid ...] codesign -h [-v] [pid ...] codesign --validate-constraint path ... The first argument t…

No, it's very confusing, especially for people who are used to tools built with GNU getopt.

I too wish that command-line arguments were standardized, but alas, we were given `char *argv[]` and I've finally accepted (yes, I'm looking at you Go) that the only way is to read the documentation and type the command exactly as described, with dashes and equals intact :(

Re: Apple. Apple Please

#27

Post by LoganDark »

TheCleric wrote: post #24
LoganDark wrote: post #22

Earlier quoted context omitted.

Who autocompletes flags? Even as a Fish user, I'm stuck with not-Fish often enough that I can't afford to let it become part of my muscle memory. Before you say "Bash can autocomplete flags" I don't think I've ever encountered a single third-party shell command that actually packages proper completions. (Some Rust commands that use `clap` for argument parsing do something to install completions after the first run, b…

Plus while it’s very convenient for tools that support autocomplete of their parameters, but not all do. So sometimes you just fall in the habit of assuming they don’t.

My experience with flag autocomplete is like 90% it completing a huge filename that I then have to backspace annoyedly. Not entirely sure which shell I encountered it on but wow. I just can't afford to rely on it because of cases like those.

Re: Apple. Apple Please

#28

Post by mananaysiempre »

godelski wrote: post #21

I hate Apple products, but I just hate Windows more and am willing to give Linux a pass more. Why are core util programs different? Seriously! I know it's BSD based, but let's be real, you _should_ be able to use a command one-to-one from linux to OSX. That should be the goal. These are __core utils__! And you're gonna tell me that flags are different? Brittle AI features with obviously insufficient testing I'll be f…

The flags are different because GNU as originally conceived is the Borg of Unix userspace—every option and feature across 1980s commercial Unices must be assimilated (perhaps after minimal rationalization). Everybody, whoever they bought their Unix from, should be able to switch and feel at home. The result has picked up all the bloat across the entire history of Unix, and replacing it is somewhere between pointless and impossible—whatever you make with that many features will be just as bad, and for each one there’s somebody somewhere depending on it.

Re: Apple. Apple Please

#29

Post by minkles »

godelski wrote: post #21

I hate Apple products, but I just hate Windows more and am willing to give Linux a pass more. Why are core util programs different? Seriously! I know it's BSD based, but let's be real, you _should_ be able to use a command one-to-one from linux to OSX. That should be the goal. These are __core utils__! And you're gonna tell me that flags are different? Brittle AI features with obviously insufficient testing I'll be f…

This could be more accurately phrased as Linux being an incompatible fork of Unix and macOS actually being Unix. And you are annoyed at this scenario.

I'm not sure what your noise cancellation point is, because that works absolutely fine here between myself and everyone else I know. As for the rest of the AI stuff, I don't use it so I can't comment.

Edit: on the first point, I'm not really a fan of some of the GNU stuff. I'd rather use FreeBSD than Linux for example. That is more logically consistent.

Re: Apple. Apple Please

#30

Post by xyst »

Add this to the growing list of Apple bs that has developed over the past 10 years.

Used to be in deep in the ecosystem. Now have been winding down significantly, hardware hasn’t been upgraded since 2017. Various iDevices aging out until bust.

Services reduced to bare bones iCloud. Whatever the 200G plan is for keeping basic backups. Otherwise, have self hosted most of their services

- iTunes/Music/TV transitioned to media server accessible via VPN

- no longer use @icloud.com/@me.com email. Have own mail server with unlimited aliases. No more dealing with hide my address bs

- password/credential management migrated to proton pass

- cloud storage migrated to self hosted with other providers as backups to the backups (“3-2-1”)

Am I now paying for these services that were once “free”? Yes, but I also learn more about the protocols, set up processes, and able to customize for my own needs. No more DRM, lawyer bs that takes away your “paid” (licensed) media, no more Apple wall.

Post reply on HN