You are here

Photos for OS X Beta is in OS X 10.10.3 Developer Release

PhotoJoseph's picture
February 5, 2015 - 12:47pm

The time has come, the walrus said… 

Photos for Mac OS X is now available as beta software for those on the developer program. Since I'm currently on the road, don't have a system to sacrifice to a beta OS, and am not on the dev program anyway, sadly I won't be giving you a personalized first look.

The good news is that you can get one from tons of others sources. [I've moved the list of articles to the bottom of this post] Thanks to everyone sending these in; keep 'em coming!

So far about the only other things I can tell you is that there are no star ratings, Aperture import of a large (but not unreasonably so) Aperture library is crashing it, and that as expected it's certainly no Aperture replacement. I'm glad to see that books are still there. Obviously at some point I'll have to get my hands on it, but at this point, I'll have to rely on the reports of others to update the site.

If you're a developer, since clearly this isn't a secret, please post your thoughts in the comments below.

===

UPDATES: I'll keep adding articles here as they are sent to me.

Level:
Beginner
App:
Apple Photos for macOS
Platform:
macOS
Author:
PhotoJoseph

Photos for Mac will really shine and show it’s strenghts when third party extensions will start releasing. Maybe developers of extensions will bring star ratings and flagging to Photos app.

That is certainly a strong selling point. Whether that comes to fruition remain to be seen. What I’m reading regarding UXKit in OS X vs UIKit in iOS is promising. Developers report that 10.10.3 beta with Photos for OS X is arriving with UXKit, an interface library similar to UIKit for iOS. We can only hope that this will encourage developers of extensions will offer them across both platforms.

When I watched the WWDC 2014 videos about frameworks, expectations were high for me that Apple was going to make this push and that 3rd party extension developers would follow. Now that we have a view into Photos for OS X, and we have seen some extensions for iOS, time will tell how well the likes of Nik or onOne will integrate into these frameworks  and whether this becomes a truly seamless ecosystem where they provide their powerful tools across both iOS and OS X.

We have long wanted “adjustment bricks” for 3rd party add-ons to make adjustments to our raw files just like the built-in adjustments in Aperture. Let’s cross our fingers that we see this come to fruition. The frameworks appear to be coming. We now need developers to follow through.

I would love to see developers of apps like SKWRT make extensions for OSX Photos app.. lens distortion correction is greatly missed in Aperture.. I use SKWRT all the time on my iPhone and UXKIT might be the way to port it over to Mac… 

Even beginners like to label things when they have many to choose from so I imagine some sort of rating system will ease into the system. Otherwise we wouldn’t have tags and colors in Yosemite. 

Now that we finally have something out, I can’t wait to see what companies like Macphun, Pixelmator, and OnOne are going to do with this. It’s pretty clear that Photos isn’t close to an Aperture replacement (yet). But this style of workflow is what a wave of next generation photographers will take to. Accessible, lean, fast, and with little cognitive load. Dang kids. They’ll ruin photography… ;)

Christopher Breen also has a first look on Macworld

Question of the day: Why didn’t The Photos Expert get early access from Apple? What were they thinking?

Thomas

That, my friend, is a question I've been asking myself all day.

@PhotoJoseph
— Have you signed up for the mailing list?

Should have it soon once 10.10.3 gets to Public Beta.

I’ve already opened my first bug. No Aperture Library of any size or number of images seems to successfully migrate. Photos gets stuck at 47% way through and never completes. Activity Monitor shows it consuming 10’s of gigs of memory. CPU gets to 100% on a quad core i7 MacBook Pro Retina. Star ratings are no more. It appears to retain the ability to make all of the products we liked in Aperture and iPhoto in terms of slideshows, books, calendars, prints.

“ No Aperture Library of any size or number of images seems to successfully migrate.”

When you say ‘never completes’ how long are you waiting?  The progress bar does stick.

Also, wondering if you have many offline referenced files?

I imported 33,000 photos / 260Gb from Aperture successfully, took around 30 mins. 

--
Bill.

That is encouraging. I have provided my Aperture source library and Photos resulting library to Apple. Two different ones I tried had the same problem. I will try on a different computer that doesn’t have some of the controls applied that my current system has. Possible that some control on this system is not compatible with Photos (like disabling iCloud).

Walter,

I migrated a 27Gb library without problems.  (Slow though and once complete it goes on to do lots of ‘stuff’, so high cpu usage for a while longer).

