dick applebaum

wizard69 said:

canukstorm said:

macxpress said:

techprod1gy said:

That will be awesome for Apple to roll out new models 4 months after I invested in their below average iteration of the MacBookPro.

I wouldn't count on Apple updating the MacBook Pro anytime soon...what you see is what they'll offer for at least the next 6-8 months.


It also looks like the CPUs that could go in a MacBook Pro still do not support LPDDR4 RAM. They do appear to support DDR4 RAM, just not LPDDR4 RAM. Maybe I'm reading this wrong, no? If true, then Apple would absolutely not be updating the MacBook Pro, but instead waiting on a chipset that supports what they need unless they want to continue maxing the RAM out at 16GB total. 

It will be interesting to see what Apple does with these new chips. I hope they've had some prototypes in their hands so they could be developing new/updated Macs around them. 

"It also looks like the CPUs that could go in a MacBook Pro still do not support LPDDR4 RAM"

Correct. They don't.  Not till Cannon Lake or Coffee Lake, which is next year.

Yep! No Apple suitable processors in this lackluster release.

It is interesting that the iPhone 7 uses LPDDR4 RAM -- I wonder why the new Intel processors can't/won't support it.



http://evertiq.com/news/40311

thewhitefalcon said:

I hope there are more iPad specific features than this...unless they're going to launch the new iPads in March with 10.4.

Mmmm... see below

mattinoz said:

So the iPad centric update so far has zero iPad Centric features?
after all why would they make rumored mode iPad only surely as stated it would be useful to all idevices.

with other here rumor has been set free without being fully formed. 

Yes!  There are several things that could be in play, namely:

• Swift
• Expansion of iCloud services
• FoundationDB
• New Apple File System
• More Pro User support for iPads

At some point in 2017, Swift will be stable enough to be used for critical Systems Software, not just apps -- Swift has come a long way since 2014.

It appears that Apple is quite serious about expanding its iCloud offerings -- and increasing revenue from iCloud services.  But, currently, iCloud provides a bunch of unrelated silos of services, Photos, iTunes Match, Synching...  What is needed is some kind of common glue to amalgamate these services.

FoundationDB was acquired by Apple in March of 2015 -- 3 months after a major release of the FoundationDB system. FoundationDB is Lean, Fast, Reliable, Distributed, Scalable, Transactional (ACID) and Flexible.  FDB, through a system of Layers allows multiple database architectures to share a common data store.  For example, you can have an SQL Layer and several NoSQL/non-SQL db structures  (Document, Graph, Hierarchical, etc.) share a common store.  It is interesting that one of these structures is hierarchical -- as in an Hierarchical File System.

Apple's New File System:

Apple File System is a new, modern file system for iOS, macOS, tvOS, and watchOS. It is optimized for Flash/SSD storage and features strong encryption, copy-on-write metadata, space sharing, cloning for files and directories, snapshots, fast directory sizing, atomic safe-save primitives, and improved file system fundamentals.

It appears as if AFS can benefit from, and build upon the features of FoundationDB whether AFS is being used on a single Mac or iDevice -- or accessing the various iCloud services.

iPads, especially the iPad Pro, seem constrained for many Pro users...  Apple could offer additional iOS features for iPads or a more specialized proOS for iPads.  This would allow the iPad to take better advantage of: more Screen Size, Larger Battery,  more RAM, more Storage, more APU/GPU Power, a KB/Cursor, better Multitasking/background processing, Direct Interconnection to other iDevices/Macs, etc. -- while still exploiting the iPad Touch UI.  

Mike Wuerthele said:

jdw said:

AppleInsider said:

The yearly add-on brings palm rejection, and pressure sensitivity for both macOS and Windows.

Why must I pay for an endless subscription for only that?  Are those features constantly evolving such that one must pay for them endlessly?

If you need the features, you're probably happy to pay for it. If you're not, then you won't. Software development isn't cheap.

The way the app store works, is you can't charge for updates unless you make an entirely new app. If you do that, then there's no way to offer upgrade pricing from previous versions without promotion shenanigans or creative use of the software bundle feature.

