News for hackers. Stuff that matters.
Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by macintux on Monday April 02, 2018 @02:53PM (#16737925)
> Having those mobile/tablet apps expand automatically to desktop is the next logical conclusion.

Thankfully Apple comprises vastly smarter people than me, but I've always thought this is a bad idea.

The two interaction models are so dramatically different that I don't see how merging them makes sense. A finger is not a mouse.

Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by rdsubhas on Monday April 02, 2018 @04:06PM (#16738739)
> ... I've always thought this is a bad idea ... A finger is not a mouse

There are no good or bad ideas :) Its all about time, place, knowledge of tradeoffs, execution, business, marketing, taking into account all stakeholders (user is one of them) and everything holistic :)

What you say is true, a finger is not a mouse. But we're now a decade past the release of iPhone, and by this time, the industry in general (and Apple in particular) have deep knowledge about all the tradeoffs involved here. 5 years before and this can be considered a reckless bet that requires a Steve Jobs to pull out. Now, its just natural evolution. Responsive design has been around for even longer, and changing interactions based on screen and form factors is a pretty mature problem domain now.

To be very specific:

- whether its a finger or mouse can be a runtime decision, not necessarily a compile-time or clean-slate/distribution decision for different platforms

- those decisions are already standardized enough based on existing knowledge that you can let the platform/framework (or 3p libraries) handle it out-of-the-box for you and just register multiple possibilities. instead of debating finger vs mouse - think finger and mouse

i.e. different interactions requiring entirely different apps - is not necessarily true for all of them. for a 2D application, some amount of standardization is actually good, otherwise it doesn't really help all the interaction patterns and may instead stagnate them.

Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by PullJosh on Monday April 02, 2018 @03:11PM (#16738109)
It's hard to argue with the resounding success of Windows 8.
Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by mamon on Monday April 02, 2018 @03:43PM (#16738492)
Its easy to succed when you have the monopoly in PC operating systems so success of Win 8 proves absolutely nothing. Touchscreen in PC is about as useful as a waterproof towel
Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by macintux on Monday April 02, 2018 @03:57PM (#16738657)
I had assumed that was sarcasm.
Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by amedvednikov on Monday April 02, 2018 @04:00PM (#16738694)
I think this was sarcasm :)
Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by nie on Monday April 02, 2018 @05:35PM (#16739608)
I'm also surprised that no one (of significant voice) has voiced enough to pressure Apple to think about their developer user population. Everywhere I go I see devs using mac. I'm sure the reason behind this is 2 folds: supported hardware, x64 + Unix platform. So if they make the transition, say, in 2020, the dev world must be prepared by the end of 2019, I mean, from every toolchain to dev Apps. And this would seem quite a big endeavour, not that devs world moves slowly but the amount of work...

Is my anecdotal too far off?

Re:Apple Plans to Use Its Own Chips in Macs from 2020, Repla... by macintux on Monday April 02, 2018 @10:12PM (#16741345)
It’s a good point, but I suspect the transition (if it happens) will be staged over time to make it easier.

If you look at the PPC->Intel timeline[1], Apple announced it 6 months in advance, although it went fairly quickly after that.

1: https://en.wikipedia.org/wiki/Apple%27s_transition_to_Intel_...