I would suggest that you first open your library in iPhoto, which I believe will do some ‘updating’ then open in Photos, which will do its own updating.

I can confirm that I can open the library with Aperture again, after having ‘updated’ it to Photos.

My thoughts :

This is a ‘fun’ photos app, like iPhoto.  It’s a marked improvement on iPhoto in some ways.  The big thing is iCloud integration, which will be nice for iPhone photographers and jpeg photographers (is that an oxymoron?).

This is a BIG RED FLAG for anyone using any of Apple’s professional software.  For example, FCP-X.  What this says is that Apple will drop you at any time if they no longer have a use for your market.  I don’t believe Apple have any understanding of exactly how much time (money) professionals have to invest in using any given toolset.  If I used any of those other apps, then this morning I would be looking at what’s involved in moving away from all of Apple’s ‘Pro’ software (is that an oxymoron?).

The reason that it’s a big red flag, is because Photos is simply not a professional app.  It is so far away, you can’t even consider it.  I installed it and then spent about an hour looking through it, because after an hour you’ve totally exhausted the discovery of the app.  There’s nothing left to find.

I hold a flickering candle of hope, that the considerable amount of imaging tools that Apple have built into the MacOS in the last couple of years, combined with an open plug-in architecture in Photos might, just might, mean that it could be brought back up to pro-level … but I’m not holding my breath.

Personally, I shall continue to use Aperture 3.x because it works well and will do so with Yosemite.  I will submit bug reports when something breaks.  Once Yosemite is replaced, it becomes a lottery.  It may continue to work well going forward and it may not.  Certainly, now is not the time to switch to anything else in my view, because on the upside, thanks to Adobe’s shenanigans and to the recent developments in the core imaging tools in MacOS, photo management is a space where things are likely to be happening.  Well … let’s hope so.

Photos copies your Aperture Library to a new Photos Library. Look in your folder where you keep Libraries and you will see your original Aperture Library and a new Photos Library of the same name. That is my experience.

All the libraries I tried were managed. Was your library managed or referenced? Wonder whether that makes a difference. The new Photos Library was about the same size as the source Aperture Library, implying to me that all of the data was successfully copied over. The processing it was doing in Photos simply consumed the system and Photos consumed all of my memory and a lot more until it simply got stuck. At one point it was consuming 65GB of memory on a 16GB laptop.

“Photos copies your Aperture Library to a new Photos Library.”

Quite right Walter.  The wording in the explanation of how the libraries work is somewhat ambiguous and I’d taken it to mean that subsequent to conversion, the libraries could be opened by all three apps.

My libraries are a mix of managed and referenced.  Managed for current work, referenced for everything else except the final images.

Consuming memory suggests it’s topped out in ram and is now hitting the scratch disk.  Are you on SSD?  I reckon you may just have to wait it out.  Pop the Mac in the fridge and let it do its thing :) :) :)

I have 16GB of RAM. Photos eventually consumes over 60GB according to Activity Monitor. OS X eventually pauses Photos. Other apps begin to pause. They all get memory starved. At that point CPU % on Photos drops from nearly 100% down to zero.

I let it sit like this for nearly 10 minutes. All of my other apps froze. At one point even Activity Monitor froze.

Fortunately I had already opened the Force Quit window. Within seconds of killing Photos, all of the other apps returned to normal. This is a bug and I have filed it as such with Apple.

This is 1.0 software. I realize this. I opened the bug report as I’m expected to do. I’m sure Apple will address this. I surely will not be the only person who experiences this.

“Apple will drop you at any time if they no longer have a use for your market”

Yes and no. They opened up the imaging pipeline and much more to extensions, which means that the possibilities to surpass the features in Aperture are there, given the demand. I would be very surprised if the NIK plug-ins for example aren’t out pretty soon after release, with direct access to RAW files rather than having to export TIFFs.

The interface, and Aperture’s DAM features, are very important, but it’s a little too early to suggest abandonment.

Also, Adobe is really no different. They’ve killed many products over the years leaving users in the lurch (I think I’m up to 5 or 6 products counting Macromedia ones too). 

” I don’t believe Apple have any understanding of exactly how much time (money) professionals have to invest in using any given toolset.  If I used any of those other apps, then this morning I would be looking at what’s involved in moving away from all of Apple’s ‘Pro’ software (is that an oxymoron?).”

Do I really need to link all the similar comments made when FCP X was first introduced? Or the impact that Apple’s many recent updates to FCP X have had?

