121–130 of 148 posts
Earlier quoted context omitted.
> In the end, they use open source strategically. If there's no benefit to open-sourcing something, they won't. Wouldn't that apply for most companies? Let's not pretend that Facebook, Microsoft et al do open source as a charity
>> Apple's relationship with open source is pretty average. That's literally what he said.
Earlier quoted context omitted.
They said the same about Facetime and iMessages but never opened or documented those, so let's see when and if it actually happens. Apple has a history of false promises when it comes to opening and documenting their protocols & data formats. Edit: I misrecalled that iMessage was announced as something they were opening.
It's not Apple's fault that they didn't open up FaceTime. They absolutely were going to, and then they were sued by a patent troll (VirtnetX), and was forced to change how FaceTime works so it relays through Apple's servers instead of going peer-to-peer. Since it was now going through Apple's servers, there was no point in opening up the protocol.
They simply lied. They never said "We'll open Facetime, but only if it's implemented as a p2p protocol & client"
Earlier quoted context omitted.
It's not Apple's fault that they didn't open up FaceTime. They absolutely were going to, and then they were sued by a patent troll (VirtnetX), and was forced to change how FaceTime works so it relays through Apple's servers instead of going peer-to-peer. Since it was now going through Apple's servers, there was no point in opening up the protocol.
IRC also needs someone to run a server. Just because a protocol isn't p2p there's plenty of reason to open it. You can independently develop third party clients, use your own server instead of Apple's etc. They simply lied. They never said "We'll open Facetime, but only if it's implemented as a p2p protocol & client"
Changing one's mind based on changing circumstances isn't lying- it's common sense. The 'thing' that Steve Jobs wanted to publish as an open protocol stopped existing due to a lawsuit, the 'thing' that replaces it shared only its name.
Anyone know how Apple pulled off an in place filesystem upgrade ? Is the data copied to your upgrade laptop and back ?
Earlier quoted context omitted.
It replaced (as of iOS 10.3) HFS+ on the mobile devices as well, didn't it?
Almost correct. 32-bit devices that received iOS 10.3 did not receive APFS. It was exclusively delivered to 64-bit devices.
The iPhone 5c will have the shortest support window from its release, at 4 years.
Earlier quoted context omitted.
I guess you missed the whole lawsuit thing [0] that forced them to make (initially P2P) Facetime completely centralized at which point it was pointless to open it up. PS: If you're gonna hate on Apple, at least find some valid points about them to hate instead of just spreading bullshit. [0] https://arstechnica.com/tech-policy/2013/08/report-after-pat...
After having just read that article, and knowing nothing else about it: ... How is that patentable?
Earlier quoted context omitted.
Good. GPLv3 software can't be on Apple products, yet every Chromebook ships with it, because Saint Google.
Signal is GPLv3 and readily available on Apples App Store. So no, you are mistaken.
> GPLv3 software can't be on Apple products
it is not saying:
> App Store
Earlier quoted context omitted.
There are a couple features missing from HFS+. Some of these are implemented in APFS: * Case sensitivity * Clones extents / ranges (reflinking) * Holes in the middle of files * ACLs * Collapsing file ranges * Per file compression and per file encryption These are useful for apps like SQLite or other stores which implement a multi user, log structured store.
FYI - HFS is capability of case sensitivity and is an option during formatting. I believe it even used to be the default.
The biggest problems I encountered were (1) occasional bugs with Homebrew formulas, and (2) Adobe's applications cannot be installed on a case-sensitive file system.
Earlier quoted context omitted.
HFS and HFS+ were never case-sensitive by default on Mac OS. Case-sensitive HFS+ was made available as an option in Mac OS 10.0, but was always glitchy (especially for boot volumes), because many applications depended on case insensitivity.
I have a case sensitive HFS+ and everything works fine. That was a problem with older versions of Adobe suite, but since lots of people on Macs used Adobe Apps...