New Apple Lust Objects for 2010 and onward

FINALLY a stake is driven into HFS+ but beware of splinters
http://arstechnica.com/apple/2016/06/digging-into-the-dev-documentation-for-apfs-apples-new-file-system/

o shit

Hope Siracusa comes out of retirement to talk about that a bit

No mention of the Dynamic kerfuffle during the Swift talk last night. I'm with the oldies on this one; I like Objective-C and I wish some of these whippersnappers understood what it was good for before inventing less-useful successors. But I'm still in a snit that bindings didn't make to iOS (not least because I saw a very cool demo of them running on an engineer's phone once) and a bigger snit about dot syntax so it's no surprise I'm not the biggest Swift fan.

dynamic kerfuffle? please to have the links

I don't have links but some people complained about Swift's type system and then John Gruber got to pretend he has written a line of code since he crapped out Markdown.pl

Tsai has the links: http://mjtsai.com/blog/2016/05/21/dynamic-swift-2/

I haven't jumped into ObjC/Swift development (just a little fiddling around with ObjC every couple years) but have a love/hate relationship with dynamic objects and all they entail

I'm assuming by "bindings," stet, you're talking about the GUI type that's essential to things like MVVM and a slew of modern frameworks and I'm kind of surprised, although not shocked, that there's no support. The current world of higher-end libraries and GUI frameworks are possibly _too_ dependent on dynamism although, outside of strict implementation in the native libraries, I'm not sure if there's a good solution.

Having gone from backend Java programming that seemed to get more coupled to dynamic binding every year (Spring, any ORM solution, eventually every library that seemed to exist) to desktop C# with MVVM/WPF I can see where leaving Swift in a binding-less, dynamism-free world makes everything very literal and debugging much simpler, but it kneecaps the ability to implement any modern-styled libraries without leaning heavily on the ObjC runtime.

I'm guessing the interim will be abstracting all your foundational code in ObjC or relying on community libraries that do all that for you and implementing pure Swift solutions, but again, you're going to hit a debugging black hole.

On the other hand, there's the WPF-style nightmare where if you don't code things exactly MVVM-style, setting up bindings required some near-arcane memorization of the binding syntax. I think the debugging/visual tools for setting those up in Visual Studio have gotten a lot better, but I still grind my teeth thinking about running an app in debug and looking for particular binding errors in the logs due to the fact missing a binding didn't generate an exception in user code

by dynamic it sounds like people are talking about introspection/reflection? these are both things you can achieve perfectly well in a static setting...

(also suspect that ppl aren't comfortable enough with protocols as a mechanism for polymorphism?)

I think that those two things are the most visible implementations in modern languages, yeah

xxp there's some good stuff from better beards than me about why that's not really the case here, at least not with substantial extra effort. Things like NSCoding, KVO and the responder chain are harder to achieve, and were impossible in earlier versions of Swift. A Swift author writes: https://news.ycombinator.com/item?id=11752983

Swift has protocols and people seem pretty OK with them, too.

with NSCoding I think the issue is what people would otherwise call "auto-deriving of protocols". that's absolutely solvable with "static reflection" (also known as "real generics").

I guess if we get all this without the Obj-C runtime etc, it'll all be sweet. But given we've got it all right now, I'm peeved at having to wait. I like Objective-C, basically.

all the things a journeyman programmer should be able to avoid but gets drawn into

I imagine this discussion will disappear when Swift introduces higher-kinded types for protocols.

http://dtrace.org/blogs/ahl/2016/06/15/apple_and_zfs/

re: the apple/oracle software points, there are huge differences between using a company's software for your retail/supply chain/hr operations (oracle's software used at apple), helping port a product to your os (oracle db running on macos), and actually integrating another company's software into your consumer product

using oracle products to do inventory tracking or something isn't a product development relationship

can't even think of very many instances where apple is dependent on an outside _hardware_ company where they haven't created an exclusive relationship, own large parts of the company, or have invested large amounts in infrastructure in the course of the partnership

displays and memory are multi-sourced, processor design is in-house and not dependent on any one chip fabricator, cellular modems/wifi chips tend to go in waves and they seem open to switching on a moment's notice. if there might be a dependency on a particular material used in construction, they've gone so far as to nearly buy out that liquid metal company and had a near-lock on that sapphire glass company before they went belly-up

anyone else on ios 10?

are you posting from 10

how is it over there?

of course