I'm sure that Apple Pencil refinements will be the vast majority of the developer's work going forward, and as such, it makes sense for that group to bear the burden of the development cost.

I have Duet running on a 12" iPad Pro and it's OK.

I suspect that:

• the rumored early 2017 iPad Pro will include the ability to connect directly to a Mac and be used as an auxiliary display, auxiliary KB/Trackpad and as a graphics tablet I/O.
• Adobe, Pixelmator, AutoDesk, Apple, etc. will supply Mac and iPad Pro apps that operate stand-alone and/or interconnected.
• there is a great potential for image editing on the iPad Pro for industries such as healthcare/patient care, Drafting/Construction, etc.

Sadly, this will take all the wind from Duet's sails.

volcan said:

nht said:

You use a 5K iMac and a Mac Pro to do software development?  LOL.  Okay.

Thats too much for your average developer for anything but bragging rights and too little for anyone actually needing heavy metal.

My work covers a few different disciplines so I have my reasons for using those larger desktop machines. I guess I'm just spoiled now. I find working on a small laptop screen very tedious, especially when I have to remotely log in to the office private network while on the road. Plus when on the road the laptop ergonomics are usually awful which makes the experience even worse.

You might consider a 12" iPad Pro with KB Case -- less expensive, longer battery, denser display, lighter weight...

Here's an example remoting to an iMac 5K using the Screens App -- it shows both client and server running locally on the iMac:

• Top Left - Xcode Kitura Web Server running locally -- with access to remote IBM Bluemix services in the Cloud, e.g. Couch DB, etc.
• Top Right - Xcode iOS Client running locally in Simulator -- connecting to local Kitura Web Server
• Top Center - The iOS Client running locally in the Simulator
• Bottom left - a Safari Window accessing the Kitura Web Server running locally
• Bottom Right - a Finder Window showing the Client and Server components that are running locally in Xcode

Now if we could only do this Standalone on the iPad, too -- well maybe next year...

SOT:

My granddaughter wants to learn Swift programming, so I spent several hours updating her MacBook Air with Sierra, Xcode 8, etc.  I hadn't used a MacBook since my Alu 17" so it was an interesting experience -- especially relearning how to use the track pad.

I have a 12.9 inch iPad Pro with the Apple KB/Case and I couldn't help comparing it to the MBA. 

1. The MBA has a larger screen, but the iPad has higher resolution
2. The MBA weighs twice as much
3. The MBA has more RAM
4. The MBA has 512 GB max storage the iPad 256
5. The cost of a 256 GB MBA is a wash with a 256 GB iPad with Apple KB/Case
6. No GPS/Cell radios on the MBA, Optional on the iPad on the iPad
7. MBA weighs twice as much as the iPad
8. MBA runs macOS, iPad runs iOS

8) is the differentiator for this exercise.  To really develop in Xcode Swift, you need capabilities that are accessible in macOS but either not accessible or not present in iOS...

Yea, access to the file system, background processes, access to external devices, some missing OS and Swift capabilities...  Sure, the iPad's Swift Playgrounds (written in Swift) approximates Xcode to some extent -- but not for heavy development -- OK for incidental code maintenance and changes. I don't think a touch screen lends itself to heavy development.  

Some would add 9) to the above list -- iPad lacks a mouse/trackpad (cursor)...

Or does it?  With the Apple KB/Case, you can touch the screen to place a cursor and then use the arrow keys to move the cursor, e.g. extend a selection.

If you don't have an external kb, you can touch the screen to place the cursor and bring up the iPad's on-screen kb.

Now, it gets interesting!  If you 2-finger touch the on-screen kb, it turns into a trackpad -- and you can move the curser until you release your fingers.


So, iPad iOS has rudimentary capability for a trackpad/cursor.  What if Apple were to offer a KB/Case with a trackpad?

The items (in bold) above could be addressed by extending iOS for Pro iPad use without sacrificing any iOS capabilities for normal users.  A more robust iPad Pro with A10X, options for more RAM, larger SSD...

I'd be willing to bet developers and other Pro users would eat this up!   I know IBM and its IT customers would.