mike eggleston

I have recently gotten myself an Watch (Series 3 with LTE) through T-Mobile. I thought it would be a good thing to have, plus make a fashion statement. Now that I have been using it regularly, I hav noticed that I have become a bit more active, I am not staring at my phone as often, and my notifications are definitely more private. An added bonus (that I completely forgot about initially) is that my Watch now automatically logs me in. All in all, I am very happy with my purchase.

mattinoz said:

StrangeDays said:

AppleInsider said:

Also expected to remain on track is the so-called project "Marzipan" that will simplify developer tools with a unified code base, potentially making it easier to port iOS apps to the Mac.

Nope. AI's interpretation on this rumor has been unique a one, where the other sources don't frame Marzipan about "porting" iOS apps to the Mac. It's about universal apps that target multiple endpoints from a Xcode project codebase. The views designed for the Mac target will be just as custom and non-ported as screens created for tvOS are. But by tightening this support in the IDE it will hopefully reduce effort and barriers to entry.

So it only targets Apple platforms still or are we talking something really new like a "Swift Native" Interface project that will allow universal apps across all platforms by any developer willing to buy a mac?

I honestly think this is going to be more of a singular code base (your classes and methods) while the Interface Builder/Storyboard part of it all be handling the UI linking like it does now. Just you will be able to target Mac, iOS, tvOS, and potential watchOS all at the same time, making the handling of code and squashing of bugs far more efficient. TL/DR: Basically AI is right and so is @mattinoz ; all at the same time.

I think the biggest question that has been largely ignored by the press is this: Did Intel/ARM/Apple knowingly have a security flaw in their hardware, or was this more of case of a flaw was discovered. We know that Intel was aware of it for a couple of months, but no mention about if Apple or ARM (leaning more towards ARM on this one) knew about it. I think that should be addressed way before we start talking about lawsuits.

dysamoria said:

The only caveat is file system corruption. If the device suffers corruption to the bits referenced by multiple records, those records will all include bad data and therefore result in the user seeing multiple corrupted files. This is why we do backups to other storage devices. This is why we have always done backups, and should always do backups, to other storage devices.

A couple of things that should be pointed out. First, this is all on the same volume. So if you have a corruption on a volume, you usually do not end up with a partial corruption, it is usually more widespread (being that because the actual data on the drive isn't stored linearly, but in blocks of space that it can deal with). Secondly, this isn't "new" technology in that GIT has been doing this for some time. With GIT, you can clone a branch, make changes to it, remove files, etc, and the original branch is safe and secure. This is just like GIT, except it is on a per file basis; but it is the same mentality.

Minor question: does anyone know if the Messages app on High Sierra will be fully implementing all of the niceties that iOS iMessages has (effects, stickers, etc)?