For me, the true test of what is actually “professional” is the finished product.

Have you made any comparisons as to the finished image quality when processing RAW files in Photos … as compared to the results achieved for the same image in Aperture and/or Lightroom? That assessment would be very beneficial and informative.

“Do I really need to link all the similar comments made when FCP X was first introduced? Or the impact that Apple’s many recent updates to FCP X have had?”

I understand the sentiment, but it’s not the same scenario Butch.

Apple didn’t take iMovie and FCP, cancel them both and replace them with a single app.  Instead, they said they were doing a total, ground up re-write to modernise FCP.

With Aperture and iPhoto, they have said … we are cancelling both of these apps and replacing them with Photos.

“Have you made any comparisons as to the finished image quality when processing RAW files in Photos … as compared to the results achieved for the same image in Aperture and/or Lightroom? That assessment would be very beneficial and informative.”

 

Raw conversion seems to be identical to Aperture, which is what you would expect, seeing as all 3 Apple apps are using the underlying Core Image to process files.

However, Photos seems to automatically apply a raw conversion setting of Boost and Hue Boost 1.00 and I can see no way of turning this off.

Adobe use the ‘acquire and kill’ tactic to reduce competition.  They brought out Photoshop in 1989 (I have a copy of 1.0) and they still sell it today.  It’s their bread and butter.

They didn’t kill flash, probably because they thought it was going to give them a monopoly on web creation software.  There was considerable belief a number of years ago, that the web would be running on flash.  If only it hadn’t turned out to have as many holes in it as a swiss-cheese.

Yep, but not only talking about the acquired products. :-)

​Adobe doesn’t need to kill Flash (like they have so many other offerings) it is dying on the vine of it’s own volition …

Here is evidence I stated above in graphic form.

 

Yup.  That’s a bug. :)

I did another test with this same Library. I made a copy and ran a rebuild on the copy. The copy with the rebuilt database successfully migrated.

This will be a mute point for me given what I’m seeing missing in Photos. I won’t be moving my Aperture libraries to Photos. I will continue to use Aperture for what it is and monitor how Adobe’s migration tool matures. I was a long time Lightroom user prior to switching to Aperture. The reality is that I will likely have to return there. The DAM tools in Photos simply won’t be powerful enough for the professional photographer.

I anticipate using Photos for features where it excels - sharing across the Apple ecosystem. That will require exporting scaled down versions from Lightroom, importing into Photos, then sharing via iCloud. If Adobe were to get on board with iCloud integration, they could win over even more Aperture users. You would get all of the Lightroom DAM capabilities and all of the iCloud ecosystem sharing capabilities. Sharing via Lightroom Mobile only gets photos to your iPad. It doesn’t get them to anyone else, and it doesn’t get them to your iPhone or iPod.

It’s not clear to me. Can aperture and photos co-exist on a Yosemite Mac? If you choose not to use cloud syncing, can you choose to edit with photos in its library and at another time choose to edit an aperture library with aperture? If this is possible I assume you would have to open each library separately.

In other words, once you move to the photos app, would that BUST APERTURE? Or would aperture work until a new OS Doesn’t let it work?

It’s not clear to me. Can aperture and photos co-exist on a Yosemite Mac? If you choose not to use cloud syncing, can you choose to edit with photos in its library and at another time choose to edit an aperture library with aperture? If this is possible I assume you would have to open each library separately.

In other words, once you move to the photos app, would that BUST APERTURE? Or would aperture work until a new OS Doesn’t let it work?

I’ve had a look at Photos, as a long time Aperture user, and frankly it’s a step back for me, but a step forward for an iPhoto user. 

Clearly Aperture is very dead, and we won’t get back to the sophistication of Aperture any time soon - no plug-in is going to provide the clever tagging, ranking and sorting, or keywords (I believe), nor the integrated range of adjustments, soon.

I now face the facts that for a pro-user I have to leave Apple and consider Lightroom, I’m not going to wait for Photo to slowly morph into something stronger. 

It’s a sad day, I like Aperture, but I’ll get used to something new.

--
Bill.

And also much like the email server MSexChange from Microsoft, this site has become PhotoSexPert, which is kinda funny.

--
Bill.

My opinion is also that Photos is an upgrade to iPhoto and a (big) downgrade to Aperture. No stars ratings - what were they thinking? No folders/smart folders? Even if you shoot iPhone only for years, you probably have at least 30 projects/folders. Now with photos, every project is displayed as a thumbnail in a window and you have to scroll… No list, no putting into folders. 

