foljs

nunzy said:

 Maybe he should maybe he should look in the mirror to see where the blame lies. He is biting the hand that feeds him. Apple should cancel the show and fire him.

He is a millionaire, he could not care less for being in the show. Besides, not "biting the hand that feeds you" when they do something wrong just means you're subservient.

qwwera said:

I can’t wait. Charging cables have always been the worst part of phone ownership and wireless chargers work amazing. 
The sooner the better.

I wish you a painful death of your future port-less phone and the need to use a wired device with it.

nunzy said:

davidmalcolm said:

I really hope that Apple has a lot better stuff to announce at WWDC than some headphones with too much bass.

The article says that Beats was launched so people could hear music the way the artist intended.

"Too much bass" is a nerdy white audiophile person concern. For a black person, especially into the kind of music those artists were, there's no such thing as "too much bass".

Speaking in jest, but not entirely.

danv2 said:

wwchris said:

Mouse support would actually allow the iPad to become a "real" computer. Que the "what's a computer" jokes. :-)

This is my point entirely as well. If you start adding in the mouse to iPad apps you essentially just have a thin laptop. The entire point of the iPad was to avoid a mouse. The entire point of a desktop OS is to use a mouse. 

Nope. That's totally un-Apple like thinking.

The entire point of either device is ergonomics and fit for purpose.

Not about "avoiding the mouse" specifically or not.

And future devices and form factors can erase this divide even further. Not to mention future UIs can be trivially (although costly) made adaptable to mouse and touch input modes (just note like MS did it). E.g. a Cocoa UI framework that can switch to different sized/shaped targets for buttons and different layouts for apps depending on whether it's used in a touch-device or a mouse-capable one. Which has nothing to do with "avoiding the mouse" or "using a mouse".

Heck, lots of programmers ALREADY share tons of backend code between their Desktop and mobile version of their app. This will make it easier to share UI code too. 

Besides:

As a gamer, I prefer a joystick, controller or a racing steering wheel when using desktop games.
As a musician a prefer a MIDI keyboard/controller.
As a designer, I prefer a digitizer or digital pen.
As a disabled person I prefer a special controller for typing/pointing.
etc.

All of those alternative input modes can use with a desktop or a tablet -- and they're neither touch nor mice, yet apply to tons of apps in very important sectors (gaming especially is a billion dollar market).

Using touch or mouse can equally co-exist as all of the above, depending on the app and use case.

melgross said:

The only thing that bothers me is the file copy. When I copy a file, I'm doing it for a reason. I want an exact copy. If I alter one, I don't necessarily want the other altered. If one gets corrupted, rare, but it does happen, I want the other pristine one to replace it. I'm not sure how this will work.

its a reason why I'm not fond of de-duping. My copies are intentional.

You're doing it wrong then.

"Redundancy" on a single drive is not a replacement for backups (plural: as you should not only backup, but backup to more than one location).

(And of course if you actually alter the one "copy" of the file, APFS wont alter the other -- they're not hard links, they're just deduplicated until altered, and then they end up as two different copies, like "copy on write").