This isn't a criticism of you, but when a major OS update comes down to trivia like this, it seems a bit of a shame to me. I remember the 10.2-10.6 releases and just how significant they were and it feels like rearranging deck chairs in comparison nowadays.
There's a whole new FS that went into production in something like 4-5 years (unheard of) among lots of over things...
Anyway: I installed the GM with an HFS+ boot volume that would fail an `fsck_hfs` (and when attempting to fix inconsistencies, it would get stuck indefinitely). Given the amount of bitrot I experience with HFS+ I welcomed the in-place conversion to something (hopefully) better and I'm surprised it worked so well.
Amazing days.
Lately I only upgrade when forced. I ran 10.8 until earlier this year when I finally upgraded my machine. Then I spent a week trying to figure out how the hell to get gdb working again because binaries now require code signing and there's this horrible new thing called System Integrity Protection that tries to protect me from myself. They also took away my Escape key and replaced it with this TouchBar nonsens just because I wanted an i7 CPU. To put this into perspective: I practically live inside vim.
That’s why I questioned the original broad claim: I know there are edge cases but most of the developers I know work on Macs and SIP just isn’t mentioned often enough for it to be anywhere near as bad in general as a few random commenters claim, not to mention that anyone I know who’s at all security savvy appreciates that it’s a trade off rather than a unilateral bad move.
1) Too many packages/servers/etc. I've tried to install under OS X over the years just didn't quite work right. That's probably not the case so much any more, but I have experienced it recently.
2) Developing against a macOS localhost can mask problems associated with my code running in the deployment environment. So to avoid those surprises, I develop against the deployment environment.
If I need root for package install or other server deployments, I log into the VM and do it there. I rarely need to install stuff on my macOS workstation.
I'm doing this on Ubuntu, but there are ways to get it done on OSX too.
1. Wait a half-second after typing the "j". That causes the mapping to time out and you can type the "k" without a problem.
2. Type something like Dijj<del>kstra.
once installed, open the app, and go to the "complex modifications" tab. then click "add rule". then click "import more rules from the internet". on the web site that opens, expand "Modifier Keys". import "Change caps_lock key".
that'll give you a rule to do what you want in karabiner. (the rule is "Change caps_lock to control if pressed with other keys, to escape if pressed alone".)
The new dock and changes to the multitasking interface and behavior take some getting used to, but my iPad feels like a much more powerful device than it did a week ago.
You already could run two apps side by side in iOS 10 (I was a pretty heavy user of that feature, which is incidentally also the primary reason I opted into the beta), it just wasn't quite as flexible. Drag and drop is new, for sure. I suppose I haven't used it much so haven't really noticed it.
The dock seems like a small improvement over the old dock, added because of the better multitasking.
They're great improvements for sure, but they still seem like incremental improvements to me.
For an example of where this smooths things out, I've been using Readdle's Documents as an approximation of a local filesystem for a while now. Saving an image to that before was tricky; iOS doesn't have a way to isolate an image out of a page, just copy or save to camera roll. So you could save to camera roll and then import it over, but you lose the filename in the process and replace it with something generic like "Image 10". Or you can do weird workarounds like using Workflow's "Get images from page", which pulls up a slideshow of all the images on the page, which you then get to scroll through and find the one you wanted.
Now you just drag it and put it straight into the destination. You can also drag the URL bar over, which saves the URL as a new text file.
And if I have data in Documents that I want to use elsewhere, there's no shenanigans required with piping it through share sheets, I just drag it out and use it.
If you want something less permanent than a file manager, the popover multitasking is also a good platform for temporary "shelf" style data buckets. I'm currently trying Scrawl Pouch, but I've seen a couple others that looked equally nice. It's basically intended as a drag-and-drop destination to temporarily store any type of data until you want to drag it back out somewhere else.
This can be the obvious stuff like images and links from Safari, PDFs and other files out of Documents. You can also drop things like map pins, which can be shared via messages or email or dropped as links into Pages documents. I haven't experimented a lot with 3rd party apps, but presumably we'll see this show up in other ecosystems, maybe dropping things like audio effects between a family of media creation tools, or someone could make a 3rd party service for sharing paintbrush presets that you could drop into Procreate.
They've also brought in the "spring-loaded folders" behavior from Finder for this. If you're dragging a URL and you want to add it as a Safari bookmark, you can hover it over the sidebar button to pop it open and then navigate to the folder where you want to drop and save it. Or after the sidebar opens, you can hover over the Reading List tab to put it there instead of bookmarks. It's integrated like that throughout the entire OS.
A whole lot of things that just weren't possible on iOS are now a 2-second interaction.
As a downside, the interface for picking up multiple objects feels a bit weird and is probably one of the bigger learning curves that iOS has gotten.
Another example I just found - you can drag an email (or several) from Mail over to Documents where they're saved as .eml files. Documents doesn't know how to render these so you see the full markup, but I can imagine that would be a useful feature for something.
Maybe a utility app to view full email headers? I don't think Mail.app has a way to get into those.
iCloud Photos is frustratingly bad, but I don't want to buy into other cloud ecosystem, like Google's. Does anybody know if it's possible to replicate the integration with Photos on both iOS and macOS, so I could write my own sync thing?
https://support.apple.com/en-us/HT202786
Some highlights:
> When shared, photos taken with standard point-and-shoot cameras, SLR cameras, or iOS devices have up to 2048 pixels on the long edge.
> Videos can be up to five minutes in length and are delivered at up to 720p resolution.
> Maximum shared albums an owner can share: 100
> Maximum shared albums a user can subscribe to: 100
> Maximum number of photos and videos from a single contributor across all shared albums, per hour: 1000
Agree with you on the time ordering. If people want a particular order, they could upload in that order. If they want time ordered, they could tap a button to refresh sort by time taken.
However, and this is a big gotcha -- you may find that causes more problems than it solves, as a group of n people are likely to have >n different time stamps and at least 2 time zones on their various devices. The resultant sort will be interleaved by sets out of order by hours in case of time zones, or out of order by minutes for individual devices.
What Apple could do is recognize contributors and devices in a shared album and let you assign an offset to each contributor plus device pairing, then sequence these all sensibly.
What I do is have a inbox type album for everyone during and following the trip, then import, sort and select and manually fix time offsets (if I remember, I have everyone take the same photo of the same phone clock at the same moment to make this easier), then re-order and curate to taste, then re-publish.
100 albums is nothing. Looking at my photo share history (on Google+, not iCloud as iCloud is useless) I have about 500 albums shared with friends and family over the last five years. And of course, there have been innumerably more albums shared with me, while iCloud limits that too to only 100 albums.
The best thing about these Google+ albums is that I don't even have to give them a name, unlike iCloud shared albums.
> and what family sharing use case needs more than 1000 photos "per hour"
It's easy, I don't share photos every day, I share them e.g. at the end of a holiday, and then there are more than a thousand. In any case I might need to share even more, since I might share the same pictures to different people in different albums, and that counts multiple times.
Of course this is all moot, since the quality is degraded too much to use this service anyway.
> (you can add thousands, just rate limits the uploading)?
It doesn't rate limit, is blocks you out and it tells you to try again in an hour. I have to remember to do that and I have to remember where it errored out. It takes forever to do something that should take seconds. They already have all my pictures stored in iCloud. They are already there! "Sharing" doesn't consume resources, it's just an entry in a database referencing data they already have. Which, btw, means that they should not have to reduce the photo quality. They already keep my high quality data, and I pay for this storage. Reencoding into lower quality actually increases the storage they have to use for my data.
I suspect iCloud Photos and iCloud Photo sharing are two completely disconnected services at Apple that don't communicate properly.
> you may find that causes more problems than it solves, as a group of n people are likely to have >n different time stamps and at least 2 time zones on their various devices. The resultant sort will be interleaved by sets out of order by hours in case of time zones
Erm, no, because you sort by actual physical time keeping track of time zone and everything?
I despise Google as a company and I try to avoid their products and services, but their photo solution just works so well on Android (it works like crap on iOS and macOS even if you install Google Photos, but that's a discussion for another day). Good model, fast, and no artificial limitations. I wish Apple would keep up.
What problems do you have with Google Photos on iOS, macOS? I use it regularly with web (windows, macOS) and my android, iOS devices and have no major complaints. For me, it's by far the best photos solution there is.
I attempted over the years to use the various incarnations of Google's photos but they consistently mangled pictures, canceled / renamed / migrated services, bungled who gets to see what under what Google Accounts, etc., until I was browbeaten into conceding defeat.
I think you missed the point on sorting by time. If multiple people are at an event, you lose the information about "physical time" because the time recorded in their snapshots is very probably wrong. So unless you fix the metadata, the only sort you can have is manual.
Note: If you're not even naming albums, how does one find them again? What's the use case? Throwaways? You're making on average a new album every 3 days, which still seems a little awkward. And innumerably more shared with you, means, what, 10 albums shared with you a day? It's amazing you have time for detailed and thoughtful HN comments. You should switch to pictures, they're worth a thousand words.
I am very happy to pay someone to take care of my problems and I am a big fan in general of paying for software and services. Not sure exactly how Flickr would help me though, but I will take a look at Flickr.
Does it integrate with the iOS/macOS photo library? Basically if I make an album in Photos on an iPhone, does it get synced up as an album by the flickr app, or does it just upload the pictures? Similarly, does it integrate with Photos on the mac, or do I need to use some other method to get my pictures that lives outside Apple Photos?
> I think you missed the point on sorting by time. If multiple people are at an event, you lose the information about "physical time" because the time recorded in their snapshots is very probably wrong.
Why is the time "very probably wrong"? I don't understand this, everybody uses NTP or whatever the GSM/telecom equivalent is. I haven't seem a wrong time on a mobile device in probably over a decade.
> If you're not even naming albums, how does one find them again?
I rarely search for specific albums, usually I prefer to view all the pictures and search by date. Albums are just a grouping mechanism for sharing. Sometimes "an album" contains just one picture.
When I go in vacation, etc, I might create a named album that I can reference later, but other than that, yeah, albums are throwaways that are just for grouping a set of pictures at a moment in time.
Not talking about mobile devices. Talking about cameras.
A dozen of us from work flew to have lunch at Noma in Denmark. We combined pictures after. There were nearly as many wrong times as there were people in the group. No software could have machine sorted these.
> Flickr
Flickr integrates with camera roll to upload originals in background but you manage albums and sharing in their app or web, and share via URLs or app. Only you have to be a member.
Personally I use cloud services like iCloud only for my iPhone pictures. For my "real" photography I just keep files on a NFS server (and Lightroom is a pain with NFS...), I don't import then in cloud services.
Which is why we have UTC.
> The resultant sort will be interleaved by sets out of order by hours in case of time zones
See UTC.
> or out of order by minutes for individual devices.
which is alright, compared to the sort by time added to album.
And I'm invariably the only geek whose photos are timestamped in UTC because I set devices that way (except for phones which I can't), or who knows that the metadata doesn't even record the TZ until a recent EXIF standard update, 2.31 released last fall, added support.
Wikipedia still says "There is no way to record time-zone information along with the time, thus rendering the stored time ambiguous." It'll be a while for cameras to catch up.
Most of my friends and family take their photos with Android, iOS devices and Google Photos seems to have fixed this issue and all of my photos have a timezone field. Here is an example of a recent one: https://i.imgur.com/8AFgKs3.jpg
Apple Photos sorts photos by UTC, today, I assume by using the GPS information inside EXIF. There is no confusion between photos taken in different time zones.
I do a lot of photography from jets, and the photos are sorted just fine, while the time zone changes all the time.
Wow, what a deal breaker. I always felt like something was off quality-wise but never took the time to delve into that.
I think (but I am not sure) you can use iCloud Photo sharing even if you don't use iCloud Photo library, but that's a special case. Then you could limit the quality of those photos, I guess. But why degrade the quality of photos that you already have? Sharing doesn't use any extra space than non-sharing. They are in the cloud anyway.
I was horrified when I learned that Google wasn’t going to save full resolution by default. Had no idea Apple would do something similar.
It's kind of a nice feature, but at the same time it makes doing things like collecting photos from my wife for a photo book annoying.
You still have full resolution originals without any recompression in iCloud Photo Library.