Your second example of a choice is a consequence of a choice. Those companies chose not to comply with new reporting rules which resulted in having their Pentagon access revoked. This is an important distinction when given "choices" that aren't really choices but mandates.
As far as how this YouTube scenario is different, people can host their content elsewhere, but there's only one Pentagon in the US.
This may be the "cell phones in public" stage, but society has completely failed to adapt well to ubiquitous cell phone usage. There are many new psychological and behavioral issues associated with cell phone usage.
It provides a perverse incentive for those running prisons (usually the government but also private owners) to put more people in prison for their slave labor.
It costs a lot more to incarcerate a prisoner than their labor will ever pay for, so there’s no meaningful incentive from the government itself.
Private prisons have an incentive to incarcerate more prisoners regardless of prison labor—as do corrections officer unions—and I can understand abolishing both of those (the unions are probably an even bigger problem). Nonetheless, judging by our high rates of violent crime, it seems clear to me that the United States isn’t incarcerating enough people.
You can get value out of yabai even without disabling SIP to add the hooks into Dock.app. The things it needs that for isn't that long of a list, see the first bulleted list here https://github.com/koekeishiya/yabai/wiki/Disabling-System-I... , maybe you don't need those / can replicate them without yabai?
When I initially read this on that page,
> The following features of yabai require System Integrity Protection to be (partially) disabled:
, I thought that meant "so yabai just won't work at all if you don't disable SIP", but it's not the case at all. I use hammerspoon to deal with spaces, and don't care about window transparency/shadows/animation, and I don't know what "picture in picture for any window" means. I do miss stickiness and per-window floating (which are features I used in XMonad), but it's fine, I'm not going to disable SIP for those.
Particularly, if you just want focus-follows-mouse like in X Windows, yabai gives you that without disabling SIP.
I'd call your ISP, because mine is not small and offers "business" class service which costs the same as residential, reserves a static ip, and slightly boosts uplink speeds.
The company may or may not pay everything. I get a $125 shoe allowance (iirc, I haven't checked the policy in a while) every two years, but most shoes that qualify for the allowance cost more that that. Of course many years I haven't been someplace where I need to wear them, but i'm expected to have them should I every have to debug something that only happens in the factory. I wear.mine mostly at home, when I remodel I like to keep my feet.
None of them, since they basically all copied Netflix! The grid view limits users to slowly looking over limited categories of content. Any list based tree structure would be better in my opinion.
I think you are overestimating your knowledge of design and UI. Mainstream software has been rigorously researched, tested, and proven to work. If we left UI design up to HN users we would end up with some plain text directory listing with vim keybindings.
At some point around 2006 I could sort all Netflix titles by user rating and even better, what Netflix expected I would rate a given title. This expected rating became incredibly accurate after I’d rated 50-100 titles according to the extant five star system. It was so good that I found myself watching many titles that I otherwise wouldn’t have considered, because the system was invariably right. I could also safely avoid titles I was very interested in when the system surmised I would be disappointed. And I could very easily inspect, sort, and edit my watch list.
Today I rarely use Netflix, and I wouldn’t pay for it. Periodically I open the app and add to my list those titles that are immediately visible which I know I want to watch, like comedy specials of comedians I’m familiar with, but I don’t inspect further, because if I haven’t already heard about a title from some external sources I trust, it’s not worth my time to check. That list just grows and grows, though titles are often removed as they become unavailable, but I never prune the list, because when I remove one title, I’m taken all the way back to the beginning of the list. Trying is just a wast of time.
It is baffling to me that anyone could interact with Netflix’s current UI and conclude that it was anything but a raging dumpster fire.
Your example is worse than stringWithFormat: for the same reason C++ iostreams are worse than format strings.
It's hard to control once you want anything more interesting than + and it's not localizable. Complaining that a function call's name is too long doesn't matter at all.
If you think that function name length doesn't matter you haven't written enough ObjC yet. It matters. Source code shouldn't read like Tolstoy.
ObjC itself is not responsible, it's NeXT and Apple's fault for perpetuating that abominable naming convention for much too long.
As for localisation, only a tiny fraction of strings in a software program are user visible. I don't think we should be designing language syntax around that edge case.
I'm sure I've written more than most other people currently alive.
ObjC is one of the most readable languages around. That's mostly because of the param:value syntax, which is much better than C-like syntax because you can see the parameter names. But the long method names aren't a problem once you have autocompletion. They also make it clearer what the best name for a method is - if you call something fmt() you start needing to make up equally clever short names for everything else, and it becomes less principled.
For algorithmic string building, I'm not sure how often you want + (aka appendString:), appendFormat: or componentsJoinedByString: are more flexible.
>if you call something fmt() you start needing to make up equally clever short names for everything else, and it becomes less principled.
Not necessary. There's a very sensible "huffmanization" principle created within Perl/Raku community which says that the need for a name/token to be overly descriptive is inversely proportional to frequency of its usage. So you can have short names and they still be human-parseable just because they are used often, and your brain used to register it. FWIW they will be easier human-parseable, because longer words take longer to read. With this approach one can has both fmt, and formatSomethingSomewhereSomeday
1. param:value is used, but convention is param:value not the gratuitous Engrish verbingParamProposition:value ObjC inherited from Smalltalk.
2. param: is optional if the variable holding value in the calling function is named "param" at compile time. This pushes you to name your params "param" everywhere that makes sense.
Jakt's popularity is limited, obviously, but it's a compile-to-C++ language, so you could use it many places.
Could this be because every privacy relevant permission, except internet access, now requires a manual approval dialog? Why list every permission when it's only used for specific feature X which is requested upon usage?
That sort of thing should be called out in (1-star) reviews.
The Samsung Gear app is like that, for example. You need it if you want to tweak the settings for their Galaxy Buds headset (the ambient sound level, for example), but on first startup it prompts for what appear to be all the permissions needed for every kind of Samsung device, including things like smartwatches—calendar, contacts, notifications, the works. If you deny any permission the app refuses to start, even though none of that is necessary for the task at hand.
My workaround was to install it and then immediately disable all Internet access (airplane mode), adjust the settings, and then purge the app from the phone before turning the network back on. Fortunately the settings are persistent even without a constant connection to the app. I think that should be sufficient to avoid any unwanted data leakage, but it's a lot of work for relatively minor benefit, and the process must be repeated any time the settings need to be adjusted.
As far as how this YouTube scenario is different, people can host their content elsewhere, but there's only one Pentagon in the US.