it's a keiretsu/japanese style of hybrid vertical/lateral integration that is very efficient/effective

owning parts of the company allows apple to influence them to better align with apple's core competencies

lower difficulty parts can be multisourced

xxp

Zing works fine on 10. Haven't found any other apps that don't work either (only about 10 installed). New iMessage stuff is fun to play with. And raise to see the home screen is useful when you pull your phone out of your pocket.

Music controls on home screen are much larger too, finally.

on the lock screen, that is

how's stability/battery life?

Stability seems fine. Haven't noticed a change in battery life either, but only been using for about 6 hours so far

http://thenextweb.com/apple/2016/06/16/ios-10-apps-fast-af/

If you’re scrolling through an app like Airbnb, there are a lot of ‘cells,’ or blocks of data. If you scroll fast, you’ve likely seen apps jitter trying to keep up. That’s commonly called ‘dropping frames,’ and makes apps look a bit worse than they are.

During a session at WWDC, Apple noted the reason for those dropped frames was that content is loaded just before it lands on-screen. Those cells you’re about to scroll to were loaded milliseconds before you got to them.

Now, Apple is loading those cells well ahead of the time you scroll to them to make sure that when they do land on your screen, the scrolling performance and load times aren’t noticeable. Apple says 60 frames per second is ideal, but existing scrolling performance often misses that mark.

http://thenextweb.com/apple/2016/07/28/apple-tv-network-negitiations/

the reason we don’t have actual TV channels on the Apple TV is because the company tried to strong-arm networks — and failed.

Apple’s Senior Vice President Eddy Cue is said to have taken the wrong approach. In one meeting, he reportedly told TV executives that “time is on my side.”

Cue is also accused of bluffing executives by claiming other networks — specifically Disney and Fox — were already signed up.

I WAS gonna upgrade my iPhone this year (currently still using a 5S) but w/ more and more reports of another incremental change instead of a redesign should I even bother??? Or should I finally just sign up for that ATT plan that lets me get a new phone every year? Sheesh!

5S -> SE should actually be a pretty decent upgrade if you like small phones, and that definitely won't get an increment next month.

Would you like a new iPhone 7? It is only...wafer thin.

I'm just moving to the plan to get a new phone every year.

anyone here spent time with the "smart keyboard" + IPAD pro? finally have the € for the latter, thinking about the former so that I can leave the mbp home more often, but I need to be able to write while out.

same q for pencil: anyone here used one for annotating pdfs e.g.?
+ is there any reliable info on m/l rt text recognition w/ one?

the only complaint I have about the smart keyboard is it feels a little "looser" in fit than it did originally and it's not ideal as a stand when not using the keyboard portion since it's at a set angle

as a keyboard it's pretty good, imo, although not as good as using the apple bluetooth keyboard, which I've done previously

the iPad pro is very nice hardware

My iPhone 6 has a cracked screen now and charging has been wonky, although it improved a lot after I literally cleaned dirt out of the charging point with a knife. Need to order the 7 the second it comes out.

exactly same thing happened to me - it was still under warranty so Apple just gave me a new one

my 5 (not S) finally stopped sending audio to the ear speaker so i have to either have headphones plugged in or use speakerphone :(

i have the option to update my iPhone 6 to the 7 this fall, but 7's looking like a pretty incremental upgrade. essentially a 6S v1.5. may just wait until fall 2017 when the big redesign is supposed to happen.

i assume no updates to the SE

which is what i would want

tbh i am considering going featurephone, and using my speakerless iphone as an ipod touch.

is apple still going to be dumb and get rid of the headphone jack

yes.

figure they'll one day take off the volume switch, make you adjust it from inside the OS or on your Beats cord.

Via Siri.

is the jack going away with the 7 or with the one after that?

So will they be offering some kind of wonky adapter for 1/8 inch audio connectors? Trying to figure out how that's going to look/work coming out of a single lightning jack. Honestly I hate the lightning cable so much -- having an exposed connector is the stupidest shit ever and I've had to throw out tons of cables, including "apple-licensed" ones, because they corrode so easily.

I am definitely not buying new lightning adapter headphones, nor am I going to get Bluetooth headphones -- fuck having another device to charge.

maybe they'll make you have to use a apple watch to listen to music (do those dumb watches have headphone jacks, I assume so)

that's the idea. they don't want you to use a different wire. they want you to stop using wires.

what is an "exposed connector"?

that was xp