I like the fast paced edit workflow. Just imagine if Apple just added this into Aperture along with iCloud support (the current one is rubbish).

I’ve noticed a lot of problems with my library on Yosemite and the very tough choice for me is - downgrade to Mavericks or switch to Lightroom. Sticking up with Aperture is just delaying the inevitable. 

I’ve just checked Capture one, which many people are suggesting. Maybe it has better RAW engine and a lot more features, but is not as intuitive as Aperture. There’s no freakin’ way to compare before and after shot?! You have to manually create a new version from original and THEN compare it with the adjusted image. Not to mention the lack of gestures for browsing photos and increasing brush size. 

I’ve also tried DXO and the story is almost similar (apart from the exist of the before-after option woohoo!). Next up is Lightroom. I hate Adobe products for their lack of user-friendliness. If there’s no one around to show you some trick, you have to spend hours watching youtube videos. For Aperture I think I’ve watched only the quick start videos on Apple’s site… Photoshop is great, I use it for work (prepress design) almost every day. But I still hate it.. Took me years and counting to learn some kinda basic stuff (and I’m a very techy person, a software must be very complex in order to be a problem for me).

“No folders/smart folders? Even if you shoot iPhone only for years, you probably have at least 30 projects/folders.”

Near as I can tell this is wrong. There are folders and projects. The default view is not the only one.

There are no smart folders - I am certain of this.

I also didn’t see any folders - more specifically projects inside folders. I saw only projects in a long list of thumbnails.. 

There is a sidebar.

You may be certain Stefan, but there are Smart Folders:

File/New Smart Album

 

 

Certain? :-)

In my testing I created numerous smart folders based on keywords and date. Worked fine. Kinda expected those smart albums to sync over to my iPhone but they didn’t. iOS Photos doesn’t have the ability to make a smart album itself in this latest beta but hopefully this works the same in the final releases. I did, however, create a normal album in iOS and it sync’d to Photos on my Mac.

> I’ve noticed a lot of problems with my library on Yosemite …

Stefan, I’m still on Mavericks due to sluggishness of Yosemite with window resizing especially in Safari (even in 10.10.2), but I’m not aware, that 10.10.2 has problems with Aperture. What are those problems?

I’ve been doing some extensive testing and taking careful notes regarding what migrates from Aperture and what doesn’t. Stay tuned.

I can’t say thank you enough to all of you ‘beta’ photogs. While I will not download the beta, I am following this dialog. A few questions and some observations from other sites. 

Photos creates another library alongside the Aperture library….if this is the case then the size of the Photos library is the same as Aperture’s and will take up the additional disk space on your computer.  Working with a MacBook Air with only 250gb is a problem. My referenced Aperture library is about 60gb. I don’t have that additional space on my HD.  All of my originals are offline and take up 270gb. 

Is it true that when you migrate your library, referenced or managed;  you can define the location to the same folder as the originals and reference the same files?  If so does this mean that the files are not replicated and do not increase the disk usage?

Are changes to raw Photos files permanent or non destructive?

Can changes be ‘rolled back’ individually?

At this time I understand the frustration that I am hearing here, but I see that I still lose nothing by continuing with Aperture and wait to see the final release of Photos before I make a commitment to another company. 

It doesn’t make a physical copy of your originals. I migrated a 35GB managed Aperture library. The new Photos library copy also takes 35GB+. However, if you look at your disk space, you didn’t consume another 35GB of actual disk space. I did some checking in a Terminal window and Photos is leveraging a Unix feature within the filesystem known as “hard links”. You can have one physical copy of a file on disk with multiple directory entries pointing to the same disk data. All can have different names, permissions, owners, etc.

I navigated into the Aperture library Masters folder and the copied Photos library Masters folder. The same file with the same name appeared in both, and the filesystem said there were 2 hard links to the file. That was telling to me. I know that it didn’t seem to take long enough to physically copy 35GB+ of data so Photos must be doing something very smart. Sure enough it is using hard links. I haven’t tried migrating a referenced library, but it’d bet a dollar that Photos would use the same referenced files as Aperture.

What would consume more space would be a copy of all of the databases Aperture and Photos keep about your images. Photos definitely makes a copy of this information into it’s own databases and files.

Referenced files are not duplicated.

How could they be?  For example, if they are offline at the time the new Photos library is made.

No software alters raw files.

“I still lose nothing by continuing with Aperture and wait to see …”

And in all honesty, wait to see, not just what happens at launch, which I can tell you is likely to be what we see here, except with less bugs … but more importantly, wait to see what happens when Yosemite is superseded.

I’m certain that at this stage, even Apple don’t know if Aperture will break at that time and although they have said that Aperture is no longer being developed, they have also said that they will support Aperture whilst Yosemite is still the shipping OS, which means compatibility bug fixes.

I think that there will be more options one year from now, than there are at the moment.  Moving to a new piece of software for professionals, is not something you take lightly, so why not wait, unless you’re happy to just go with Adobe anyway, which I have no doubt, many will be?

What’s important to put in context here, is not just the regression in terms of Aperture, but that professional Aperture users were getting very frustrated that development had stalled and that long hoped for features have never appeared.  There were a lot of improvements we were waiting for.

Now, the desperation is just to get back to where we were with Aperture.  No brushed adjustments???  On the up side, there is ‘emoji’ support.  Sigh.

Thanks Walter for that analysis. FCP X does the same thing with hard links.

Seems the easiest way to tell how much extra space Photos is using with an Aperture library is to monitor the entire hard disk size before and after a migration to see the difference.

Thomas

Walter, great evaluation. Have you modified a ‘modified aperture file’ in Photos and checked if the modification is reversible? Or nondestructionable  Are you able to retrieve the original raw file?

Has anyone figured out how to use the Favourites button? It’s easy enough to click and make something favourite, but I can’t see any way to filter on that, like you can with Flags in Aperture.

Having looked at the situation, I am deeply pissed off. Migrating to Lightroom loses your Aperture adjustments, but gives you a new professional platform. Staying with Photos loses useful tools like Flags and Colours and filtered views, which are essential.

So Apple has pitched Aperture users into a black hole of pain, the first time Apple have shafted me so badly. I want a pro tool, but losing all the adjustments is just so bad.

I am considering keeping Aperture for as long as it remains usable, but maybe using Lightroom going forward for new images, and not migrate unless I really have to. Perhaps even then I would use Photos for the legacy portion of the library so as not to lose adjustments, but that loses me my Flagged selections.

Which ever way you go, Apple have dropped Pro users onto a bed of nails. I would resort to expletives but this is a nice forum so I’ll stop.

Bill.

--
Bill.

I feel your pain… What I would suggest is once a public Beta is released, send feedback to Apple regarding the fact that having flags, colour ratings or star ratings is really important to your workflow.. if a lot of people rally together and send in those feedbacks, maybe it would make Apple think about adding it to the final release or version 1.1…

it must not be hard to add those features later on..they could even put it in the info panel or something to hide it from regular consumers and have it handy for Pro users..  I miss brush adjustments aswell.. 

Right now Apple is trying to win over the consumer market and not really giving attention the the Pro market.. If all the feedback they receive is : Wow, love how fast and responsive the photos scroll; they will never think of the negative impacts of their App..

 ”If all the feedback they receive is  Wow, love how fast and responsive the photos scroll”

On my Mac, it currently doesn’t scroll as fast as Aperture, nowhere near.  This is perhaps to be expected, since it’s still in beta (optimisation is frequently performed for the shipping version).

Could someone explain to me why they are convinced that the new Photos app, because it is missing certain specific features in the first publically discussed Developer Beta that it will NEVER have those features or that Apple is intentionally withhoding those features just to be spiteful?

Apple has been very busy behind the scenes re-writing a completely new paradigm … they aren’t taking shortcuts. They are not simly going to copy and paste old tired code into this new vehicle. There are way too many apps that already offer that … bloated, excessive, resource hogging code that sometimes isn’t worth the storage space it consumes when it comes to measuring it’s worth.

Does Aperture 3.6 have more or less features, functions and capabilities than did 3.5, 3.4, 3.3 …. or 2.0 or 1.0?

Stop and think about it. Didn’t Apple recently add the ability to more easily add color labels and tags (keywords) at the OS level? Why, after all this time of not only Aperture but iPhoto as well, have star ratings …. the Photos app doesn’t have it in the first beta offered … so that is proof positive it will NEVER have it?

This all reminds me of kids peeking in their mother’s oven while a cake is baking and they are convinced it’s never going to be any good because she tried a new recipe … show a little patience and wait until you can actually taste the cake before you convince yourself it’s not fit for consumption.

Lots of screaming and shouting about very little so far. I don’t understand why anyone here would think that they’d be migrating their professional workflow from Aperture 3.6 to Photos 1.0 on day 1. Actually, it’s not even day 1, day 1 is months away!

Butch,

this is being delivered ‘free’ as part of the 10.10.3 update.  That could be 2 to 4 months away, but I can’t recall any beta released to appleseed, that has taken longer than that to go to public release.  So there isn’t much time to add stuff in.  Features do occasionally get added at this stage, but it is quite unusual (although has happened recently).  This is about ironing out bugs (of which I haven’t seen any, which is impressive and perhaps a little silver star badge for Apple’s new Swift language, which Photos is being written in ( as I recall )).

Generally, I’m very sceptical, much like yourself, about hooha on Apple sites, on any subject (usually viruses) however, I feel differently about this.  It just seems clear to me, that this app is not destined for pros, unless those pros needs happen to fit into what Photos provides.  I can see how you could quite happily use it if you only ever do simple global adjustments etc., and I’ve no doubt there are people earning their livings with a camera who will be fine with this, but to give you an idea … I can find no way to ‘narrow’ the selection visible in an Album other than to make a Smart Album, which for example if you want to narrow, as one would do with star ratings, you would have to edit the Smart Album for each view, or perhaps, make several Smart Albums.  Amateurs and enthusiasts don’t need this kind of precision, so they don’t care.

But you may be correct Butch and Apple will surprise us by selling a Pro plug-in via the App Store, that will transform Photos into something useful to pros, but at the moment, it’s looking like a way to generate yet more income for the company.  iCloud space will be gobbled and is paid beyond 5Gb.  ’Projects’ in Photos, are uniquely about purchasing services.  It doesn’t look like you can even use the Books module as print templates, which I have done in Aperture with delight for years.

As for labels/flags.  Apple have done a lot of work on Mail, an app that you could argue Apple executives and engineers actually use, unlike their pro apps, and yet there is only the ability to apply a single flag to a message in Mail, and if your correspondent changes the colour in a reply to you, then your flag changes colour too.  Mail app has been around since MacOSX 1.0, so it is not given as read, that Apple will add anything at all.  They will look at it and say ‘will the average user find this useful or confusing’ and make their judgement on that and not on ’will the average professional find this useful or confusing’.

As you say though, only time will tell.  Depends on how long you’re prepared to wait.

@gfsysmon

You clearly have a “glass is nearly empty view” on things do you? ;)

Judging Apple on product design was always a moot point; so many people think they clearly know how, when and what Apple does… In reality it often comes different.

Is Apple always right? Definitely not! Always wrong? Ehr.. No.

It all boils down to a single thing: You tend to compare “Photos” with what you perceive as “Pro App” within the last decade. This is just wrong. Photos is not a “Pro App” it is part of the Operating System. A preinstalled component. It IS very likely that Apple may never market a “Pro App”-Product for photographers again, but that doesn't mean that Photos, the framework, the App and all that is built on it may not or even never be a valuable part of a professional photographers Workflow.

There are so many things you still cannot do with LR or Capture One alone - How could those be called “professional” with if you just have a “One-Stop-Shop”-Attitude? You had to combine your tools and you will have to combine your tools. This is were extensibility plays an important role. In contrary to Aperture - it is now the OS that gets extended and not only a “Pro App” for which many people decided against. There will be alot of LR, C1, DXO and so on photographers who will have “Photos” on their devices. It is very likely that they will demand integration and interoperation with what they perceive as a standard feature of their devices.

The new world of networked devices of astonishing computing power on little room is beginning _now_. “Photos” is one realisation on how to do this. Take a look on music and video - both are now mostly consumed using streaming services over the internet. I do not have to store my music library on any of my devices anymore. Storage prices did drop dramatically and my guess is - they will for sure drop even more. In the same time broadband internet is more and more established. I can easily get 100mbit here for less than 50€/month. I remember times when 10mbit were called “LAN”. Will everyone get that? No, there are still many people on slower lines - but this doesn't really hinder new products that rely on broadband internet.

Why should one badmouth an App just for not being what one irrationally hoped for? Particularily since many experts (including Joseph) did always make clear that the App will NOT be a replacement for Aperture! Photos is less… and more. And much more important: It will be omnipresent and extensible.

Jochen H. Schmidt

Pages

You may login with either your assigned username or your e-mail address.
Passwords are case-sensitive - Forgot your password?
randomness